GIS for energy planning
We prepare geospatial models, manifests, layers and traceability for generation and transmission projects before UPME or ANLA submissions.
PRIMARY INTENT
GIS consulting for UPME energy projects
BUYERS
Energy project developers · Environmental and land teams · Engineering and consulting firms
EDITORIAL REVIEW
2026-10-18
Geospatial information for an energy project should be traceable from its source and design alternative to the package reviewed by an authority. We structure that path for generation and transmission projects, coordinating technical, environmental, land and mapping components. The service aims to reduce internal rework and find gaps early; it does not promise approval or replace any UPME, ANLA or other competent-authority procedure.
A shared foundation for different teams
We begin with an inventory of layers, tables, drawings and studies. Every source records an owner, cutoff date, licence or authorization, coordinate system, scale and applied transformation. We then agree identifiers that connect alternatives, works, easements, constraints, environmental units and documents. This prevents engineering, environmental and land teams from operating on incompatible versions of the same feature.
The model is designed against a verified current instrument, not a legacy template. A correspondence matrix connects requirements to objects, attributes and evidence, with unresolved fields assigned to an owner. Where EPSG:9377 is required, we document source coordinates and transformation methods and retain controls for displacement or mixed CRS. Merely declaring a code does not prove that coordinates are correct.
Review before packaging
The scope can include a data model, dictionary, manifest, file conventions, automated checks, change register and delivery procedure. We examine names, types, domains, identifiers, geometries, extent, duplicates, references and consistency between inventory and files. Findings are classified as internal blockers, interpretation questions or recommended improvements; the authority retains the final decision.
The local prevalidator processes a sample in the browser and does not persist its content. Any exported GeoJSON is a diagnostic representation for inspection and internal exchange, not an official submission format. The anonymized experience across twelve projects provides a repeatable preparation method but does not disclose clients, private outcomes or regulatory decisions.
Selecting the right support
To estimate the engagement, we need the project phase, target authority or process, reference version, file inventory, coordinate systems and target date. Support can range from a focused assessment to team coaching or full structuring with milestone reviews. The proposal separates data correction, transformation, documentation and packaging, with internal acceptance criteria and an explicit list of assumptions to confirm.
VERSIONED REGULATORY REGISTER
Sources and verification date
Ministry of Mines and Energy and UPME
UPME External Circular 000037 of 2026 and MME Resolution 40358 of 2025
in force; initial deadline expired · Technical annex, April 2026
It applies to the scope defined by the resolution. EPSG:9377 and SHP/GDB are deliverables; GeoJSON is used only for local diagnostics.
ANONYMIZED RELATIONSHIP
Twelve prepared energy projects: anonymized experience
Methodological experience across twelve projects prepared for UPME or ANLA processes, without disclosing clients, data, official decisions or private outcomes.
Review scope and limits →LOCAL TOOL
Local manifest and GeoJSON prevalidator
Checks structure, declared CRS, attributes and basic consistency in a sample package. It is a readiness review, not official validation or an acceptance guarantee.
Local processing: the file is not uploaded or persisted. Maximum 10 MB. JSON, GeoJSON or XML depending on the tool.
Expected JSON contract
{
"instrument": "Resolución 40358 de 2025 / Circular 000037 de 2026",
"crs": "EPSG:9377",
"format": "GDB",
"metadata": {
"source": "equipo responsable"
},
"dictionary": "diccionario.xlsx",
"files": [
"proyecto.gdb"
],
"layers": [
{
"name": "proyecto",
"geometryType": "Polygon",
"fields": [
{
"name": "project_id",
"type": "text"
}
]
}
]
}Readiness diagnostic only. It is not certification, official validation or an acceptance guarantee.
CLUSTER GUIDES
UPME geospatial deliverables: preparing the model before export
A method to organise layers, attributes, domains, metadata and traceability before producing SHP or GDB in EPSG:9377 for the applicable UPME scope.
Read guide →EPSG:9377 for energy data: reprojecting with traceability and precision
What to record when transforming energy data to MAGNA-SIRGAS 2018 Origen-Nacional: source CRS, operation, units, controls and final format.
Read guide →CONTEXTUAL RELATIONSHIPS
ANLA geographic storage model
Preparation, review and traceability of MAG deliverables without promising official acceptance.
Geospatial data interoperability
Inventory, metadata, quality, catalogues and OGC services aligned with Colombia’s ICDE framework.
Utility network cadastre
Inventory, topology, quality and data governance for water, sewer, gas and associated utility assets.
GIS for mining
Titles, restrictions, operations, environmental evidence and spatial traceability for mining decisions.
Frequently asked questions
Does the review guarantee acceptance by UPME or ANLA?
No. It reduces observable errors and improves traceability, but each authority applies its current version, procedure and assessment criteria.
Is the generated GeoJSON an official deliverable?
No. It is a diagnostic, interoperable format; submissions must follow the formats and structures required by the current instrument.
When should geospatial structuring begin?
As alternatives and sources are defined, before files accumulate with inconsistent names, coordinate systems, cutoff dates and owners.
COMMERCIAL CONVERSATION · TRANSPARENT QUALIFICATION
Tell us what you need to solve
The answers help prioritise the conversation. The score is not stored or sent until you submit this form.