Skip to content
GEOSAT
Back to blog
ORDENAMIENTO
ORDENAMIENTO2026-08-31GEOSAT10 min read

Life Areas in Colombia: how to delimit, georeference and publish them under Resolutions 1491 and 0358

A GIS guide for municipalities and districts to delimit, document and publish Life Areas, and for companies to prepare their programmes without confusing formulation with material compliance.

Life Areas ColombiaResolution 1491 of 2025Resolution 0358 of 2026Law 2173 of 2021municipal GIS

Colombia’s Life Areas need to become verifiable polygons rather than place names in a document. For a municipality or district, the technical path is to identify potential areas, validate restrictions and tenure, delimit the geometry, document sources and methods, publish the required cartography and retain evidence for progress reporting. For a company, the immediate task is to formulate a programme with scope, resources and traceability, but planting and programme submission are not materially enforceable while the relevant jurisdiction has no delimited and published Life Areas.

This guide interprets the official texts reviewed through 31 August 2026. It does not replace legal review or coordination with the competent authority.

What Resolution 0358 of 2026 changed

Resolution 1491 of 2025 implemented Law 2173 of 2021 and allocated responsibilities among municipalities and districts, environmental authorities, medium-sized and large companies registered in Colombia, and other actors. Article 6 assigns municipalities and districts the delimitation and publication of Life Areas. Publication includes a .shp file prepared in accordance with the technical annex and a graphical output showing all delimited areas.

Resolution 0358 of 16 April 2026 amended the deadline and clarified the transition. The maximum period for delimitation and publication is 18 months from the resolution’s entry into force. Municipalities and districts must also report progress every two months to the competent environmental authority, while those authorities report quarterly to the Ministry of Environment and Sustainable Development.

The amendment acknowledges that delimitation requires cartographic analysis, land-tenure validation and coordination with territorial-planning instruments and protected-area management. A team should therefore not announce a calculated calendar deadline until it has confirmed the publication and entry-into-force date applicable to its case.

Responsibilities by actor

ActorPrimary responsibilityPractical evidence
Municipality or districtDelimit and publish Life Areas within its jurisdictionGeospatial layer, graphical output, methodological record and publication log
Competent environmental authorityProvide support within its powers and consolidate monitoringOpinions, observations, correspondence and quarterly reports to the Ministry
Medium-sized or large company registered in ColombiaFormulate its programme and implement it when delimited and published areas are availableProgramme, budget, area selection, implementation records and submission
Ministry of Environment and Sustainable DevelopmentGuide implementation and receive monitoring informationResolutions, annexes, guidance, catalogue and national consolidation

The territorial authority retains the power to delimit and publish. A consultant can prepare inputs, perform quality control, document decisions and operate a viewer, but cannot adopt the boundary on behalf of a municipality or independently certify a company’s legal compliance.

A GIS workflow for delimiting a Life Area

1. Inventory sources and restrictions

Gather official cartography and the instruments that constrain the area: administrative boundaries, territorial-planning instruments, ecological structure, protected areas, hazards, land cover, available parcel or tenure information, and determinants issued by competent authorities. Record the responsible organisation, date, scale, coordinate reference system, licence, validity and source URL or file for every input.

The national layer in the Ministry of Environment’s geographic catalogue is distributed as a vector shapefile and declares a 1:100,000 scale. It is a reference and discovery input; that scale should not be represented as a definitive parcel-level delimitation.

2. Identify candidate areas

Build a criteria matrix before drawing. It should state which conditions allow, exclude or refer a location for further review. A spatial intersection can detect a coincidence, but it cannot automatically resolve land rights, regulatory compatibility, ecological restoration suitability or implementation availability.

When two sources differ, retain both geometries and turn the conflict into a documented decision. Do not delete the original input or select a layer because it looks better on screen.

3. Validate with accountable teams

Review candidate areas with the relevant environmental, legal, planning and land or tenure teams. Record who reviewed the candidate, which source they used, what observation they made and how it was resolved. If a decision depends on another authority, keep it pending instead of replacing it with a GIS inference.

Local participation and coordination also need evidence. Minutes, opinions, correspondence and geometry versions should reconstruct why a polygon was included, adjusted or rejected.

4. Delimit and check geometry

Create one geometry for each Life Area using stable identifiers. Before publication, check at least:

  • a declared coordinate reference system and consistent units.
  • valid, closed polygons without empty geometries.
  • no internal overlaps or unexplained gaps.
  • a clear relationship between the geometry, jurisdiction and supporting instrument.
  • area calculated in a reference system suitable for measurement.
  • explained alignment with administrative boundaries, without silent snapping.
  • visible version, cutoff date and technical owner.

The required shapefile is more than a filename extension. The dataset needs its component files, encoding, projection definition, compatible field names and the content specified in Resolution 1491’s technical annex. If the team works in GeoPackage or PostGIS, generate the .shp as a controlled deliverable rather than keeping it as the only master copy.

5. Prepare metadata and traceability

Article 29 of Resolution 1491 refers the database and cartography to the metadata matrix and annexed technical document. Apply those current documents rather than inventing a local template and presenting it as official.

A useful technical record should reconstruct:

  • the source and version of every input layer.
  • selection, clipping, adjustment or generalisation operations.
  • criteria and accountable reviewers for acceptance or exclusion.
  • geometry checks and corrections.
  • the published file, its checksum and publication date.
  • the relationship between the layer, graphical output and submitted reports.

6. Publish for people and systems

Deliver the required shapefile and a readable graphical output with title, jurisdiction, cutoff date, legend, scale, north arrow, coordinate reference system, sources and limitations. Also publish a stable page where residents and companies can identify the current version and download it without relying on a temporary link.

A web map improves access, but it does not replace the download or the corresponding instrument. Bogotá’s Life Areas viewer is a useful reference for cartographic access; each jurisdiction remains responsible for publishing its competent products and context.

7. Report progress and preserve versions

While delimitation is underway, a municipality or district should be able to substantiate its two-month progress reports to the environmental authority: sources gathered, areas under review, outstanding validations, checked geometries and final publication. Do not overwrite prior deliveries. Keep a version sequence so the environmental authority’s quarterly report can rely on verifiable evidence.

What a company can do while delimitation is pending

Resolution 0358 distinguishes programme formulation from material implementation. Companies within its scope can move forward by:

  1. confirming that the company is actually within the regulation’s scope.
  2. defining an accountable owner, budget, covered workforce and documentary traceability.
  3. asking the municipality or district and environmental authority about delimitation status.
  4. preparing area-selection, species and maintenance criteria subject to competent validation.
  5. designing location, date, accountable-person and implementation-evidence records.

A planting on any parcel should not be recorded as automatic compliance with Law 2173. Resolution 0358 states that material planting and programme submission are not enforceable while no delimited and published Life Areas are available, without prejudice to programme formulation. Once an area becomes available, the company needs to check the official version and coordinate the applicable implementation.

Errors that weaken publication

  • Using a national-scale layer as a parcel boundary. The declared scale limits the detail the data can support.
  • Publishing only a PDF. Resolution 1491 also requires a .shp file in accordance with the annex.
  • Delivering a shapefile without context. Geometry without projection, metadata, sources and version is not auditable.
  • Resolving legal conflicts through an intersection. GIS identifies coincidences; the competent authority or team decides how to treat them.
  • Confusing formulation with implementation. The 2026 transition permits programme preparation while conditioning material enforceability on published areas.
  • Promising compliance or certification. A cartographic product is technical evidence, not an administrative decision or legal guarantee.
  • Hiding version changes. Companies, residents and authorities need to know which polygon was current at a given date.

Pre-publication checklist

  • The competent authority and supporting instrument are identified.
  • Every source has an organisation, date, scale, coordinate reference system and version.
  • Relevant tenure and restrictions have been reviewed by the accountable team.
  • Geometries pass validity and topology checks.
  • The shapefile follows the current technical annex and retains its projection.
  • The graphical output matches the published layer.
  • Metadata explains method, scope, limitations and cutoff date.
  • The publication URL is stable and identifies the current version.
  • The record retains prior reviews, files and reports.
  • Public language distinguishes technical support, official adoption and corporate compliance.

Official sources reviewed

GeoSAT can support source inventory, data structuring, quality control and cartographic publishing through its GIS service for territorial planning and POT. Where the scope includes a catalogue, metadata, downloads or interoperable services, review the geospatial interoperability service. The technical deliverable supports a competent decision; it does not replace official delimitation or certify compliance with Law 2173.

Related articles