Skip to content
GEOSAT
← Tibasosa

Activity areas · IGAC 2025 in Tibasosa

Select an area of Tibasosa to inspect codes, labels and observations from activity areas · igac 2025.

1 layer · 9 published map features · Tibasosa municipality · IGAC / Colombia OT · GeoSAT adaptation: domain labels and empty values

Open this query ↗

Tibasosa · Public query

Planning land uses and zoning

Open the map with its prepared layers and select a feature to inspect its attributes.

Query planning and land use →

Query planning and land use at a point

Locate an area and read matching polygons from the integrated layers together. The record retains their codes, attributes, sources and dates; unknown values remain unreported.

  1. Open the viewer and choose the planning query.
  2. Mark a point on the map or query its center. Pan the map to inspect another area.
  3. Compare findings by layer and open their sources. A layer with no matches, awaiting integration or unavailable does not establish an absence of rules.

This is a mapping query by location, not an address search or a legal report. It confirms neither legal validity, permits nor authorized activities; cross-check applicable documents and administrative acts.

Query Tibasosa planning →

What it includes

How to use it

  1. Click “Open this query” to load Activity areas · IGAC 2025 in the viewer.
  2. Select a feature on the map or in the Results list to read its record with attributes, source and date.
  3. Build a thematic map to compare, or open statistics to analyze the loaded data.
  4. Share the view link or export received results with attribution and dates.

Locate the query in Tibasosa

Open the planning example and press “Query map center” to view 45772, “Comercio y servicios”. To filter records, use “View layers and explore the area”, “Inspect and export results”, the Activity areas layer and the Record identifier (OBJECTID) field. Urban areas in Santa Teresa retain that original observation. 45779 and 45780, “Protección ambiental”, retain use 8, Other, and warn of overlap; 61082 and 61083 also overlap other uses. Do not add their areas as exclusive coverage. In rural mapping, “Vivienda campestre propuesta”, PTAP, PTAR and road corridors retain use 20, Other. “Bienes inmuebles candidatos a BIC” does not establish a heritage designation; “Predios adquiridos para la protección” neither identifies parcels nor establishes ownership. Risk, mining, 45-degree-slope and Chicamocha riparian-zone labels do not certify current conditions, measurements, permits or boundaries. Compatible, conditional and prohibited uses are unreported in the available records; an empty or null value means neither permitted nor prohibited. General address search does not identify parcels. For rural example 61051, “Áreas forestales protectoras (cuerpos de agua)”, move the center to longitude -72.99323, latitude 5.72591, zoom to 14 and query the center; to filter, select Rural zoning.

Municipal code 15806 identifies Tibasosa in Boyacá. OBJECTID identifies records within each source, not parcels or permits. Uso_Principal and Tipo_Categoria_Rural retain their separate domains. IGAC records EOT2000 (record 9051), Agreement 20, adopted on 2000-10-26, instrument status “Repealed”, long-term validity “Unreported”; register updated on 2026-05-15. IGAC records EOT2000 (record 9052), Agreement 9, adopted on 2011-09-29, instrument status “Repealed”, long-term validity “Unreported”; register updated on 2026-05-15. IGAC records EOT2000 (record 9053), Agreement 12, adopted on 2011-12-27, instrument status “Repealed”, long-term validity “Unreported”; register updated on 2026-05-15. IGAC records EOT2021 (record 9054), Agreement 11, adopted on 2021-11-20, instrument status “In force”, long-term validity “In force”; register updated on 2026-05-15. Instrument status and long-term validity are separate IGAC-register fields; they neither certify currently applicable rules nor identify the act behind each polygon. CEM reports a catalog date of 2025-11-28 and inputs dated 2025-02-20 for these layers; these are neither municipal-act adoption dates nor dates for individual polygons. Copies were retrieved on 2026-10-08. Under IGAC public cadastre, use “Search by NPN” with all 30 digits to query both municipal layers. CODIGO is the NPN, not a land-title folio or CBML.

Local example: Activity areas · IGAC 2025 · latitude, longitude: 5.74723, -72.99945

Query guide for Tibasosa →

Frequently asked questions

How do I query “Activity areas · IGAC 2025”?

Open “Activity areas · IGAC 2025” in Tibasosa: Activity areas · IGAC 2025. Select an area and read its detail, code, official domain label and observations. For activity areas, Uso_Principal 1 means Residencial; for rural zoning, 1 means Agricola. The domains differ: do not compare codes across layers as if they were the same category.

Does an empty field mean a use is allowed?

No. Compatible, conditional and prohibited uses retain what the source reports when available. Nulls remain missing; discrepancies between codes and descriptions are neither filled nor corrected. Identifiers distinguish records, not parcels. Confirm the rules and applicable act with municipal Planning.

What dates and coverage do the polygons represent?

The IGAC catalog lists publication on 28 November 2025 and inputs dated 20 February 2025. These are not adoption or planning-validity dates. The copy retrieved on 2026-10-08 retains all received municipal records; the visible area loads by pages, up to 5,000 map features and 8 MiB per layer. Overlaps and gaps may exist; do not add their areas or interpret risk categories as current alerts. Read the local notices in Sources.

What is the source and how can I reuse the data?

IGAC / Colombia OT, using municipal instruments as inputs. Colombia en Mapas declares CC BY 4.0 for the selected layers: credit the municipality, IGAC and the GeoSAT adaptation when exporting. GeoSAT retains geometries and codes, adds official domain labels and represents empty text as null. Records link the service, catalog and documents; the documents are not automatically linked to individual polygons.

Open this query ↗