Matt
Closing as complete. We'll open individual issues to handle ongoing issues.
@LocoDelAssembly Let's revisit this please. At minimum I think we need one of these options. For reference here are (some) of the fields in question: ``` # locationID: [Not mapped]...
Good call with the consideration for preference/requirement of shapes. @LocoDelAssembly Maybe we need to have Redis caching to speed some aspects of the import up (i.e. once found don't hit...
Closing as duplicate of #3070
All these features exist in the current implementation. Closing for new issues highlighting individual issues.
Unified filter release will let you expliciltly query this, like so:
Closing as done.
# Model ## Base (required) * `geographic_item_id` The ID of a GeographicItem * `name` - string ## Utility * `parent_id` the ID of a Gazetter which encloses(?) this shape. Defining...
> Which shapes for Gazs should be allowed? All. Anything that we can spatially compute with. > Hierarchical data maybe requires more custom imports? Target individual (== flat) records initially....
@LocoDelAssembly can confirm what we are using in production, but you should assume for dev evolution 3.3.6 and PG 15. I'd be happy to push that as far foward as...