Could you show me the error that it's creating? I don't want to interfere with routers, but I also think that keeping the nodes close to where the curbs are in reality is optimal.

This changeset appears to make the curbs no longer align with aerial imagery. Are you using the correct offset of 0.6,-1.54 for Bing maps aerial imagery? I am generally very precise when I put in the curb nodes for sidewalks.

Hi there, several of these buildings should be divided much more than they are.

Rapid Editor is useful more for standalone houses than it is for series of plexes. If you'd like to use it, some of the areas up on the East end of the Island or in Laval might be good places to start, since they have many standalone buildings.

In addition, please use the offset of 0.6,-1.54 for the Bing imagery in the region of Montreal, as specified on the wiki: osm.wiki/Montr%C3%A9al

I see you've asked for review on this. I changed the direction of 1re and 2e Avenue a few weeks back, what did you change in this changeset?

Good catch, thanks. I've fixed these.

The cycleway was not missing, it was tagged on the highway. I had verified it on site just a few days ago. Having it drawn in as a separate way makes it hard for people to know what kind of bike lane it is: currently the section that is just painted and the section that is actually divided from the road are represented the same way, which I feel is deceptive for people looking for the safest routes.

This was also not drawn in with the correct offset, so it is misaligned.

Ah, I think I see why you weren't seeing any changes. Mapbox doesn't change in realtime — it takes about a week for me to see changes I've made on OSM to appear on Mapbox.

I think the reason the REV is mapped as a way despite the infrastructure on the ground not being different is specifically about the fact that it's a named way. It would be difficult to name only the bike lanes if they were only tags on the main road way.

At least on the web map, I am able to see bike paths that are tagged: https://secure.bixi.com/map/

We should avoid "tagging for the renderer," which is discouraged. osm.wiki/Tagging_for_the_renderer

I think we ought to be moving the other way with these, honestly. It feels deceptive to be marking bike lanes as separate ways when they're not completely divided from the road — with the one exception that if they're part of a named network like the REV. I have been meaning to switch the southern part of 1e Avenue to tags instead of ways, but have been waiting for construction on it to finish so that we can see what the new layout is.

I have reverted this change. Your version did not even intersect with any roads and would not have been usable by routing software. Please review the errors before uploading changes to OSM.

changeset/141160033

Hi, I already added this cycle lane a few days ago. It is now duplicated. Can you please undo your changes?

Bonjour, la piste était déjà là. Je l'ai ajouté il y a quelques jours. Maintenant il y a deux pistes. Est-ce que vous pouvez annulez vos changes?

What do these points represent?

Qu'est-ce que ces points représentent?

And every walk I did for the past month?

Wait, did you revert the entirety of what I did on my walk that night?

And sorry, I just realized I forgot the final step regarding data duplication, so I added that section to the diary entry.

I just finished up a diary entry that should help a lot with the driveways! @une%20abeille/diary/402005

Hiya, I see you're taking on the sidewalks in this area. I'm doing the same in Rosemont and thought I'd pass along some resources that I'm following in order to make the data we add the most useful possible for people who use mobility tools. [This video](https://www.youtube.com/watch?v=_AczR5YHPdw) explains a lot of the standards.

A few things I've noticed about your edits in this area:

- Are you using the offset of 0.6, -1.54 that is the standard for Bing imagery for the area? If not, you should write this down and start using it from now on so that your edits align with others'.
- Some of your crossings are labelled as Marked, but they appear in the satellite imagery to be unmarked. I know this changes a lot (paint doesn't last long through the winters here!) but we should try to use each tag when appropriate.
- It's helpful to add a Curb node to each endpoint of a crossing — though not in the middle of a sidewalk line, because that might imply to routing software that one has to traverse a curb when continuing on a sidewalk when one doesn't, if that makes sense. I don't add any further detail to the curbs in the iD editor, since it's hard to know their height, but instead scout this on location with Street Complete.
- My understanding of `concrete:plates` is that it is for premade plates that are moved into place, not for concrete poured on site.
- There are also some complicated standards for where sidewalks cross driveways, that I can elaborate on. I've been writing up a document to try to help consolidate the data on how to do sidewalks to the best standard, but haven't finished it yet.

I would very much like to coordinate with you to continue work on the sidewalks in the greater Montreal area! :)

I there a standard on how to represent les Ruelles Vertes that are not passable by cars? So far I have just been splitting the alley into sections and flagging the blocked sections as not allowing car access.

Ah, I was following the convention I saw on Avenue Laurier. I do pass by that park weekly.

I will change my offset now, thank you.