Diff: services/pointsav-gis-engine
From c2b7ac9 to c2b7ac9
+0 / −0 lines
| Before | After |
|---|---|
| --- | --- |
| schema: foundry-doc-v1 | schema: foundry-doc-v1 |
| title: "PointSav GIS Engine" | title: "PointSav GIS Engine" |
| slug: pointsav-gis-engine | slug: pointsav-gis-engine |
| category: services | category: services |
| type: topic | type: topic |
| quality: complete | quality: complete |
| status: active | status: active |
| audience: public | audience: public |
| bcsc_class: public-disclosure-safe | bcsc_class: public-disclosure-safe |
| language_protocol: PROSE-TOPIC | language_protocol: PROSE-TOPIC |
| last_edited: 2026-05-02 | last_edited: 2026-05-02 |
| editor: pointsav-engineering | editor: pointsav-engineering |
| cites: | cites: |
| - maplibre-gl-js | - maplibre-gl-js |
| - pmtiles-spec | - pmtiles-spec |
| - tippecanoe-tool | - tippecanoe-tool |
| --- | --- |
| The PointSav GIS Engine is a high-performance, sovereign Location Intelligence platform designed for offline-first, flat-file operation. Built in Rust, it represents a structural departure from traditional, proprietary geographic information systems (GIS) that rely on centralized database instances. | The PointSav GIS Engine is a high-performance, sovereign Location Intelligence platform designed for offline-first, flat-file operation. Built in Rust, it represents a structural departure from traditional, proprietary geographic information systems (GIS) that rely on centralized database instances. |
| ## Architectural Principles | ## Architectural Principles |
| The engine is engineered to operate as a stateless application surface, adhering to the PointSav principle of complete data sovereignty. | The engine is engineered to operate as a stateless application surface, adhering to the PointSav principle of complete data sovereignty. |
| ### Flat-File Substrate | ### Flat-File Substrate |
| Unlike traditional GIS stacks that require persistent database management, the PointSav engine utilizes a flat-file substrate. It consumes geographic data directly from `JSONL`, `GeoParquet`, and `YAML` formats versioned within a Totebox Archive. This architecture ensures the data layer remains entirely decoupled from the application logic, eliminating database maintenance overhead and preventing vendor lock-in. | Unlike traditional GIS stacks that require persistent database management, the PointSav engine utilizes a flat-file substrate. It consumes geographic data directly from `JSONL`, `GeoParquet`, and `YAML` formats versioned within a Totebox Archive. This architecture ensures the data layer remains entirely decoupled from the application logic, eliminating database maintenance overhead and preventing vendor lock-in. |
| ### Sovereign Rendering Stack | ### Sovereign Rendering Stack |
| The platform avoids commercial SaaS mapping dependencies by utilizing a high-performance, open-source rendering stack: | The platform avoids commercial SaaS mapping dependencies by utilizing a high-performance, open-source rendering stack: |
| - **PMTiles:** A single-file archive format for tiled data that enables maps to be served directly from standard web servers (Nginx) or blob storage without a dedicated tile server. [pmtiles-spec] | - **PMTiles:** A single-file archive format for tiled data that enables maps to be served directly from standard web servers (Nginx) or blob storage without a dedicated tile server. [pmtiles-spec] |
| - **MapLibre GL JS:** A WebGL-based library for rendering interactive vector maps with high client-side performance. [maplibre-gl-js] | - **MapLibre GL JS:** A WebGL-based library for rendering interactive vector maps with high client-side performance. [maplibre-gl-js] |
| - **Tippecanoe:** A tool used to compile massive flat-file datasets into optimized vector tiles, ensuring rapid delivery of complex co-location clusters. [tippecanoe-tool] | - **Tippecanoe:** A tool used to compile massive flat-file datasets into optimized vector tiles, ensuring rapid delivery of complex co-location clusters. [tippecanoe-tool] |
| ## Spatial Processing and Orchestration | ## Spatial Processing and Orchestration |
| The engine's core logic resides in the `app-orchestration-gis` service. This component executes the Woodfine co-location methodology deterministically: | The engine's core logic resides in the `app-orchestration-gis` service. This component executes the Woodfine co-location methodology deterministically: |
| 1. **Ingestion:** Reads retail and civic infrastructure records from the Totebox Archive. | 1. **Ingestion:** Reads retail and civic infrastructure records from the Totebox Archive. |
| 2. **Analysis:** Executes spatial joins and proximity queries to identify co-location clusters across 1.0 km, 3.0 km, and 5.0 km radii. | 2. **Analysis:** Executes spatial joins and proximity queries to identify co-location clusters across 1.0 km, 3.0 km, and 5.0 km radii. |
| 3. **Ranking:** Applies the 12-rank named-anchor matrix to generate site quality tiers. | 3. **Ranking:** Applies the 12-rank named-anchor matrix to generate site quality tiers. |
| 4. **Serialization:** Outputs the processed results as tiled data for the visual interface at [gis.woodfinegroup.com](https://gis.woodfinegroup.com). | 4. **Serialization:** Outputs the processed results as tiled data for the visual interface at [gis.woodfinegroup.com](https://gis.woodfinegroup.com). |
| This stateless approach ensures that the entire GIS environment can be re-provisioned instantly from the immutable data layer, providing maximum service resilience and auditability. | This stateless approach ensures that the entire GIS environment can be re-provisioned instantly from the immutable data layer, providing maximum service resilience and auditability. |
| ## See Also | ## See Also |
| - Totebox Orchestration GIS operations guide (planned — `guide-totebox-orchestration-gis`) | - Totebox Orchestration GIS operations guide (planned — `guide-totebox-orchestration-gis`) |
| - Co-location Methodology (planned — `co-location-methodology`) | - Co-location Methodology (planned — `co-location-methodology`) |
| --- | --- |
| ## Provenance | ## Provenance |
| - **Draft Source:** `topic-pointsav-gis-engine.md` (project-gis) | - **Draft Source:** `topic-pointsav-gis-engine.md` (project-gis) |
| - **Refinement:** 2026-05-02 by project-language Task | - **Refinement:** 2026-05-02 by project-language Task |
| - **Verification:** Architectural details and rendering stack confirmed against `app-orchestration-gis` build configuration. | - **Verification:** Architectural details and rendering stack confirmed against `app-orchestration-gis` build configuration. |
| --- | --- |
| *Copyright © 2026 Woodfine Capital Projects Inc. Licensed under [Creative Commons Attribution 4.0 International](https://creativecommons.org/licenses/by/4.0/).* | *Copyright © 2026 Woodfine Capital Projects Inc. Licensed under [Creative Commons Attribution 4.0 International](https://creativecommons.org/licenses/by/4.0/).* |
| *Woodfine Capital Projects™, Woodfine Management Corp™, PointSav Digital Systems™, Totebox Orchestration™, and Totebox Archive™ are trademarks of Woodfine Capital Projects Inc., used in Canada, the United States, Latin America, and Europe. All other trademarks are the property of their respective owners.* | *Woodfine Capital Projects™, Woodfine Management Corp™, PointSav Digital Systems™, Totebox Orchestration™, and Totebox Archive™ are trademarks of Woodfine Capital Projects Inc., used in Canada, the United States, Latin America, and Europe. All other trademarks are the property of their respective owners.* |