docs: Document optional geo spatial SQL functions#1743
Merged
Conversation
Document the new opt-in spatial UDF support shipped in spiceai/spiceai#10833: - Add a Spatial SQL Functions section under runtime.params explaining the dual gate (Cargo --features geo on spiced, plus runtime.params.geo: enabled in the Spicepod) and a small ST_Point example.
✅ Pull with Spice PassedPassing checks:
|
|
🚀 deployed to https://2d33a0f5.spiceai-org-website.pages.dev |
|
🚀 deployed to https://1e0a5e20.spiceai-org-website.pages.dev |
lukekim
approved these changes
May 18, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Document the new opt-in spatial UDF support — PostGIS-style
ST_*functions registered viageodatafusion.Source PRs
Changes
website/docs/reference/spicepod/runtime.mdruntime.paramsdocumenting the dual gate (build with--features geoANDruntime.params.geo: enabled) and a smallST_Point/ST_AsTextexample.Test plan
cd website && npm run buildpasses locallygeo) and value (enabled) verified against the source diff (app.runtime.params.get("geo").map(String::as_str) == Some("enabled"))geo) verified against the Cargo.toml additions in the source PR