Winnipeg

V・T・E Winnipeg, Manitoba

latitude: 49.90, longitude: -97.14

Browse map of Winnipeg 49°54′00.00″ N, 97°08′24.00″ W

Edit map

Users in Winnipeg GPS traces Geohack for OSM with more maps

External links: Notes Quality checks with Osmose Keep Right! OSM Inspector Streets without names CheckAutopista2 Public transport with öpnvkarte.de Wikipedia: en Wikimedia Commons OpenStreetMap contributors map Mapillary KartaView

Use this template for your locality

Winnipeg is a City in Manitoba at latitude 49°54′00.00″ North, longitude 97°08′24.00″ West.

This page contains information relating to mapping activity that is specific to the city of Winnipeg, in Manitoba, Canada.

Mapping projects in Winnipeg

If you would like to help map Winnipeg, User:Dshpak would be interested in setting up Wikiproject Winnipeg to coordinate mapping activity.

Roads

Highways and provincial roads

See Canada:Manitoba for Manitoba roads outside of Winnipeg (outside the Perimeter Highway).

Trunk

There are 4 roads in and around Winnipeg which are trunk routes. Highways 1, 75, 100 and 101. These should all be labelled as trunk roads, within or without city limits. The roads that connect trunk routes to lesser roads should be tagged highway=trunk. The roads are almost all divided, and thus should have oneway=yes as well.

Primary

Major artery roads within Winnipeg should be tagged highway=primary. They are all truck routes and have metro route numbers, so should be tagged with ref=*. Roads that connect primary roads to lesser roads should be tagged highway=primary_link.

List of primary roads:

• Bishop Grandin Boulevard (Route 165)
• Donald Street/Smith Street (Route 42)
• Dugald Road—Marion Street/Goulet Street (Route 115)
• Henderson Highway/Disraeli Freeway (Route 42)
• King/Princess/James/Alexander (Route 42)
• Lagimodiere Boulevard (Route 20, Highway 59)
• Main Street (Route 52)
• McPhillips Street (Route 180)
• Notre Dame Avenue/Cumberland (Route 57)
• Pembina Highway (Route 42) (till it reaches the perimeter, where it becomes a trunk route as HWY 75)
• Portage Avenue (Route 85) (the parts that are not part of HWY 1)
• Route 90

Secondary

Large roads, with somewhat less significance than primary, should be tagged highway=secondary. They are all truck routes, and most have metro route numbers.

List of secondary roads:

• Archibald (Route 30)
• Chief Peguis Trail (Route 17)
• Corydon Avenue (Route 95)
• Dublin Avenue (Route 57)
• Grant Avenue–Roblin Boulevard (Route 105)
• Hespeller Avenue–Redwood Avenue (Route 37) (Henderson Highway to Main Street)
• Inkster Boulevard (Route 25, 221) (From Main Street to Perimeter)
• Isabel–Salter–Balmoral–Colony (Route 62)
• Jubilee (Route 125)
• Keewatin Street (Notre Dame Avenue to Inkster Boulevard)
• Leila Avenue (Route 23)
• Logan Avenue (Route 47)
• McGillivray Boulevard (Route 155)
• Maryland/Sherbrook (Route 70)
• Moray Street–Charleswood Parkway (Route 96)
• Nairn Avenue–Regent Avenue–Pandora Avenue (Route 35)
• Osborne Street–Dunkirk–Dakota (Route 62)
• Plessis Road (Fermor Avenue to Dugald Road)
• Provencher Boulevard (Route 57)
• Salter Street–Isabel Street–Balmoral Street–Colony Street (Route 62) (Redwood Avenue to Portage Avenue)
• Stafford (Route 70)
• St Anne's Road (Route 150)
• St Mary's Road (Route 52)
• St Mary Avenue (downtown)
• Taylor Avenue
• Waverly Street (Route 80)
• Wellington Avenue (from route 90 to airport)
• Wilkes Avenue (Route 145)
• York Avenue (downtown)

Tertiary

Significant roads among unclassified or residential roads. There will be too many of these to list.

Residential

Roads within a residential area, often with no lane markers, stop signs, and parking on one side. There will be thousands of these roads.

Unclassified

Roads within industrial or commercial areas which are not large.

Service

Service roads are unnamed, usually have uncontrolled intersections, and no signage.

Includes:

• Back lanes
• Roads within parking lots
• Loops in front of hotels

Common tags

Tags that we should try to have on as many roads as possible.

• bridge=* with layer=*
• lanes=* (in one direction)
• maxspeed=* (in km/h)
• name=*
• oneway=* (yes for oneway)
• surface=* (mostly paved in Winnipeg)

Wards and neighbourhoods

This section should be updated regarding the new tags place=neighbourhood and place=quarter.

Winnipeg is subdivided into five community committees, made up of a total of 15 council wards. For planning purposes, it is also subdivided into a parallel set of community areas, made up of neighbourhood clusters. The 230 neighbourhoods of the city are the basic building blocks common to both of these schemes. See w:Subdivisions of Winnipeg.

A ward or neighbourhood is to be mapped with a node and boundary. Well-known community areas or other named districts of Winnipeg should also be mapped, with only a node.

Each ward or neighbourhood is mapped with a node near its centre, having the following tags (where applicable).

• place=suburb (or place=locality for an unpopulated industrial neighbourhood)
• name=<name>
• population=<number>
• source:population=<free-text citation>
• wikipedia=<url>
• is_in=<ward>; <community committee>; Winnipeg; Manitoba; Canada; CA
• is_in:ward=<ward name>
• is_in:community committee=<community committee name>
• is_in:city=Winnipeg
• is_in:province=Manitoba
• is_in:country=Canada

The boundary of a ward or neighbourhood is mapped as an area.

• boundary=administrative
• admin_level=10
• border_type=community committee or border_type=ward or border_type=neighbourhood

Relations

Better still, each subdivision can be represented as a relation, grouping the place node (with label) and boundary ( outer). The boundary can be composed of an area, or of individual ways sharing endpoints, and may contain holes represented by ways or areas ( inner). A boundary segment can serve for both of its adjacent subdivisions, or for both a neighbourhood and its containing ward. Road, railway, and waterway segments may also serve double duty as boundary segments.

Relation

• type=boundary
• name=<subdivision name>
• boundary=administrative
• admin_level=10

Place node

• Tags listed above
• label

Boundary areas or ways

• Tags listed above
• outer or inner

[Should place=* tags be duplicated in or moved to the relation?]

This scheme may change as new tags are adopted for quarters and neighbourhoods.

• Proposed features/place=quarter
• Proposed features/place=neighbourhood

 Buildings

Buildings should be marked as a buliding, and have a name and address.

The following tags should be present on as many buildings as possible:

• building=yes
• addr:housenumber=(number)
• addr:street=(street of number)
• addr:city=Winnipeg
• addr:province=Manitoba
• addr:country=CA
• addr:postcode=(Canadian postal code)

If the building is a mall, add shop=mall. If it's a hotel, add tourism=hotel. Look at Map features for other tags.

Recently the tasker has been used for tracing building footprints, the tasker is availiable here: http://tasks.osmcanada.ca/project/89

Bus routes and stops

Main article: Winnipeg Transit

We have completed the project to migrate all Winnipeg Transit stops and routes to the PTv2 schema.

WT publishes their data using the GTFS standard. We pull in that stop and route data to generate and keep the routes up to date.

We are using a combination of PTNA and GTFS-OSM-Validator to ensure that the Winnipeg Transit routes are in sync. Again, we are using Winnipeg Transit's GTFS files as the source of truth.

PTNA Configuration: Winnipeg/Public Transport/Analysis/WT-Routes

Additional Stop Data by hand

There is additional stop data that is accessible via Winnipeg Transit's API, but not in their GTFS feed. Things like:

• bench=yes/no
• heated=yes/no
• shelter=yes/no

Every so often, we update stops with their features using the WT API.

Winnipeg Transit's digital staff have been very responsive via their feedback form if a stop appears to be grossly misplaced. If a stop appears to be on the wrong side of the road or something like 70+ metres away from its actual location, please let Winnipeg Transit know via that feedback form.

Walking and biking trails

Walking paths can be tagged with highway=footway, whether they are paved, gravel, or dirt paths. If bicycles are allowed (as they normally are), add bicycle=yes. Areas with steps (e.g. the stairways that access the river walk) should be tagged highway=steps instead.

As with roadways, the surface tag can be added to differentiate between paved and unpaved paths.

Bicycle routes can be tagged per the cycle routes guidelines. City of Winnipeg bike routes segments can be grouped into relations tagged type=route, route=bicycle, network=lcn, and bicycle=designated. For named routes, add name=Trail Name. The Trans Canada Trail can be grouped into a relation tagged network=ncn and name=Trans Canada Trail.

(Many city bicycle routes are members of a single cycle route relation named Winnipeg Active Transportation Network. This seems contrary to the intent of the tag, since the network is not a route.)

Remember that most maps are copyrighted. Derive the actual routes from personal experience, GPS tracks, or Bing satellite photo.

Cycling infrastructure

The City of Winnipeg’s Cycling Map includes the following legend entries.[1] The infrastructure categories correspond to some entries in the type field for cycling facilities in the city’s Open Data portal.

• Off-street paths
  • Multi-use path, paved: these are wider than the standard sidewalk. Tag as highway=cycleway, foot=yes, segregated=yes/no depending on markings, surface=paved (concrete or asphalt).
  • Multi-use path, unpaved: as above, with surface=unpaved (gravel or chipped wood).
  • Spur route: park paths and sidewalks.
• On-street bikeways
  • Protected bicycle lanes: highway=cycleway.
  • Buffered bicycle lanes: cycleway=lane, typically cycleway:buffer=left, cycleway:buffer:width=0.6 (see Proposed features/Buffered bike lane).
  • Painted bicycle lanes: cycleway=lane.
  • Neighbourhood greenways: usually no specific AT infrastructure, but could be marked with bicycle=designated.
• Informal on-street routes
  • “Low-stress”: no infrastructure, not an official bike route, no special tagging.
  • “Medium-stress”: no infrastructure, not an official bike route, no special tagging.
  • Sharrows: “Note: Sharrows (painted bicycle symbol only) are shown on this map as informal facilities.” The Manitoba Highway Traffic Act requires slow vehicles including bicycles to travel as close to the curb as possible, so the city’s sharrows do not conform to the NACTO Urban Bikeway Design Guide. Our sharrows are non-standard, so let’s not mark them as cycleway=shared_lane.
• Area of caution: no infrastructure.

External links

• Winnipeg Cycling Map at City of Winnipeg Public Works
• Active Transportation Network at City of Winnipeg Open Data
• Winnipeg Trails Association Trails and Maps

Open data

The city of Winnipeg has an open data website at data.winnipeg.ca, subject to the Open Government Licence – Winnipeg. The OGL Winnipeg is similar to the OGL Canada (diff): a substantive difference is the definition of “personal information” by the Manitoba FIPPA instead of the Canadian Privacy Act. This licence has not been confirmed to be compatible with OSM.

Winnipeg Transit has a separate Open Data Web Service and API: api.winnipegtransit.com; Open Data Commons PDDL[2]; Terms of Use[3]. An earlier static version of their open data was used to import bus stops to OSM.

See also Potential Datasources#Winnipeg MB.

To do

• Check, if there are tasks on pages that link to Winnipeg

See also

• Canadian tagging guidelines
• Map Features
• Canada:Manitoba
• Canada

External links

• City of Winnipeg official property map
• Wikipedia: List of Winnipeg City Routes