There’s some additional discussion about this stopline mapping effort in the thread starting at <https://lists.openstreetmap.org/pipermail/talk-us/2017-September/017821.html>.

This changeset inadvertently duplicated most features in downtown San José. Reverted in changesets 52315977 and 52316818. Everything appears to be back to normal. 👍

Typo: that should’ve been Almaden, not, “Los Amaden”, in the changeset comment.

Hi Doug, note that the maxspeed tag is in kilometers per hour by default. If you want to express a speed limit in miles per hour, please indicate the unit, e.g., maxspeed=25 mph. Thanks!

The newest aerial imagery available was Bing from a year ago, so I reached out to Niederman Family Farm on Facebook asking permission to use <https://nebula.wsimg.com/01699009e4320ed6fb661a0d4f3de60e?AccessKeyId=870A82DEF36C14F24C71> (from their homepage) as a source, and they agreed.

Since the available imagery providers are years out of date, I used <https://www.facebook.com/WendelFarms/photos/a.602837743081207.1073741829.602316163133365/1662595113772126/?type=3&theater> as the source for this changeset. Before starting this changeset, I contacted Wendel Farms on Facebook, asking for permission to use this photo for mapping their corn maze, and they agreed.

Fixed in changeset 51598525.

Hi Edward, thanks for your contributions to OSM! Always happy to see more Cincinnatians around here. :-)

I noticed that you added a driveway but connected it to a power line. Since the two features aren’t connected in reality, please avoid connecting them to OSM. If you make an accidental connection, you can disconnect the two features by right-clicking on the intersecting node in iD, then choosing Disconnect or Delete.

Please let me know (either here or in a private message) if you have any questions about contributing to OSM. Thanks again!

FWIW, a software fix is being tracked in <https://github.com/opentripplanner/OpenTripPlanner/issues/2471>.

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:

osm.wiki/Key: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.