-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistency between Natural Earth and OSM road classes #1280
Comments
Just to be sure I've understood this correctly: We want the input features with Should we also remove the |
The intent was to better match the motorway versus trunk "highway" transition between zoom 7 and 8 and OSM and Natural Earth (see images and link below). But you're right – we need to ALSO combine this with Natural Earth's So something more like this (assuming we import the
Here's a view of northern California: |
It looks like we already do pay attention to vector-datasource/yaml/roads.yaml Lines 215 to 244 in 68ad88a
Roughly translated, this is saying:
As far as I can tell, this is essentially the same as the existing algorithm. Although there are 9 expressway For more detail: Here's some screenshots of OSM/NE in this location, mapping highways to red, major roads to blue (darker for (Note that I've applied the appropriate OSMNEComparison |
Yes, single line change in https://github.com/tilezen/vector-datasource/blob/master/yaml/roads.yaml#L233 from:
to:
|
I think the general
kind: highway
part of this was intentional, but possibly not thetype: Major Highway
>kind: highway
. Generally speaking that should have gottenkind: major_road, kind_detail: trunk
.The text was updated successfully, but these errors were encountered: