Update how spatial schemas are managed; update zone schema to add spatial index #1492
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.
What does this PR do? 🛠️
This PR modifies how we manage our spatial data schemas and data. The various
spatial-data/sources
file are all updated accordingly.true
if source data should also be reloaded orfalse
if the schema modification is sufficient on its ownmeta
module is updated accordinglyschema
module is added to handle migrating schemasload-shapefile.js
file is modified to be source-agnostic; it can rely on each source plus the schema migration module to handle themselvesOverall, this PR should make zone-based spatial queries a little faster, but it should also make it easier and faster to make schema-only updates to spatial data.