Sample geodata
Geodata from field to decision – standardised, versioned & critical-infrastructure-ready.
Consistent layers & symbology · Full version history · Operated locally & auditable
Infrastructure planning depends on datasets that fit together across project and utility boundaries. You receive geodata from surveying, from as-built plans, from network operations and from external planning offices, and every source names and draws its objects differently. Sample geodata (in German: Mustergeodaten) set a shared model against this that every party adopts: a fixed structure, a self-explanatory layer naming and a uniform symbology.
What sample geodata contain
Sample geodata are a standard-conformant reference model with populated, validated example data. They show on a validated dataset what structure, naming and representation look like, and can be adopted as a starting point for your own holdings. Five components belong to it:
- Data model — standard-conformant object types, attributes & relationships that define the content structure of the holdings.
- Layer naming — a self-explanatory naming convention, identical in every project. The layer states what it contains on its own, without you needing the source's project knowledge.
- Symbology — a fixed signature & legend, delivered in QGIS as a symbol catalogue per utility (style files). Identical objects look identical in every project.
- Example datasets — the model populated, not empty, so that structure, naming and representation can be read off and adopted.
- Validation rules — the reference as the benchmark against which a real dataset is validated before admission.
Why this matters in infrastructure planning
In infrastructure planning, the order within the holdings decides the effort of every handover. Electricity, gas, water, heat and telecommunications are named and symbolised differently in every office, and as soon as a dataset moves from planning to the operator, from the operator to the engineering office, or from one cycle into the next, the handover turns into a translation. This is exactly where the reference comes in: a fixed naming & symbology across all utilities makes the holdings readable without follow-up questions. It also feeds into BIM-GIS integration, because a consistent structure is the precondition for the specialist model and the geodata holdings to reference one another.
Where sample geodata sit in the geodata cycle
Sample geodata sit in phase 2 of the geodata cycle, in validating and preparing. The reference is the benchmark against which a dataset is checked before it counts. The benefit reaches across all four phases: your site visit with MoversSurvey already captures into the correct layers, MoversWebGIS shows the validated data on the map in the office, your analysis with Kermit GeoAI becomes comparable across several datasets, and your measures in phase 4 stay within the same schema. In our view the effect in phase 3 is the strongest: Kermit GeoAI answers spatial questions reliably across projects only when naming and symbology are the same everywhere.
→ View use cases for this phase
How new data stays conformant
The reference is held in a central repository: model, style files & validation rules sit in one place, from which every project draws the same version. When a new dataset is added, it is checked against this repository for conformity before it is admitted, and specifically in QGIS with the delivered styles and validation rules, that is, in the tool you work in anyway. Naming & symbology therefore stay the same across every point of entry, and the same validated basis is later available to Kermit GeoAI, which accesses the same holdings natively in QGIS.
How we set up sample geodata
We set up sample geodata together with you, starting from the relevant standards of your sector (ÖNORM, INSPIRE, OGC) and from the holdings you already keep. We contribute to the ongoing development of these standards in the Austrian Standards Committee 084 (Geoinformation and Surveying). The basis is also our work on network holdings in infrastructure planning, from which the naming and symbology logic grew. You receive a model that integrates your existing tools and supplements the missing ones, including example data and validation rules for immediate onward work.
What follows afterwards
An existing dataset is transferred into the reference through our requirements engineering and migration: the migration delivers into the model, the model is the target picture of every migration. After that, our services accompany the rest of the cycle: tenders and procurement, requirements and migration, and operations and maintenance.
In your next project you then have a dataset that every office, every operator and every analysis reads without a follow-up question. To get started, arrange a free initial consultation.
Arrange a free initial consultation →
