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

Ability to control layer visibility based on scale denominator #392

Open
jfbourgon opened this issue Jun 2, 2022 · 0 comments
Open

Ability to control layer visibility based on scale denominator #392

jfbourgon opened this issue Jun 2, 2022 · 0 comments

Comments

@jfbourgon
Copy link

Current issue

GeoTrellis-Server is currently missing a key functionality that would allow to control the visibility of a layer based on scale denominator. The feature would help to control the scale when a layer should be displayed on the map and then prevent the layer to be portrayed at resolution that exceed is native resolution or that make it very small.

See below for examples, based on the Canada Land Cover Map hosted on the following WMS service: https://datacube.services.geo.ca/ows/landcover?service=wms&request=GetCapabilities.
This dataset covers only the Canadian landmass and has a native resolution of 30m.

Over-zoomed

image

Under-zoomed

image

Expected behavior

The GeoTrellis-Server solution should allow to set min-scale-denominator and max-scale-denominator on layer object in server configuration file.

landcover-2010 = {
        type = "rastersourceconf"
        name = "landcover-2010"
        title = "2010 Land Cover of Canada / 2010 Couverture terrestre du Canada"
        source = "gdal+s3://datacube-prod-data-public/store/eo4ce/landcover/landcover-2010-cog.tif"
        min-scale-denominator = 50000
        max-scale-denominator = 300000000

Theses settings should be optional. The layer should always be rendered if omitted, which would align with the current behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants