Hello, the Carrolton boundary is now badly mangled, should I revert this edit or are you able to fix it? Please see: relation/6402220

Hi, thanks for edition bus routes, can you tell me where your getting the route information from?

Thanks for the intro Martin - Jack, we could really use your help with this!

Just curious whether you might be experiencing this JOSM bug? https://josm.openstreetmap.de/ticket/20690

I believe you made a typo in your changeset comment and meant to say "re-tagging as motorway".

Hi,
This interpretation is inconsistent with how highway classifications are used in the rest of the world. There is an emerging consensus, at least in New England, to properly apply functional highway classifications so they can be used as intended. This is one such application. The physical highway classification you described is the reason that, for example, the map is broken at zoom 7 in the TX/OK/KS area. I invite you to join the discussions happening in #local-us-northeast on the OSM US Slack as well as recent threads on the talk-us mailing list discussing highway classifications.

Corrected changeset comment: tagging stream areas

Thanks for catching that!

I would recommend discussing the place tagging with the folks in #local-nyc on the OSM US slack (https://slack.openstreetmap.us/). There are quite a few folks mapping in NYC so it would be better discussed there.

Hi, this change broke a city boundary:
relation/10090463

JOSM messed up my changeset comment. This change was to fix inconsistent highway classifications in the Warwick area so there's continuity.

Hello all. This question was actually discussed at length, and the consensus at the time was documented at osm.wiki/United_States/Public_lands

That article lists the specific tagging that should be applied to those areas, and if any tagging is different from that description, it should be changed.

If mappers disagree with the guidance listed in the United States/Public Lands wiki page, that should be raised and discussed on the talk-us mailing list. Let's make sure we're not inventing new interpretations when there are already documented conventions.

Hello brucebruce,

Can you explain this object?
way/901361357

I am not aware of any water hazard markings in this location, and I am planning to delete it, but I wanted to check with you first.

Thanks! I did some cleanup in that area, so should be good now.

Sure, you can see the gap in the border if you look here:
relation/117955#map=15/26.0834/-80.1883

Unfortunately there is a known issue with iD where this occurs sometimes (see: https://github.com/openstreetmap/iD/issues/8286)

Hi, this change broke the Fort Lauderdale boundary polygon.

Looks like there's still a big dangling section hanging off the airport:
(see: relation/109847)

Unfortunately iD doesn't warn you properly when a boundary gets broken (see: https://github.com/openstreetmap/iD/issues/8286) which I why I normally use JOSM for boundary relation editing.

Feel free to hop on the OpenStreetMap US Slack space (https://slack.openstreetmap.us/), channel #local-mississippi if you want to chat more with local mappers or need tips and tricks!

Hi @empers, this issue was discussed extensively within the US community, which is why waterway=riverbank is no longer in use in the United States.

Aloha! Thanks for adding this nicely-traced river area near K-Bay. Join me friend, in switching over to natural=water + water=river, which has emerged as the US consensus for tagging river areas. Also, feel free to join us in the OpenStreetMap US Slack, at https://slack.openstreetmap.us/ , channel #local-hawaii

For more details on river tagging, see the river modernization project here:
osm.wiki/User:ZeLonewolf/Procedure/River_modernization

Mahalo!

Hi, this edit broke the boundary of Jackson: relation/109847