Hello LaiSzeCheung,

I'm guessing from your changeset comment "GEOG588" that you're a UofC student, working on OSM for course work.

FYI, heads up: the ways that you added in this change and tagged as "highway=pedestrian" should be "highway=footway" and "footway=sidewalk" instead. "highway=pedestrian" is for roads that are predominantly used by pedestrians, e.g. Stephen Avenue downtown. See osm.wiki/Sidewalks#Sidewalk_as_separate_way for reference. Please revise your changes to suit.

Have fun and good luck with your class. :)

I've changed the tags to "disused:aeroway=taxiway" instead. Thanks

Oops, accidentally copied a previous changeset comment. I corrected "service roads" at the CFB Edmonton airfield to taxiways

No worries, I can see that these are your first few changes. You'll learn as you go. I just didn't want you to waste your time doing something you don't need(/want) to do, and I didn't want you to feel like I was biting your head off for it either. :)

Hello Mosswa,

Thanks for your contributions to the map. Please note that you don't need to—and really shouldn't—use the "name" field to describe things that don't actually have a name. For example, you don't need to tag the putting green on the second hole of the golf course as "Hole 2". We can understand that it's on the second hole because there's a way (osm.org/way/1029491215) that shows the (rough) path of the second hole. The green itself has no name. The hole itself doesn't need to be tagged as "Hole 2"; it's already noted as such using the "ref" (as in reference) tag. Again, the hole itself has no name. Very few golf holes in the world do!

For reference please read osm.wiki/Key:name and osm.wiki/Names#Name_is_the_name_only.

Thanks again for your contributions! :)

Note that I have reverted some of your changes in changeset 116683570 (osm.org/changeset/116683570#map=19/51.04763/-114.05410).

Hi Eric,

You've changed the apartment entrance on the east side of the building to a parking garage and added a driveway, but this is completely non-existent. This entrance is a hinged man-door to the apartment building, up a few steps; there is no driveway here, there is no overhead garage door here.

Please review the actual site conditions more carefully.

Thanks

Hi Eric,

I appreciate that you're trying to identify areas on the map, but I think you need to check these areas a little more carefully before doing so. For instance you tagged the north side of Daqing Avenue in Chinatown as a retail area, but the only retail on the block is a sushi restaurant in the office building on the east side, and a bubble tea joint at the base of the apartment building on the west side. Otherwise you've encompassed an olds folks home and a church within this "retail area". As such it isn't accurate at all.

Hi kbzimmer,

Please note that you broke a turn restriction at 33rd Avenue and 21st Street SW. There are barriers allowing only one-way traffic from westbound 33rd Ave to northbound 21st St; the eastbound 33rd to northbound 21st St is restricted by a no-left-turn sign, and southbound 21st St dead-ends at the (marked...) crosswalk at the intersection with 33rd Ave. Northbound traffic approaching the 33rd Ave/21st St intersection must turn left or right on 33rd Ave: there is no straight-through path for vehicular traffic across 33rd Ave.

Please don't delete this, as I can verify these restrictions do in fact exist.

Thanks

Hi kbzimmer,

Please refrain from deleting any further unmarked crossings in Calgary. Under the "Use of Highways and Rules of the Road Regulation" (see https://www.qp.alberta.ca/documents/Regs/2002_304.pdf , section 1(1)(d)) crosswalks exist at "that part of a roadway at an intersection included within the connection of the lateral line of the sidewalks on opposite sides of the highway measured from the curbs or, in the absence of curbs, from the edges of the roadway". In plainer English, in Alberta a crosswalk exists between the sidewalks at every corner of an intersection, whether it is marked or not.

You've erroneously deleted crossings which do in point of fact exist, where pedestrians have the right of way and vehicular traffic must yield to them and allow them to cross (refer section 41 of the Rules of the Road).

Thanks

Ah, I see. That sign has clearly been defaced. It's "pace car area"...

Mapillary is a service commonly used by other contributors. You could also upload them to a free hosting service such as imgur.com.

I otherwise don't really have any objections to your edits or anything, although please be mindful of what the name key is for. We don't use 'name' to describe things (that's what the description key is for), see osm.wiki/Names#Names_are_not_for_descriptions

Do you mean a "PACE car area"...?

This isn't a neighbourhood "welcome sign" per se, it's a warning that police conduct speed enforcement...

*24 Ave

Thanks for replying. I was a little concerned about the "inaccurate" remark because I wasn't sure if you were under the (mistaken) impression that the +15 network isn't on the second floor ("Level=1"). ;)

With respect to your question, "Is the priority that it is 'correct' in the sense that someone could dig into openstreets and see that - or that the tools being used for navigation are able to understand what is actually being presented?" the answer is the former, not the latter. In short, if the Mapbox API doesn't handle navigation properly because it doesn't know what to do with the level=* tag, that's a problem with Mapbox's API, not OSM. Keep in mind Mapbox isn't the only consumer using OSM data.

One of OSM's most basic rules/good practices is "don't tag for the renderer" (see osm.wiki/Tagging_for_the_renderer). The gist is we don't map things incorrectly for the sake of aesthetics or making it easier for third-party consumers to "use" the data. As a rule if routing or geocoding apps don't work properly we don't jury-rig the map as a workaround.

Per the OSM guidelines for pedestrian navigation (osm.wiki/Guidelines_for_pedestrian_navigation#Ways_inside_buildings) "an indoor way must hold the tag level=* to define the floor where it is located".

There are lots of other errors with the way this is mapped; the fact that most of it is mapped as "foot paths" is in and of itself a potentially large problem, because if a routing API is really using this data properly it should have all sorts of errors about paths crossing buildings. You can also notice many of the path segments are named "Plus 15 Skywalk" or the like, which really shouldn't be; the network relation is named "Plus 15", the paths themselves have no name as such.

Hope this all makes sense.

FYI I've deleted the maxspeed tags you added here. I can confirm from boots-on-the-ground review that there are no signs indicating a 40 km/h speed limit here.

Hello wsmiteh,

I appreciate that someone else is trying to tackle issues with the way the +15 network has been mapped, and "indoor mapping" as a whole is still pretty rough.

That said, with all due respect, how was the level=1 tagging here "inaccurate"? For someone trying to navigate the network does it not help to know the corridors that interconnect to bridges to other buildings are on the level above ground floor...?

Oh, and I deleted node 7251853879 from the map, marking the Calgary Tower. Contrary to the edit summary of the mapper who added it, the Calgary Tower was already on the map...

Hello Test1776,

You tagged this segment of 6th Street with a signed 40 km/h speed limit; where's the sign ? I drove this stretch of road this morning, and can quite literally see it from my office window as I type this message, and I don't see a 40 km/h sign.

I cross-referenced with the City of Calgary's "Neighbourhood Speed Limits" map (https://maps.calgary.ca/NeighbourhoodSpeedLimits/), and this is not among the streets that had its speed limit changed.

Hi there,

I have reverted this change. I know with absolute, 100% certainty that this is in fact a pond. There is however a fenced-in dog park right next to it, which I have also added.

cheers