Preparing a UPME storage model begins before exporting files. The team needs to identify the applicable scope, map every source to its corresponding layer and attribute, normalise domains, transform coordinates with traceability and review metadata. The official deliverables identified by the instrument are SHP or GDB in EPSG:9377. GeoJSON can support local geometry and attribute diagnostics, but it does not replace those formats.
Fix the source of truth before transformation
Consult the official UPME storage model page and the current instrument for the project type. The editorial register identifies External Circular 000037 of 2026 and MME Resolution 40358 of 2025 for their stated scope. Do not apply a template by analogy to projects outside that scope or turn a historical date into a current countdown.
Maintain a transformation ledger for every dataset: source hash and CRS, model version, class and field correspondence, applied domain, responsible reviewer and check result. Keep rules that populate or derive values separate from manual corrections. Test the mapping first with records containing nulls, relationships and complex geometry, then run it on the full set and compare counts, extent and keys. Produce the official SHP or GDB from that controlled copy and rerun checks on the exported artefact, not only on an intermediate GeoJSON.
Recommended sequence
- Verify. Download and version the official package, dictionary and documents applicable to the project.
- Map. Build a source-to-target matrix for layers, fields, domains, units and required status.
- Prepare. Normalise identifiers and relationships before reprojection or delivery-format conversion.
- Check. Transform to EPSG:9377 while retaining source CRS, operation and spatial controls.
- Close. Produce SHP or GDB, complete metadata and rerun checks on the exported artefact.
Minimum control evidence
The technical preparation record should retain:
- documented official version and scope.
- complete source-to-target correspondence.
- domains without improvised values.
- feature counts and extent compared before and after export.
What the diagnostic cannot promise
A file that opens is not proof of conformance. Shapefile has limits on names, types and length; a geodatabase preserves more structure but can still contain incorrectly applied domains or relationships. GeoSAT’s prevalidator finds signals and produces a summary; it is not an official UPME tool, does not guarantee acceptance and does not modify the visitor’s original file.
Review the specialised GeoSAT service to define scope and the related cluster to identify interoperability, environmental or territorial dependencies. This guide is informational; service pages explain evidence, tooling and an appropriate next step without promising an official decision.
