-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Add contour source #623
base: main
Are you sure you want to change the base?
Add contour source #623
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #623 +/- ##
==========================================
+ Coverage 92.23% 92.54% +0.31%
==========================================
Files 100 105 +5
Lines 4196 4666 +470
Branches 1203 1316 +113
==========================================
+ Hits 3870 4318 +448
- Misses 326 348 +22 ☔ View full report in Codecov by Sentry. |
I'll leave this open as a draft as I implement the gl-js side of this. |
This looks great overall, the only question left is the expression for the intervals and multiplier. |
build/expressions_patrial.md
Outdated
@@ -0,0 +1,136 @@ | |||
# Expressions | |||
|
|||
The value for any `layout property`, `paint property`, or `filter may be specified as an _expression_. An expression defines a formula for computing the value of the property using the _operators_ described below. The set of expression operators provided by MapLibre includes: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please use `filter` rather than `filter
@msbarry any updates on this? Is there something I can help with? |
I was planning to keep this open as I implement the maplibre-gl-js side of it in case I have to make any changes here. I got a bit sidetracked trying to get a planetiler release out with parquet/overture support but should have that wrapped up soon so I can get back to this. My in-progress changes to maplibre-gl-js are here: https://github.com/msbarry/maplibre-gl-js/tree/contour-source - I have it working but it's pretty inefficient (overfetching a lot of tiles) and doesn't handle adding border pixels yet. Need to do some more thinking about how to handle those... It might make sense to refactor source_cache first to decouple staging the tile pyramid for a source consumer from fetching/caching tiles if you had any ideas there? I think if terrain and hillshading could read from the same source, then it should be ready for contour tiles to read from it as well. |
No rush, just wanted to make sure you haven't forgot about it 🙂 |
@msbarry where are we with this? |
I'm still hoping to do this eventually, but it's gotten bumped further down my todo list in the short term 😞 I had been thinking of this as a purely additive thing. The only change to existing functionality would be if I can fix source cache and remove the need to define the same DEM source twice to use across terrain and hillshading, but that's just a convention change, not breaking. Was there anything you were thinking? |
I'm not sure what we need to break if at all in order to implement this feature. I recall stuff that might be related to source cache, although source cache is not a public API, but still. |
Add a new source type that generates contour isolines from raster-dem sources.
Fixes #583 - see that issue for the full design and discussion.
Launch Checklist
CHANGELOG.md
under the## main
section.["zoom"]
as an argument