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

Support for WMS layers #192

Open
theoway opened this issue Sep 1, 2022 · 4 comments
Open

Support for WMS layers #192

theoway opened this issue Sep 1, 2022 · 4 comments

Comments

@theoway
Copy link

theoway commented Sep 1, 2022

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.

@theoway
Copy link
Author

theoway commented Sep 28, 2022

Update: GetFeatureInfo is not a good approach. WCS could be integrated with Geoblaze maybe.

@DanielJDufour
Copy link
Member

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 :-)

@acao
Copy link

acao commented Apr 20, 2023

fwiw @theoway, I was able to use geotiff data from a WMS GetMap request with the library:

https://io.apps.fao.org/geoserver/wms/GSOCSEQ/SOCS/v2?srs=EPSG:3857&dim_socsp=SSM1&identifiers=GSOCSEQ:socs&format=image/geotiff&exceptions=application/vnd.ogc.se_xml&service=WMS&version=1.1.1&request=GetMap&layers=SOC_SU&bbox=-5322463.153553393,-2035059.4410645328,-5165920.119625352,-1878516.4071364924&width=256&height=256"

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 GetCoverage that seemed to be the even more raw source data. I think I may have accidentally brought down the FAO WCS with this query so please be careful:

https://io.apps.fao.org/geoserver/wcs?service=WCS&version=1.0.0&crs=EPSG:3857&coverage=GSOCSEQ:socs&request=GetCoverage&bbox=-5322463.153553393,-2035059.4410645328,-5165920.119625352,-1878516.4071364924&format=image/tiff&height=256&width=256&RESPONSE_CRS=EPSG:4326"

(try making the bounding box smaller if this one is very slow)

@DanielJDufour
Copy link
Member

Hi, @acao . Thanks for pushing this forward. GeoBlaze uses georaster to parse any urls, so I'm wondering if it would make sense to add WCS support to georaster?

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

No branches or pull requests

3 participants