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.

Sign up for GitHub

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

Jump to bottom

Better maximumLevel for WebMapTileServiceImageryProvider #2523

Open
pjcozzi opened this issue Feb 27, 2015 · 1 comment
Open

Better maximumLevel for WebMapTileServiceImageryProvider #2523

pjcozzi opened this issue Feb 27, 2015 · 1 comment
Labels
category - terrain and imagery type - enhancement

Comments

@pjcozzi
Copy link
Contributor

pjcozzi commented Feb 27, 2015

maximumLevel defaults to 18, which cuts off high-resolution imagery. We can

  • implement GetCapabilities (perhaps covered in OGC helper #2362?), or
  • just let requests for tiles that don't exist fail, I imagine.
@kaktus40
Copy link
Contributor

kaktus40 commented Mar 2, 2015

Hello,
for information a maxLevel property is defined for WMTS capabilities

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
category - terrain and imagery type - enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pjcozzi @kaktus40