Skip to content
PointSav Digital Systems

PointSav GIS engine

← All revisions

317daf72 · PointSav Digital Systems ·

editorial sweep: GIS batch — location-intelligence platform + UX + gis-engine + guide-totebox (attribution cleanup, structural comparison removed)

View the full record as of this revision →

@@ -17,6 +17,7 @@ cites:
  - tippecanoe-tool
---

# PointSav GIS Engine

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.

@@ -25,7 +26,7 @@ The PointSav GIS Engine is a high-performance, sovereign Location Intelligence p
The engine is engineered to operate as a stateless application surface, adhering to the PointSav principle of complete data sovereignty. 

### 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 (e.g., PostGIS, Esri) which 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
The platform avoids commercial SaaS mapping dependencies by utilizing a high-performance, open-source rendering stack:
@@ -46,19 +47,11 @@ The engine's core logic resides in the `app-orchestration-gis` service. This 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.

## See Also

- Totebox Orchestration GIS operations guide (planned — `guide-totebox-orchestration-gis`)
- Co-location Methodology (planned — `co-location-methodology`)
*   [[guide-totebox-orchestration-gis]]
*   [[co-location-methodology]]

---
## Provenance
- **Draft Source:** `topic-pointsav-gis-engine.md` (project-gis)
- **Refinement:** 2026-05-02 by project-language Task
- **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/).*

*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.*
Important Information

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is a trade name of Woodfine Capital Projects Inc. ("Woodfine"). PointSav does not itself offer, sell, or solicit any security. Any securities offering associated with Woodfine's real-property direct-hold solutions is made exclusively by Woodfine, and only by means of the applicable Private Placement Memorandum.

No investment advice. This wiki's content is provided for engineering, operational, research, and development purposes. Nothing on this wiki constitutes investment advice or a solicitation to invest in any Woodfine partnership or direct-hold solution.

Intellectual property. The PointSav name, trade name, wordmark, and marks, together with all current and future PointSav- and Totebox-branded products, services, and offerings — and the software, source code, documentation, design system, and all related materials — are proprietary to Woodfine and its affiliates, except for components identified as open source. No rights are granted except as expressly set out in a written license or agreement. See TRADEMARK.md in this repository for the full trademark notice.

Open source components. Portions of the platform are made available under permissive open-source licenses identified in the accompanying repository. Use of those components is governed by their respective license terms.

No warranty; informational use. Content on this wiki is provided for general informational purposes only and does not constitute a representation, warranty, or commitment with respect to product functionality, availability, pricing, or roadmap. Some articles describe planned or intended features, capabilities, and milestones — language such as "planned," "intended," "targeted," "may," and "expected" marks this forward-looking content, which is subject to change and does not constitute a commitment regarding future performance.

Confidentiality. Where an article describes an operational or deployment detail that is not intended for public disclosure, that article is not published on this wiki. Content here is general-purpose engineering documentation, not customer-specific configuration.

Jurisdiction. Woodfine Capital Projects Inc. is organized in British Columbia, Canada. References to the Sovereign Data Foundation on this wiki describe a planned or intended initiative only, not a current equity holder or active governance body.

Changes to this notice. PointSav may update this notice from time to time; the version posted on this page governs.

Not a filing system. This wiki is not a securities filing system, an electronic disclosure repository, or a substitute for SEDAR+ or any other regulatory filing system. Formal securities filings are made through the applicable regulatory filing system, not through this wiki.

Full disclaimer. This notice supplements, and does not replace, the full Disclaimers article. In the event of any conflict, the full Disclaimers article governs.

Read the full disclaimer →