Hi! Thanks for your contributions! However, this cycling path was already mapped as part of the road. When there is no physical separation between the road and the cycling path (only painted lines or flex posts), we map the cycling path as tags on the road itself. Thanks!

Ouch! Thanks!

Good catch!

J'y suis passé hier, la séparation est une rangée de bollards amovibles/flex posts, donc je vais conserver la piste cyclable dans les tags de la route. Merci!

À moins qu'il y ait eu un changement dans les 6 derniers mois?

Cette piste cyclable n'est pas séparée physiquement de la rue, donc normalement, on garde le tag sur la route elle-même. Il n'y a que des bollards amovibles (flex post)

Is this section now separated from the road with a barrier or curb? If not, please follow wiki and keep the old tags which were correct?

When there are more than one shop/POI in a single building, please use a node instead of adding the shop to the whole builidng. Thanks!

Parfait, merci!

SVP garder les POIs en noeuds et les adresses sur les portes (entrance=shop), c'est plus facile à traiter.

ok super!

OK, fixed with hgv and trucks tags.

I believe this entrance is accessible to customers? access=customers is the ocorrect tag here. private would be for employee only. Can you confirm please?

Ok no problem thanks!

Est-ce une nouvelle piste cyclable sur le bord de l'ancien golf? Est-ce que les barrières sont démantelées? Merci de valider.

We could also contact the city and ask for a no-foot crossing sign there. This may be easier than you think!

Keep in mind that I agree 100% we need to be able do distinguish dangerous crossings and we at Chaire Mobilite are exploring future ways to do so as well. See https://www.reddit.com/r/openstreetmap/comments/12p3nee/dangerous_pedestrian_crossing/ for more info.

I understand very well. You could change foot=permissive isntead, but there is no way right now to specify the danger level of a footpath. I wish there was, but it does not exist yet. Usually, we should use other data on top of osm for this kind of usage, but I know it is difficult to implement. However, you can add any tag you like and use them for your specific routing. Example: routing:danger=1-10 and then in your routing engine you could route only if danger <= 5 or so. But keep in mind this is non-standard and people could remove those unstandard tags. The problem here is that on a Sunday at 7AM, this crossing is almost always emty and thus very safe, but at rush hour on a weekday, this is dangerous, but still legal. Highway code explains that you must use a crosswalk if between two intersections, but at an intersection, you can cross, even if there is no paint or crosswalk as such, expcet if there is a specific sign for pedestrian saying it is illegal to cross the street there.

Unsafe but legal. Unfortunately, we need to keep them. Thanks!

Also, please use this offset when dealing with Montreal Bing 2020 aerial imagery: 0.6,-1.54

See this page: osm.wiki/Montr%C3%A9al under Bing Maps Offset