Incidentally, the Mapbox Navigation SDK is open source, and so is the routing software that powers it:

https://github.com/Project-OSRM/osrm-backend/
https://github.com/mapbox/mapbox-navigation-ios/

I understand that it’d be inappropriate to tailor our mapping to any particular router, but we still need to take into consideration the needs of data consumers (and end users) in general.

No, that’s not at all what I’m saying. Just to be clear, I believe we’re talking about these signs:

https://www.flickr.com/photos/navymailman/5637080430

As opposed to these signs, which I think do call for using the name tag:

https://thumbs.dreamstime.com/t/sign-pacific-coast-highway-california-52305409.jpg

The difference is that it isn’t practical to identify the highway by “CHP Officer John Pedro Memorial Highway”. Not only is the name unusually long, but it’s also posted too sparsely for someone to use on the ground. If someone comes in from Riverside Dr. and leaves on Green Valley, they’ll never see this name:

https://www.mapillary.com/map/im/wSEpEKjppPynptwQrp6XvA

If we use the name tag, a user of OSM-based navigation software (corporate or otherwise) might well miss a turn trying to get onto Highway 1.

My suggestion (and what I ended up doing in changeset/50044505) was to move Officer Pedro’s name to the official_name tag. A renderer, geocoder, or router can choose to make use of official_name. In fact, several applications do use this tag. Perhaps they give official names more appropriate treatment when they’re in the official_name tag:

https://taginfo.openstreetmap.org/keys/official_name#projects

Finally, please don’t interpret my remarks here as a sort of corporate takeover. I’m still a volunteer mapper by night, even if I happen to work by day on software that relies on OSM. (For the record, I was working elsewhere on non-OSM software in 2012.) I brought up Mapbox because I’m sensitive to how OSM is used in the real world and want to ensure that ultimately end users are best served by the choices we make here. I hope we agree on that point.

Haha, no, I’m not stalking you! :-D A coworker of mine pointed out how the Mapbox Navigation SDK was trying to say, “Continue on CA 1, CHP Officer John Pedro Memorial Highway, for 14 miles”. It took almost 7 seconds to say this mouthful, and the corresponding label in the UI shrank to a tiny font just to fit it all in there.

You’re right that the signs bearing Officer Pedro’s name are posted along the highway, but it’s not nearly as frequent as the Highway 1 shield, is it?

The official_name tag is… official:

official_name=*
https://taginfo.openstreetmap.org/keys/official_name

Back in 2012, Foursquare switched to OSM, and a prominent Foursquare superuser had only nice things to say – except the unwieldy official names I had placed on the map, especially “Staff Sergeant Matt Maupin Veterans Memorial Freeway”. It was then that I finally came around to using the official_name tag:

https://web-beta.archive.org/web/20120321012448/http://aboutfoursquare.com/after-just-three-weeks-foursquare-launches-major-improvements-to-their-maps/

An alternative to putting Officer Pedro’s name on the highway would be to map the signs themselves as historic=memorial POIs.

While “CHP Officer John Pedro Memorial Highway” may be signposted in a few spots, it isn’t signposted prominently or frequently enough for general usage. changeset/50044505 moves it to the official_name tag and restores “Cabrillo Highway”, which is the legislatively defined name for the entire stretch of freeway.

Incidentally, this specific name came up as an argument for eliminating highway names entirely while testing navigation software at Mapbox. That would be unfortunate, because the name tag is where you also find “Pacific Coast Highway” and the like.

Construction won’t begin until late 2018: http://www.bizjournals.com/sanjose/news/2017/01/23/are-you-ready-for-a-subway-digging-for-bart-begins.html

Reverted in changeset/49904054. Please let me know if you have any questions.

Phase II of the BART Silicon Valley project has not yet begun construction. In fact, funding hasn’t even been fully secured for it yet.

Thanks for your contributions! As you add stoplines, please remember to connect them to the roadways, as that would be more topologically correct.

In fact, since most roadways in OSM are modeled as lines rather than areas, most existing software prefers that stopping positions be mapped as [highway=stop](https://taginfo.openstreetmap.org/tags/highway=stop) nodes rather than [highway=stopline](https://taginfo.openstreetmap.org/tags/highway=stopline) ways. However, mapping the stoplines as lines is an interesting experiment, and I’m curious as to how you envision this data being used.

Also added or adjusted several businesses downtown.

Thanks!

Thanks for this contribution. FYI, OSM isn’t allowed to accept data derived from Google Maps due to copyright issues, although it’s OK to use it to corroborate information you obtain through other means. It’s unfortunate that the Bing aerial imagery is a bit outdated in this area. The Mapbox imagery is slightly more current, but only enough to see construction beginning on this building. If you need something more current to overlay, consider the 2015 Ohio NAIP imagery at https://gis.apfo.usda.gov/arcgis/rest/services/NAIP/Ohio_2015_1m/ImageServer (click on ArcGIS JavaScript), which is in the public domain. Let me know if you have any questions.

This resolves note #876899.

The GNIS import included some Catholic parish names in the West Side of Cincinnati. Locals will use these names in cases where the parish still exists, but St. Jacob’s no longer appears to be a parish. (St. James is right around the block from this POI.)

(The name of this subdivision, that is.)

Do you know the names of this subdivision, by any chance? Named landuse areas would help to make this part of the map easier to navigate.

These changes have been reverted in changeset/46012761. You’re welcome to add parks and sidewalks to OpenStreetMap, but please make sure they reflect the real world. In experimenting with this part of the map, you moved some streets way out of place, potentially impacting routing. There are plenty of sidewalks around here; if you map them accurately, you’ll probably get better results in Pokémon Go anyways. Please let me know if you have any questions about contributing to OpenStreetMap.

Hi, absolutely – this area could use a lot more Wikidata tags. 😀

I’m a bit puzzled by your addition of <node/4589615728>. The website you tagged doesn’t make it sound like much of a museum.

I undid most of this changeset in changeset/44096514. Don’t use the name field in MAPS.ME to replace a Vietnamese name with a description in Italian. If MAPS.ME lacks a way to add a description in the proper description tag, please find a way to add a note instead of modifying the POI. Thank you.

This changeset replaced the Vietnamese name of this museum an the Italian translation. I fixed the issue in changeset/44096307.

This changeset added the wrong Wikidata entity for Yên Bình. Q8052180 is for a district (huyện), whereas Q10837974 is for that district’s capital town (thị trấn). I’ve clarified the Wikidata entities and also corrected the wikidata tag in changeset/43814653.