Oops pressed Enter and uploaded too soon. Changeset message continued: "I'm not sure if the sidewalk mapped on west side of Garrison Road is still there, it's not visible in aerial imagery, I'll have to resurvey"

Per the above, I have now removed the tactile_paving=yes tags added by you in this area in osm.org/changeset/167374082

I marked the sidewalk and cycleway as disused:highway=* here since they might be physically removed or pretty beat up and thus arguably aren't a sidewalk right now. I kept the roadway as highway=residential because it is still a street, just closed to general traffic - trucks use it for construction

Undeleting the ways allows keeping history, see osm.wiki/Keep_the_history

Hello,

Thank you for your OSM contributions in Toronto!

When editing in an area you are not familiar with, I would encourage you to check OSM history before deleting features. In this changeset, you have deleted a crossing which was built in 2024 and which I added following survey (with a changeset comment specifying that it's per survey). I had to manually re-add it in osm.org/changeset/167227001

Thanks!

The key `tc` has now been documented: osm.wiki/Key:tc

Tagging `aeroway=aerodrome` + `abandoned=yes` seems problematic to me, probably it should be something like `abandoned:aeroway=aerodrome`? See osm.wiki/Lifecycle_prefix

Hello,

Thank you for your interest in bike infrastructure in OpenStreetMap!

Just wanted to confirm - are you aware of the CyclOSM and Cycle Map views on osm.org? You can see them through the Layers switcher on the right, or here are direct URLs to see this area:
- osm.org/#map=17/43.664484/-79.425262&layers=Y
- osm.org/#map=17/43.664484/-79.425262&layers=C

In particular, the counterflow bike lanes (and the fact that the streets are two-way for bikes) are displayed on those maps, as are other features like bike tracks.

The way to mark up counterflow lanes in OSM is detailed here: osm.wiki/Key:cycleway#Bicycle_infrastructure_in_one-way_roads . Shaw Street is already marked up such and can be seen on the bike map layers. If you use bicycle directions on osm.org the routers should also know about the counterflow lanes and be able to use them.

We cannot have the bike lane which is separated only by paint as a separate way, because in OSM separate ways are only used when there is physical separation like curbs or traffic islands (and for some of those, like bike tracks like on Bloor, separate ways are not required and it's often easier not to have them).

Let me know if you have any questions!

Thanks,
--Jarek

Hi hhcfw,

I noticed you have edited in Charlotte County and elsewhere in New Brunswick, including this edit in St. Stephen back in 2019.

I'm hoping you can provide input as a local New Brunswick mapper:

The city has been renamed to "Saint Stephen" in OSM a couple of years ago. As far as I can tell, this was not done by a New Brunswick mapper. Is the local usage "Saint Stephen", "St. Stephen", or mixed?

I noticed that your change left the name spelled St. Stephen while you also edited Saint Andrews nearby - is this indicative of the local usage, or more of an accident?

If you wish you may also comment on the OSM forum where I asked about this: https://community.openstreetmap.org/t/st-stephen-new-brunswick-or-saint-stephen/130485

Thanks!
Jarek

This was done earlier today (before noon EDT) but didn't upload - reuploaded now

correction: this was actually using Esri imagery, so alignments would be to Esri

Hi skfd,

You added some foot=use_sidepath tags on roadways in Toronto. This tag refers to a _legal_ requirement for pedestrians to use a sidewalk if there is one present. I was unable to find such a law in Ontario, or a bylaw in Toronto specifically. Could you comment on https://community.openstreetmap.org/t/foot-use-sidepath-in-ontario/129980 if you know such a law?

Thanks,
--Jarek

Hello,

When you draw sidewalks as separate ways, please also update the road way (like osm.org/way/178826208) to have sidewalk=separate

(The current sidewalk=both tag means that the road has sidewalks on both sides but not drawn as separate ways)

Hello,

I saw that you have used the tag channelised=yes, for example on osm.org/way/1161788455

I recently created a wiki page for this tag: osm.wiki/Tag:channelised%3Dyes basing it on my understanding as well as a forum thread https://community.openstreetmap.org/t/is-a-channelized-river-still-a-river/127905

Since your usage of the channelised=yes tag predates the wiki page, I wanted to ask if what I wrote in the wiki matches your use and understanding of the tag (to avoid a situation where the wiki would retroactively redefine your tag). Does it? Please let me know if you'd make any changes to the wiki page.

Thanks!

Hi -- thanks all the detailed surveying you're doing in the GTA!

Quick note about the change to surfaces here. You've added surface=concrete:plates to the sidewalk. This value actually refers to prefabricated concrete plates that are made offsite and then trucked to where they are needed and placed with a crane.

The vast majority of concrete sidewalks and paths in Ontario are instead poured in place: liquid concrete is poured onto the ground in between formwork, then once it hardens, control joints (for stress relief) are cut into it. This gives the appearance of separate "plates", but the plates might be different lengths and they don't have eyelets they would have been lifted with. So I think surface=concrete is the better tag?

See osm.wiki/Tag:surface%3Dconcrete for details and photos. Let me know if this makes sense or if I have something terribly wrong!

Well, low-rise except for the tower on College, that is...

Hello! In this changeset you created a relation for the branch of Sixteen Mile Creek that flows through the centre of Milton (osm.org/relation/13103547) with the note "not the main 16 Mile Creek". I wanted to ask about this - is this local knowledge of understanding?

According to Geographical Names Database https://geonames.nrcan.gc.ca/search-place-names/unique?id=FCOTA , the branch through Milton is the main Sixteen Mile Creek, while the branch that flows southwest along the 407 is the East Sixteen Mile Creek https://geonames.nrcan.gc.ca/search-place-names/unique?id=FEHOQ . Conversely, the 1996 watershed study https://www.conservationhalton.ca/wp-content/uploads/2023/02/16MileCreekWatershed_HaltonUrbanStructurePlan-compressed.pdf linked on https://www.conservationhalton.ca/watersheds/ seems to refer to the Milton branch as West Branch, but to me it's not clear on where the "main" trunk with no branch subname begins.

Do you know the local understanding and/or usage in Milton or Halton Region?

Changeset comment continued: where final layout was not clear from City imagery (because it shows the rebuild in progress) I left the cycleway tags in place (since it'll be either lane or better), and removed parking tags (because parking might not be there in the final layout).

Having passed through here last year, I am reasonably confident what's tagged now is not wrong, but I haven't done a detailed survey. Local surveys to add parking details and/or refine cycleways are welcome/appreciated.

(I removed the phone number because the company website now lists a different one. The address and email are still the same on the website.)

Hi, thank you for the response, I appreciate it.

My initial goal with the crossing=no tag was to instruct routers not to have pedestrians cross here, rather than e.g. to communicate with other mappers that there really isn't a crossing here.

Routers incorrectly routing on the road rather than the sidewalk and crossing the street in unsafe places rather than on crossing ways is still an issue today, e.g. osm.org/directions?engine=graphhopper_foot&route=43.723463%2C-79.458302%3B43.722979%2C-79.456049 (and it's the same with all 3 routers on OSM.org: GraphHopper, OSRM, Valhalla)

But I think I see the issue you're pointing to: with a crossing=no tag at an intersection, a router can't know if they shouldn't route pedestrians along one street, along the other, or both. And in this case, routing along Dufferin Street would be valid, as long as the side of the street isn't changed.

And while I would say that a good pedestrian router shouldn't route along Dufferin Street itself given that sidewalks are mapped along it, equally, that good router wouldn't route along Dufferin Street to get anywhere from the T intersection.

So tagging the intersection itself crossing=no would be ambiguous for any router that attempts to read it, and not needed for a router that correctly prefers sidewalks.

And tagging crossing=no north and south of the intersection would only be useful for communication with other mappers, since it wouldn't change the situation for the routers. And at least in Toronto we haven't had a problem with mappers mapping crossings that don't exist, so I don't think it's particularly important to do so.

So I don't think a change here is really necessary now.

Thanks again!
--Jarek

As a point of interest, this changeset and the related changeset 164738300 are the result of about 35 survey notes and 20 photos

source was also a mix of Esri and Mapbox aerial imagery, sorry for missing it in the source tag