Roads: no bridge/tunnel rendering, and the attribute is not imported #18
Labels
No labels
claude-wip
map-report
map:is
map:se
needs-review
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
art/ismap#18
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
All three sources carry it — Iceland
einingvegakerfis(1=road, 2=bridge, 3=ford,4=tunnel, 6=mountain pass, 7=ferry), Sweden
Bro_och_tunnel_Konstruktion, PolandPOLOZENIE— and none of it is imported, because the style has no underpass/overpass drawordering to consume it. Adding the column alone would put bytes in every tile for a
rendering that does not exist.
Adding the attribute and the ordering is one job, not two. Doing it means: a shared
column on the
roadscontract inconf/common.yaml, three per-country mappings, and astyle that splits each road class into below/at/above-grade layers ordered so that a tunnel
passes under and a bridge over.
Worth weighing against the fact that z14 is the current ceiling — at z14 the visual payoff
is modest, and it grows if the ceiling ever rises.
docs/geo-primer.mdrecords this as aknowing gap under "layer order", and that note should be updated if this is done.
Note that Iceland's
einingvegakerfisalso carries ferries (7), which is the subject of#6 — the two would be imported from the same attribute, so consider doing them together.