Skip to content
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

Contours #1925

Open
wants to merge 13 commits into
base: master
Choose a base branch
from
Open

Contours #1925

wants to merge 13 commits into from

Conversation

rwrx
Copy link
Contributor

@rwrx rwrx commented Sep 27, 2019

Add contour lines layer.

It is also needed to modify tilequeue, I will create pull request for it.

I will also modify installation instrucions for vector-datasource for how to add contour data into postgresql database.

@@ -108,6 +108,9 @@
- {$layer: 'water', kind: 'sea'}
- {$layer: 'pois', kind: 'nature_reserve'}
- {$layer: 'water', kind: 'lake'}
# for contours
- _reserved: {count: 10}
- {$layer: 'contours', kind: 'std'}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kind should be contour

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would put this at the very bottom of the file... just above the default value.

These contour in this file are just for the label collisions, which should be least priority. If there are "index" contours (eg with a kind_detail) then those should have priority over generic contours.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated according to your first comment.

- &output_properties
source: {col: source}
min_zoom: {col: min_zoom}
ele: {col: ele}
Copy link
Member

@nvkelso nvkelso Sep 27, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. We generally spell out property names, so elevation here instead of ele, and to match elevation property name which we already use in the pois layer.

  2. Please add documentation for this new optional layer:

  • elevation: Elevation of the contour in meters.

Copy link
Member

@nvkelso nvkelso Sep 27, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Generally we want to assign an index contour that's every say 4th or 5th value... so 0, 20, 40, 60, 80, 100 where 0 and 100 would be index contours. This allows the index contours to be "bold" (or thicker stroke) to establish better visual hierarchy on the map display, and the text can also be styled bold.

So we'll probably need a new transform to assign kind_detail when it's an index contour.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated according to your first comment.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure how to add this new transfor to assign kind_detail. Is this also needed? Because in current styles I am doing this in function in scene styling files.

queries.yaml Outdated
@@ -9,6 +9,7 @@ all:
- boundaries
- transit
- admin_areas
- contours
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would be an optional layer for the mainline build... and a fork could put it into the all grouping.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated according to your comment.

@@ -0,0 +1,2 @@
kind,sort_rank
*,1500
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should go between dam and breakwater, so reserve a slot there, and value more like 224 (with breakwater and other values in there getting +1).

https://github.com/tilezen/vector-datasource/blob/a53f1ef0b54c66da391584e25fa750f8aed1a9c9/spreadsheets/sort_rank/landuse.csv

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated according to your comment.

@nvkelso nvkelso added this to the v1.9.0 milestone Nov 11, 2019
@rwrx
Copy link
Contributor Author

rwrx commented Nov 23, 2019

@nvkelso I have noticed that you have added this pull request and also other pull requests from me to 1.9.0. Which is great, thank you :). You do want to merge this before releasing 1.9.0? Also when is planned 1.9.0 to be released?

@nvkelso nvkelso modified the milestones: v1.9.0, v2.0.0 Apr 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants