-
Notifications
You must be signed in to change notification settings - Fork 28
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
Support for WMS layers #192
Comments
Update: GetFeatureInfo is not a good approach. WCS could be integrated with Geoblaze maybe. |
Hi, @theoway . Thanks for pushing this discussion forward. I have to think about it more before responding more substantively, but just wanted to say thank you :-) |
fwiw @theoway, I was able to use geotiff data from a WMS
computing stats from a derived visualisation like this is less desirable of course, because you have to map the colorized values back to actual values. some WMS servers allow requesting unstyled data, but this one did not. I was also able to use geotiff data from a WCS URL using
(try making the bounding box smaller if this one is very slow) |
Is your feature request related to a problem? Please describe.
There is no documented way to use
geoblaze
with WMS. This is a very important use case as raster data is generally large in nature and usually served through WMS.Describe the solution you'd like
One should be able to use geoblaze with WMS. Instead of passing the file url, one can pass the WMS url and get results.
Describe alternatives you've considered
No alternatives considered yet. Looking for some way to do stuff on client-side, if geoblaze can deal with WMS, that'd be awesome.
Additional context
GetFeatureInfo
can help to get actual pixel values. This can be integrated into the code.The text was updated successfully, but these errors were encountered: