Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#4563 closed defect (invalid)

MapQuest rendering: issues with ref tags

Reported by: NE2 Owned by: mapnik-team@…
Priority: critical Milestone:
Component: mapnik Version:
Keywords: mapquest Cc:


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: 301 and 601 are U.S. Routes 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: 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: The US 395 shields are on what is tagged ref=US 395 HISTORIC.

Change History (4)

comment:1 Changed 8 years ago by NE2

Priority: majorcritical

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. 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.

comment:2 Changed 8 years ago by Ldp

Resolution: invalid
Status: newclosed

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

comment:3 Changed 8 years ago by Grant Slater

Mapquest stylesheet issues can likely be posted here:

comment:4 Changed 8 years ago by rickmastfan67

Note: See TracTickets for help on using tickets.