(This only affects the Vietnamese name.)

Hi, thanks for your interest in this park. This building is a picnic shelter, not a house. No one can live here. You can see in Bing Streetside imagery that there are no walls, only a roof over a concrete slab floor and a picnic table inside. In general, a building inside a park is unlikely to be a house, though there are exceptions. osm.org/changeset/168747793 reclassifies this building.

Hi, osm.org/changeset/168580613 removes these name tags. The route relation is already tagged network=US:OH and ref=11, which is sufficient for data consumers to format it as OH-11 if they really want. As far as addressing, the USPS recognizes a number of different formats for numbered highways [1], but “State Route #” is the canonical one per ODOT and county addressing systems.

[1] https://pe.usps.com/text/pub28/28apf.htm#ep79483

Hi, your addition of a ref tag to the Peña Boulevard route relation is apparently causing some renderers to think this route is numbered “Peña” despite already belonging to a route network all its own. You also cited an image on Wikimedia Commons that might be misleading people to think it’s a route shield:

https://github.com/osm-americana/openstreetmap-americana/pull/1214#issuecomment-3034717224

The rule of thumb is that OSM maps anything that still exists based on observation, while OHM maps anything regardless of when it existed (past, present, or future) based on research. This subway tunnel still exists, but the stations only exist as clues like platforms and setbacks in the walls. It’s perfectly normal for something to be represented in both projects, but it might be described differently in either.

The subway itself definitely belongs in OSM as railway=abandoned and ideally man_made=tunnel. The stations are iffier, but at least general-audience maps won’t mislead their users if you use abandoned:railway=station instead of railway=station.

There are actually two OpenRailwayMap sites these days. The one at https://www.openrailwaymap.org/ is no longer maintained and doesn’t support any tagging scheme for abandoned stations that I know of. The more modern one at https://openrailwaymap.app/ doesn’t show the Cincinnati Subway at all, because it gets its historic railways exclusively from OHM, which doesn’t have the subway yet but really should.

This subway is a bit of an oddball, since it was only ever under construction. In OHM, we’d probably end up mapping railway=construction from the 1900s to the 1920s, followed by railway=abandoned (plus man_made=tunnel). The station would similarly be construction:railway=station followed by abandoned:railway=station. If the newer ORM doesn’t show the stations with these tags, then we should be able to get the developers to fix that much sooner than with the older ORM.

Hi, I see that you attempted to keep OSM data consumers from misinterpreting the planned subway stations as active subway stations, but you need to use abandoned:railway=station or something like that. Otherwise, every data consumer currently thinks these are active subway stations, because they understand railway=station but not abandoned:railway=yes.

More generally, I think you’ll find that OSM is not a great home for information like this. We have a sister project, OpenHistoricalMap, that focuses more broadly on the past and present. It covers the Miami & Erie Canal [1] and Central Parkway but currently lacks the subway infrastructure, which would be more than welcome there. I dug up some references you could use for determining which parts of the proposed southern leg were built. [2]

In the meantime, would you mind at least retagging these stations or preferably deleting them, so they don’t mislead people looking for public transit directions? Thanks for understanding.

[1] https://www.openhistoricalmap.org/#map=17/39.107994/-84.515934&layers=O&date=1920-01-01&daterange=1788-01-01,2025-12-31
[2] https://community.openstreetmap.org/t/verifying-the-southern-leg-of-the-cincinnati-subway/115820

The Hamlet preset is for small rural communities. osm.org/changeset/168420838 merges the name into the existing brownfield area representing the razed neighborhood.

Yeah, I figured as much, so I only mapped those “rails” as not:railway=rail to clarify for mappers using Esri imagery that they weren’t looking at actual tracks. Admittedly it’s just a novelty.

Take a look at Esri World Imagery (2022 vintage). This playground used to be marked with a baseball field and some sets of railroad tracks, all painted. All of it was replaced by a soccer field as of 2023, but I strongly suspect that the painted railroad tracks indicate the precise location of the subway lines below the playground. What do you say we move the subway lines there and delete the not:railways?

Yes, it looks like labels for other things are colliding with it and take precedence at other zoom levels due to limited space. Maps tend to prioritize labels based on size. A subdivision of this size is unlikely to be labeled very prominently, but you’ll have more luck with a larger subdivision, such as Chalets or Valley Lake Estates nearby.

Hey, I noticed this addition from your comment in https://github.com/gravitystorm/openstreetmap-carto/issues/104#issuecomment-2960676006. Is The Basin a residential subdivision? If so, consider retagging this way as landuse=residential instead of as a boundary. OSM Carto and some other maps will give it a nice background fill and label.

Addresses are from https://gis.countyofnapa.org/portal/apps/webappviewer/index.html?id=0bbafe490c58430da719ff851c78b7fa

Also added some traffic signs at the Napa County line about the glassy-winged sharpshooter.

Brave of you to rely solely on landuse=education instead of dual-tagging the grounds with amenity=school so that it still appears on OSM Carto. 💪

This was also based on a field survey in 2022.

OK, thanks, I did a find-and-replace in changeset 164907952. If we can map enough of these, I think there’s a decent chance of restoring the American spelling as part of https://github.com/openstreetmap/id-tagging-schema/issues/1515

See the discussion in changeset 162094261.

traffic_sign=neighborhood_watch is an American spelling; I’ve been using neighbourhood_watch instead, with an extra u. Do you think we should switch to that spelling, or use a different tag entirely?

https://community.openstreetmap.org/t/neighbourhood-watch-signs/128215/5

Ah, that makes sense. I hope eventually the community will coalesce around one of the tags so software can better support it. For what it’s worth, the uncommon tags warning is good at catching typos or opportunities to align to more common terms (especially British English terms that Americans don’t know), but I think there’s a more specific warning for deprecated tags.