Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

MapQuest rendering: issues with ref tags #4563

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments
Closed

MapQuest rendering: issues with ref tags #4563

openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments

Comments

@openstreetmap-trac
Copy link

Reporter: NE2
[Submitted to the original trac issue database at 10.47pm, Monday, 10th September 2012]

I see that you're experimenting with two-route overlaps as higher zooms. But there are some issues with the second route being in a circle rather than the correct shield. For example:
http://www.openstreetmap.org/?lat=33.166&lon=-81.147&zoom=9&layers=Q 301 and 601 are U.S. Routes
http://www.openstreetmap.org/?lat=41.752&lon=-85.094&zoom=9&layers=Q 90 is an Interstate
The issue may be related to refs having a space after the semicolon.

Other issues with shields:
SR * (State Route/Road) is now being rendered with a county rectangle rather than the correct state circle: http://www.openstreetmap.org/?lat=40.238&lon=-82.361&zoom=9&layers=Q
Louisiana has parishes rather than counties. So PR * should be treated like CR *. (But Puerto Rico should be cut out of this rule, I suppose.)
"Historic" is not being recognized as a banner: http://www.openstreetmap.org/?lat=33.41594&lon=-117.14475&zoom=16&layers=Q The US 395 shields are on what is tagged ref=US 395 HISTORIC.

@openstreetmap-trac
Copy link
Author

Author: NE2
[Added to the original trac issue at 10.58pm, Thursday, 11th October 2012]

This has begun to show up on higher zooms (above I meant 'lower'). While the overlaps are certainly nice, the wrong shield shape is bad.
http://www.openstreetmap.org/?lat=41.4764&lon=-81.6651&zoom=14&layers=Q
http://www.openstreetmap.org/?lat=42.2603&lon=-71.8064&zoom=14&layers=Q
All the rectangles are tagged SR (state route) and should use the rounded rectangle.

On the plus side, I don't see any error rounded rectangles for Interstates or U.S. Routes, but this may be a consequence of my recent post-"redaction" once-over that removed most spaces after semicolons. Keep up the good work; showing overlaps is important. And four-character routes are now displayed (not for county roads though?).

I'm starting to think perhaps a prefix that has nothing to do with the actual abbreviation (state or route type) may be best, but that's not what trac is for.

@openstreetmap-trac
Copy link
Author

Author: Ldp
[Added to the original trac issue at 9.54am, Tuesday, 16th October 2012]

I don't know where the mapquest map bugtracker is, but it's definately not this one.

@openstreetmap-trac
Copy link
Author

Author: openstreetmap[at]firefishy.com
[Added to the original trac issue at 2.46pm, Tuesday, 16th October 2012]

Mapquest stylesheet issues can likely be posted here: https://github.com/MapQuest/MapQuest-Mapnik-Style/issues

@openstreetmap-trac
Copy link
Author

Author: rickmastfan67
[Added to the original trac issue at 2.49am, Wednesday, 17th October 2012]

NE2, you might want to take a look at this post:

http://devblog.mapquest.com/2012/10/16/terrain-added-to-mapquest-osm-tiles-other-updates/

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant