seasketch / geoprocessing

Serverless geoprocessing system
https://github.com/seasketch/geoprocessing/wiki
BSD 3-Clause "New" or "Revised" License
12 stars 2 forks source link

GP / seasketch next integration #121

Open twelch opened 1 year ago

twelch commented 1 year ago

Geoprocessing projects need to support SeaSketch Next and any changes/improvements to the IFrame API. Some of the features may be already implemented and not used, or at least stubbed in the interface.

Requirements

GP client references:

underbluewaters commented 1 year ago

It looks like I was incorrect about SeaSketch not providing the initial layer visibility. Looks like it is passed in the initial message. What's missing is updating the report view's state if the user toggles via the main table of contents. That would require a substantial amount of spaghetti code to support in legacy but shouldn't be a big deal in SSN.

twelch commented 1 year ago

Because seasketch legacy didn't send full sketch properties over the iframe API, for the last few projects gp functions send the full sketch structure (sans geometry to keep it small) back with the metric result. This was very handy for the FSM project, where we needed to inject contiguous zone polygons as extra sketches at the top of the function. Reports were then able to include these zone polygons in the displayed result.

Now that seasketch next sends full sketch properties (to be confirmed), a way forward might be for reports to go back to defaulting to using the full sketch properties passed via the iFrame, but if there is a sketch present in the gp results, then that should override.