-
Notifications
You must be signed in to change notification settings - Fork 17
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
Implement 'clip and ship' services #150
Comments
hi @gubuntu or could you give advice how to clip? |
The 'proposed interaction' in the OP describes how to clip from a UX point of view. Use the extents and user choices to construct WFS (vector) or WCS (raster) requests against the GeoNode OWS base url, which will be proxied to the Geoserver or QGIS backend. Ensure you comply with the specification version that the backend supports (e.g. WCS 1.1 vs 1.3) A resource I prepped for raster WCS clipping a while ago (only accessible to Kartoza staff; links contained in it might be out of date): https://docs.google.com/a/kartoza.com/document/d/10DBcHC4tUm1gmd-u38LkhOeWDlejm21ZfdcKTWh5yqU/edit?usp=sharing WFS vector clipping follow similar principles. |
looking good. In your mockup do you click 'download clip' and then draw a polygon? See the OP - the first step is to get the clip working by sending the view extent and using default resolution and format for the response. Sending a polygon (AOI) is more complex and remember in that case that the returned raster will still be a rectangle, but with cells outside the AOI set to nodata. |
Google Leaflet support for WFS and WCS, there seem to be a few projects out there. So you don't have to construct the requests from first principles... It might work getting Leaflet to construct the requests, although we want to download the result, not render it in the map... |
And we want to clip the result with an irregular polygon after the WCS on the server. |
Is it a specific requirement to support irregular polygon clipping? WCS 1.1.1 supports only bounding box clip. So as @Gustry says, we need to intersect the rectangular image and clip with a polygon. some possibilities:
|
We talked about:
|
A suggestion: we pass the custom polygon as an extension to the WCS 1.1 request in the same way as WCS 2. For now we intercept that and remove it from the request behind the proxy so that the custom process can use it, but later when QGIS supports WCS 2 then we won't need to change the request much? |
hi @gubuntu
but
Is the request correct? (using like docs) if it is correct, where can i get the coverage layer? in the frontend, how do we use this coverage parameter? |
Did you create a new project with the OTF plugin latest version? |
hi @Gustry how do i check |
@Gustry
is the coverage that i use is from i tried using that coverage, but got 500, internal server error
|
@meomancer @dimasciput is this up to date? Where is all the latest Haiti clip'n ship activity happening? |
Sorry @meomancer Do you still have the issue? I missed your answer |
hi @gubuntu @Gustry |
test at http://88.99.166.60:33300 |
@meomancer can you do a PR into this repo as well? cc @cchristelis So this just supports clip 'n ship with QGIS server backend (not geoserver)? |
hi @gubuntu |
@meomancer cc @cchristelis please wrap this up asap |
ping @meomancer cc @cchristelis |
@dimasciput will try to merge this as a back-end-agnostic GeoNode tool into KBIMS, then we should automatically get it here |
@gubuntu |
Implement 'clip and ship' services for a selected layer or map (multiple layers) where the user chooses an AOI and gets a zip download containing all the data + metadata for the clip area.
Further technical requirements
Proposed Interaction
cc @cchristelis @lucernae
Standards compliance
According to QGIS docs, 2.14 supports WFS 1.0.0 and WCS 1 1.1.1 so our client must construct compliant requests.
Look on the OGC website for specifications matching these protocol versions if you need a reference for constructing requests.
In future it can be extended to query the backend and respond with requests that match supported version. e.g. Geoserver supports more recent versions of WFS and WCS and future QGIS versions might also.
child of #457
The text was updated successfully, but these errors were encountered: