J,
I think the solution of closing the crosswalks for routing will work. I will do this from now on.

Whoops, let's try this again. Hi, everyone! I just noticed jmapb's message and I'm jumping into the discussion here to let everyone know what I'm doing and why. I am a very long time mapper on OSM, and it is my general goal to improve the map. I personally follow the "do no harm, delete no correct data" mantra in my mapping.

1. The Maproulette project instructions DO NOT say to add sidewalks. I am doing this as a sort of sister-project that coincides with the official "check intersection" project. My rationale is that, if every intersection in Brooklyn is done, then the crossings may as well be done at every intersection, and then if the crossings are done, than the sidewalks may as well be done, too.

2. I map sidewalks from the intersection of assignment on Maproulette until the next street to street intersection (residential or higher). This way, my methodology of pairing the two tasks stays in tact.

3. Following the logic of OSM standards for separating dual carriageways, sidewalks should be mapped as separate ways. As there is a physical boundary between the road and the sidewalk, they should be mapped separately. This allows individual tagging, for example surfaces. The road may be cobblestone while the sidewalk may be concrete. Cars and (for the most part) bicycles are not allowed on the sidewalk, and pedestrians are not allowed on the road. The land-truth physical separation of sidewalks and roads should be represented on a map where something as small as a fire hydrant can be accurately mapped.

Yes, the routing will be screwed up for a while, but I am mapping each of these individually, and I can't do all of Brooklyn in one sitting!

Hi everyone!

This needs to be reversed. Changeset deleted good data.

This needs to be reversed. Changeset deleted good data.

So the wiki is incorrect and needs to be changed. I will bring it up with the mailing group. Viewing the origins and changes, the user who originally added the highway ref tag did it incorrectly.

I'm not sure why that node is tagged that way. There was an editor that added the current traffic signals at this intersection and did not delete the previous tag of the signals at the node junction (See:node/2137931600). I will fix the error, and thank you for commenting!