The roadways that have been tagged toll=yes in this changeset are not toll roads. Reverted here: osm.org/changeset/141515683

The roadways that have been tagged toll=yes in this changeset are not toll roads. Reverted here: osm.org/changeset/141515279

Hi Zol87,

The Pine Street railroad crossing next to 11th Street has been permanently removed. There is now a raised train platform blocking its path.

Could you remove this crossing once again and check where the bus has been rerouted to?

Hi again. I haven't seen a response from you, so I went ahead and removed ref="I 69" from the roadway. Much of the roadway was already tagged with noref=yes and fut_ref="I 69", so in the future, once this highway finally gets the Interstate designation, make sure to remove those tags as well.

osm.org/changeset/140512648

Hi DawsZed, I have a question unrelated to the previous feedback.

The tunnel box under Hudson Yards was originally mapped from satellite imagery a few years ago when it was still exposed to the surface. I see that you used an angled photo of the tunnel box to adjust the tunnel edges. Tracing from aerial imagery usually allows for more precision than eyeballing from a photo. Were there any other sources you used here?

Not to mention, HaPe-CZ is accusing the German and Canadian participants in this conversation of American nationalism.

Personally, I have a lot of complicated feelings about the United States. I'm not particularly patriotic. But I'm not going to start adding Swahili and Hindi names to features in the Czech Republic, and then accuse the locals of Czech nationalism when they notify me that it's against local guidelines. When I map in an unfamiliar country, I talk to the local community and follow their guidelines.

¡Hola!

Gracias por responder. No fui yo quien etiquetó originalmente esto como highway=bus_guideway. Lo encontré y vi que estaba mal, así que agregué un fixme, con la esperanza de que un mapeador local lo arreglara.

HaPe-CZ, why are you adding German terms specifically? Why not Chinese? Or Spanish? Or Arabic? What criteria are you using to determine which language goes in the name?

If we tried to include every language in the name, then certainly every literate person in the world could read it. But of course, it would be unreasonably long. So the global community of OSM mappers generally agrees that each local community should decide which languages are appropriate for the name.

Despite our significant English-speaking majority, the United States is a vibrant multilingual country. We have plenty of places where multiple languages belong in the name, like Kaser, New York [1] or the Navajo Nation [2]. However, I'm not aware of any border communities in the US with a significant German-speaking population, so naming these lanes "LKW" would be against local tagging guidelines. Nearly all signs in the US (outside of Puerto Rico) are in English, and we map what's on the sign.

As a local of the Czech Republic, you are free to propose changing the language of names in your home country. But when you try to change tagging guidelines halfway across the world in a country you're not familiar with, it's natural that you'll receive negative feedback.

[1] osm.org/node/158859890#map=15/41.1194/-74.0627
[2] osm.org/relation/9795457

Hi jrm2020,

Has the Purchase Parkway been fully signed as Interstate 69 now? Or does this segment still have "Future I-69" signs? I couldn't find any news articles online saying that the extension was complete.

Fine by me. Redundant tagging added here: osm.org/changeset/137803578

At time of writing, there are over 36,000 objects on OSM with junction=yes + name=* [1]. But there are only 908 instances of junction=yes + ref=* [2], 512 of which also have name=* [3]. Many of these appear to be tagging errors, using the ref=* of a nearby highway.

Carto doesn't expose ref=* here. I don't know of any OSM data consumer that does.

[1] https://taginfo.openstreetmap.org/tags/junction=yes#combinations

[2] https://overpass-turbo.eu/s/1wzK

[3] https://overpass-turbo.eu/s/1wzM

Thanks for fixing it! Have a good day.

Hi brianm0000,

It looks like Ireland Road in South Bend was disconnected from the railroad right-of-way you were working on here, leaving a section missing. Has this part of Ireland Road been demolished? Or was this a mistake?

Hi web_c,

I was going off accepted practice as documented on the wiki [1]. A detention basin is dry most of the time, and periodically filled up with stormwater. Most of the parks within the Addicks and Barker Reservoirs are flooded after heavy rains and close down temporarily. This implies that the basin area should include the parks.

The City of Houston was the source for the reservoir boundaries as originally mapped. Hurricane Harvey has raised some questions about where the true northern and western boundaries of the reservoirs are, but if anything, it should include a *larger* area as a result. For the parks to be excluded, there would need to be some sort of elevation-raising project to ensure they aren't flooded when the rest of the reservoir is, and I haven't found anything online about such a project.

Is there anywhere where I can read about the findings from your meetup group (for example, a user diary entry or an online discussion thread)? If not, could you summarize what happened in the local meetup?

[1] osm.wiki/Tag:basin%3Ddetention

Thank you for reverting the changesets. I know It's frustrating to have to revert hours worth of your own work, but it's important to keep geometries valid and intact.

Is there anywhere where I can read about the findings from your meetup group (for example, a user diary entry or an online discussion thread)? If not, could you summarize what happened in the local meetup?

This issue requires more discussion than some changeset comments. Start a thread on https://community.openstreetmap.org.

Please stop making changes to the Addicks and Barker Reservoirs. You have once again broken the geometry of the both reservoir relations by leaving several inner polygons outside the outer polygon, and adding new outer polygons inside other outer polygons.

In addition, you have not specified a source other than Bing Maps Aerial, and you have not provided a link to any prior discussion on this topic, which leads me to believe there has never been such a discussion, and you are performing these changes unilaterally without consulting the local community. Please start a discussion on community.osm.org before proceeding with large-scale changes like these.

Would you like to revert these changes yourself, or would you rather I take care of it?

I'm not quite sure what point you're trying to make here, but the Addicks and Barker Reservoirs are detention basins that are indeed dry most of the time, but fill up with stormwater after heavy downpours. The accepted tagging scheme for detention basins is natural=water + water=basin + basin=detention [1]. If this doesn't look right to you, consider posting a message on the community forums [2].

[1] osm.wiki/Tag:basin%3Ddetention

[2] https://community.openstreetmap.org/

Could you please provide a link to where this issue was addressed? I am not aware of any discussions about this topic. For developed areas to be carved out of the reservoir, they'd have to be physically raised in elevation, and I can't find any information online about such a project.

To reiterate, your changesets broke five multipolygon and boundary relations. There were several "inner" polygons left outside of "outer" polygons for the reservoirs, and the boundaries for Harris and Fort Bend Counties had a chunk left missing. Even if your mapping practice were otherwise correct, these large-scale geometry errors needed to be reverted.

I was one of the first few editors of these reservoirs over 10 years ago. I grew up in Katy, and while I have since moved away and my most recent edits have largely been outside of Katy, I have not stopped caring about my hometown. The boundaries of the reservoirs and the elevations within are largely the same as they were back then. If you have any updated information, let me know.

Honest mistake. At the time, capitalization of this street name was inconsistent on OSM, so I went with the one I thought would be more common. I didn't think to check street-level imagery or official sources. Feel free to fix.