The cycleway is now separated on Rue Boileau (since 2022). I will put it back as a separated highway=cycleway

That is weird indeed. sidewalk=separate should be accepted alongside sidewalk:left=separate and sidewalk:right=separate or not.

For instance if a cyclist comes from Rue de la Canitinière on the separated cycle path and wants to turn left on Céleron, it can't without the small crossing segments.

The small segments I added were for bicycle routing, not for pedestrian. If we don't add these small segments, bicycle routing can fail when transitioning between a cycleway and a road (disconnected). Pedestrians will use sidewalks, but to connect between cycleways and roads, we need these small segments. How do you suggest we tag these if you don't want to use cycleway=crossing?

And yes, my typing is really bad today! Sorry!

An issue should be added to the sepcific erroneous rendrers so at least one day they will mainly parse them correctly. It is specified everywhere in the WIKI: don't tag for the renderer. If you have specific renderers for whihc semi-colons are causing error, please tell us and we will add issues to them directly.

OK. Thanks

Hi! Can you explain why entrance=home;shop is not valid? This is indeed a home entrance with an access for shop customers also. I changed to entrance=main temporarly, but I would like to know why the double specification is not correct here. Thanks! In our local tools and models, we need the distinction between home, shop and main entrances, and entrance=yes is ignored since it does not specify the category of people using the entrance.

sidewalk=separate is even more precise than sidewalk=both. You should not use sidewalk=both when separate is set: separate means that the sidewalk(s) are drawned separately (sidewalk:left and sidealk:right are saying where are the sidewalks drawned). I will fix this.

Thanks! Next time, please use this offset for Bing in the Montreal area: 0.6,-1.54 which have been verified with official geodesic data.

Is this information public or are there your personal properties? Please do not add personal info on OpenStreetMap.

Thanks!

I would suggest to keep public school paths with no access tag or access=yes instead of access=customers, since these are indeed accessible to the public outside school days/hours. In Quebec, most public school yards are accessible to the general public when schools are not operating.

Pour les prochains imports, vous pouvez sélectionner cet offset dans JSOM, dans Imagery/New Offset: 0.6;-1.54

Bonjour! Il existe un décalage de X/East: 0.6m, Y/North: -1.54m entre les photos aériennes de Bing et les bornes géodésiques officielles du Québec dans la région de Montréal. Est-ce possible de déplacer vos buildings avec cet offset (0.6, -1.54)?

Merci!

Apron shape for YUL was aligned with official geodesic data. The correct offset for Bing Maps in the Montreal Area is: 0.6,-1.54

Please revert alignment change.

In the wiki, it says that sidewalk=separate must be use when drawn separately:

both: Both sides of the street have sidewalks.
separate: This road has sidewalks but these are mapped using separate ways. If there is a separately mapped sidewalk on only one side of the road, consider the more specific tags below.

When both right and left are specified, we don't really care if the general sidewalk=separate is present or not, but in Quebec, the three are there together 95% of the time. This may be good for legacy tools that do not fully read the right and left suffixes yet.

Please keep sidewalk:left and sidewalk:right=separate tags and values. We use these attributes a lot to know which side has a separate sidewalk mapped. Keeping only sidewalk=separate is not precise enough, because it does not specify if there is a sidewalk mapped on both side, on the left only or on the right only. Thanks!

I updated and normalized this intersection with placements, turn:lanes and change:lanes.

Yes, I reverted every changesets from this user. This is a clone of omarsoukhane from last months.