Never mind -- my mistake. I checked the wiki and it says we should use "st" for "short ton" to indicate USA tons for maxweight. I've never seen that abbreviation used that way before, but it's consistent with the wiki so I guess it's correct?

Anyway, happy mapping, J

maxweight=*#United_States

Howdy DovePod... thanks for your mapping around Fleishmanns.

I noticed you tagged the maxweight on this bridge as "20 st". That's 20 stone, or 280 pounds, far too low a limit for a vehicular bridge.

Similarly, the Main Street bridge you tagged as "22 st".

I'm guessing these maxweights are supposed to be tons -- can you confirm?

Thanks, J

Thanks, as I mentioned above I did browse through the Atlas Checks github page but short of building my own Atlas Checks instance populated with the map in its previous state, there's no way to be certain where this process went wrong.

My best guess is that the actual issue flagged by the ConnectivityCheck was non-connectivity between ways 60251535 and 60251535, which both ended at nodes overlapping at the same location, one of which was 765365658. A connection was needed, but not the Harlem River Drive motorway. I've fixed this now (joined 60251535 and 60251535 into a single highway.)

Ok, clicking through, to osm.wiki/Organised_Editing/Activities/Facebook from your user profile, I can see the description of the "Atlas Checks" project, and drilling down into the Atlas Checks github I can see there's a little blurb about the "Connvectivty Check" feature at https://github.com/osmlab/atlas-checks/blob/dev/docs/checks/connectivityCheck.md

None of this gives me any clue why you'd want to attach node/765365658 to the Harlem River Drive. I have to assume that your Atlas Checks instance flagged this spot for review, and you decided that this connection between the track the motorway was correct. Supposedly based on Bing imagery? If you can elaborate, I'd love to hear it.

I've left this alone hoping you'd find time to review this change and perhaps improve the quality of your QA initiatives. But I believe it needs reverting, so if you want to examine it in situ hurry up.

Thanks, J

Howdy... can you elaborate on the data source for this change, and the meaning of these hashtags?

Thanks, J

Ok fixed in 110238441

howdy ... just noticed that this changeset resulted in some very sharp angled roads in downtown BK. My guess is that way/46121844 was unintentionally dragged a bit to the north. Happy to fix this but just wanted to check with you first in case there's something I'm missing. Cheers, J

Hi Ryan -- this is a real map used by real people. Please don't vandalize it. I've reverted this changeset. Thanks, J

Hi, I've removed these incorrect parking lots, except for way/944384805 which I believe can be legitimately mapped as amenity=parking + parking=street_side according to parking=street_side

Also, please try to use changeset comments that actually describe what you're doing. Repeating "Ajout multiple" every time is not helpful to your fellow mappers.

Cheers, J

Hi there... I've reverted this change. The protrusions you added to this building are floating balconies, not part of the building footprint.

Also, the imagery you're referencing is not well aligned. Consider using the NY Orthos imagery for fine detail work in NYC, since it has the best alignment.

Happy mapping, J

Chiming in -- never heard of this "Brooklyn Community Board Recognized Colloquial Neighborhood" -- what's your source?

It looks like you're using the default web-based map editor (known as iD)...

To change a road to a driveway: Click on a road (say way/20207913 ) in the editor window. At the top of the sidebar on the left, under "Feature Type", it says "Residential Road". Click that and you'll get a menu of other feature types you can change it to. Click "Minor Roads" and under that click "Service Road." It will change to a service road, and then "Fields" a box named "Type" will appear. There you can select "driveway." (OSM classifies driveways as a type of service road.)

For marking a road private, setting "All" to "private" works fine. But I'd advise to use this sparingly. Very often routing software will try to avoid private roads whenever possible, which makes sense -- but since there's no explicit link between the driveway and the house, it risks generating incorrect directions. (Eg, if the driveway way/20198840 were marked as private, routing algorithms would probably send a traveler to the closest spot on West Ohayo Mountain Road, rather than along Penny Lane.)

Setting access to "destination" instead of "private" might be a better approach. This means you're allowed to use the road if your destination is here, but through traffic is not allowed. But it's often not really necessary because this is how software tends to treat driveways regardless.

Another thing: if you haven't yet, try changing the background imagery (shortcut key B in the iD editor) to ESRI instead of Bing It's got slightly better resolution and alignment around here, and the photography's from late fall so there's a lot less tree cover obscuring the smaller roads. (It's still a few years out of date though; they all are.)

Cheers, J

Gotcha. FYI that road and many others, including most of the bizarre or imaginary roads that you'll see in the USA, were added as part of the import of the US Census TIGER data in 2007. (see osm.wiki/TIGER ). In some places the TIGER data was pretty good but it other places it was of poor quality, and cleanup of the imported road data is ongoing to this day.

If there's something that clearly doesn't exist, deleting it is the right thing to do -- though sometimes it can be hard to be sure, especially in areas with tree cover. You can also send a message or changeset comment to the user that added the road. (In this case it was added by DaveHansonTiger, which is one of the accounts used for the data import, no longer active.) And I'm happy to help if you have any questions.

Meanwhile I removed that road and added the driveway.

Happy mapping, J

Hi jg8, welcome to OSM!

It looks like this road way/20203764 doesn't really exist (goes right through a house) so I was going to delete it, but I noticed you tagged it as private. Maybe you meant to mark a different road as private?

hi sean, wondering where you found the name "Quadrangle Road" on Governors Island?

Thanks, I've opened an issue on iD's github

https://github.com/openstreetmap/iD/issues/8539

Hi MxxCon, FYI -- the "nycdoitt:bin" value refers to the building, not the POI, so it shouldn't be moved to the node. J

Hi there! Thanks for your work here around Woodstock.I'd appreciate it if your changeset descriptions could be a little more accurate, though. I don't think you touched a single garden! J

[Resolved -- it's a public trail. Nordic Road is private but allows foot traffic from parking at node/8812774745 to the trailhead.]

Hi George, is this a publicly accessible hiking trail? I'm wondering because it looks like the road it departs from, Nordic Drive, might be for private use only:

https://www.bing.com/maps?osid=06949a7a-7619-46c1-bca8-55f7ed80ce1a&cp=42.025561~-74.147495&lvl=19&dir=266.22766&pi=-4.015408&style=x&mo=z.3.35&v=2&sV=2&form=S00027

Thanks, Jason