Support geobuf sketch parameter to geoprocessing function #294
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
twelch
added a commit
that referenced
this pull request
Jun 25, 2024
* add geobuf geometry to support request param * clean up GeoprocessingRequest types * add geobuf decoding from GeoprocessingRequest
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GeoprocessingHandlerhas always supported sending a sketch as GeoJSON string, directly in event payload, within the 6MB lambda limit. This PR adds support for geometry to be sent in compact geobuf format, using an additionalgeometryGeobufparameter, that expects a geobuf encoded as a base64 text string.fetchGeoJSONnow looks for and uses this parameter first, beforegeometryorgeometryUri. The geoprocessing function continues to just receives it's sketch input in the end, doesn't care or need to know how it was received behind the scenes.