Thanks for taking care of this too!
See Utah State Highway Ref Tagging for the discussion on this. I think Indiana and Ohio (at least) use “SR” as well.
2 Likes
And? Still wrong…
If you want to continue the discussion on the change to ref=SR XX, I’d appreciate if you would take it to the original discussion on the topic, or make a new post.
Please let this discussion get back to the original questions about classification.
3 Likes
(post deleted by author)
1 Like
It’s been almost one year again, and Utah State Route numbers are still rendered with “SR xx” in a rounded rectangle instead of “xx” in an ellipse.
The Mapbox Streets source hard-codes logic to look for “UT” in way ref=* tags. The OSM community frowns upon that approach. They need to upgrade the map to at least check for “SR” in Utah or, much better yet, consult route relations. Until that happens, any Mapbox-powered map will show generic shields, including the Locator Overlay you’re looking at. You would need to bug someone at Mapbox to look into the issue. Unfortunately, I don’t think they follow this forum closely enough that complaining here would help.
1 Like
That’s exactly what I did. Unfortunately, nothing came out of it.
I’ve reached out to a contact at the company. No guarantees about turnaround time though. Some states like Indiana have been affected by the same bug for many years. The Mapbox Streets source has never been open source, so we don’t have any option other than to keep bugging them about it. In the meantime, a number of alternatives exist, including some that understand route relations.
The issue here is that the Locator Overlay that’s available in iD by default relies on Mapbox. Perhaps we could switch Locator Overlay from Mapbox to something else?
As the name suggests, the purpose of the Locator Overlay is to help you locate the part of the map you want to edit. It’s meant to be crude. Because the overlay is based on the Mapbox Streets source and raster tile technology, it departs from OSM data in a number of aspects and doesn’t even respect the user’s language. I don’t think mappers should rely on this overlay to determine whether a route is modeled correctly, particularly since it’s based on a deprecated method of choosing a shield. If mappers are getting this impression, maybe the overlay should stop showing shields altogether. The stylesheet isn’t open source as far as I know, so we’d have to contact its author directly about making that change.
As for replacing the overlay with something else, we’d need a viable alternative. You could develop one yourself, or you could put out a call for help in a more general forum. You might get better results if you can frame it in terms of something less niche than route shields in a particular U.S. state.
1 Like
I’ve been trying to develop a renderer of my own for some time now. It keeps highway=tertiary colored differently from “minor” roads,[1] abbreviates directionals and types on highway names (or at least tries to),[2] renders busways, highlights expressways, and includes shields courtesy of route relations. Yes, I used OMT for this. So far, I’ve been able to do all of these except for the abbreviating names part. I feel like this should be easy to do since the German Carto style does it, but so far, I haven’t been able to do so.
Okay, here are examples of roads whose shields don’t get rendered properly on Mapbox Streets:
- The Turnpikes of Ohio, Indiana, New York, New Jersey, Pennsylvania, and Florida.
- Historic U.S. Highways (e.g., Historic Route 66) don’t get rendered at all.
- Other “special” highways, like Clark County Route 215 in Las Vegas, Nevada, or the E-470 tollway in Denver, Colorado.
- Moving out of the United States, all of Canada’s highways are rendered with the generic round rectangle. Strangely, Mexico’s Federal Highways (Carreteras Federales) do get proper shields.
Does this count?
We’re getting way off topic for this thread.