OWN DEMONSTRATOR
GeoSAT OpenGIS: architecture and source registry
An own demonstrator that makes provenance, licence, attribution, cutoff date and version explicit before information is published in a mapping experience.
ENTITY / RELATIONSHIP
GeoSAT
LOCATION
Colombia · web demonstrator
EVIDENCE
Own code, manifests and operational demonstrator
The problem being demonstrated
A viewer can draw a layer without explaining where it came from, whether it may be redistributed or which date it represents. GeoSAT OpenGIS was built to expose those decisions before rendering. Every source authorized for a sample must declare its origin, licence, licence link, attribution, data cutoff, retrieval date, hash and redistribution approval. If that manifest is incomplete, the architecture must not treat the file as an approved sample.
This contract makes provenance a publishing condition rather than a note added at the end. It also separates the remote source, normalized response and versioned local snapshot while retaining the context required to explain what a user is seeing.
How the demonstrator is organized
OpenGIS defines sources through reproducible queries and constrains fields, extent and feature counts for each case. Responses are normalized before reaching the viewer, and upstream failures become explicit states. Available operational contexts include volcanic risk in Cumbal, coffee suitability in Calarcá and a segment of National Route 45A04. They are examples built from identified sources, not consulting outcomes or simulated data presented as real.
The same structure can support inventories of WMS, WFS, APIs, catalogues and institutional files. The goal is not to force every source into one technology. It is to document contracts between producers and consumers: purpose, owner, coordinate system, fields, usage conditions, frequency and expected behaviour when a source changes or becomes unavailable.
What it evidences and what it does not
The demonstrator evidences an in-house capability to register sources, consume them under declared rules, normalize data and present provenance within a working web experience. It also shows that a recoverable alternative needs loading, failure and availability states rather than only a map that works while every provider responds.
It does not demonstrate standards certification, permanent third-party availability, thematic quality for every decision or complete replacement of an existing installation. A GetCapabilities XML may describe declared operations without proving that the service is fast, stable or correct. Formal assessment must examine the source and applicable process.
Using it as an architecture reference
An institution can use this case to discuss an initial registry of five to ten priority sources. Every entry can identify an owner, consumers, licence, cutoff, transformations and availability test. The result is an auditable baseline for deciding what to document, correct, publish or monitor without confusing GeoSAT's own demonstrator with a guarantee about external data.