Skip to content
GEOSAT
← Tibú

Activity areas · IGAC 2025 in Tibú

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

1 layer · 4 published map features · Tibú municipality · IGAC / Colombia OT · GeoSAT adaptation: domain labels and empty values

Open this query ↗

Tibú · Public query

Planning activity areas

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 Tibú 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 Tibú

Open the planning example and press “Query map center” to view 3490, “Comercial”. To filter other records, use “View layers and explore the area”, “Inspect and export results”, the Activity areas layer and the Record identifier (OBJECTID) field. 3493, “Áreas verdes”, lacks main use: no code is inferred from its name. The commercial record’s literal <Null> observation is presented as unknown. The PBOT2000 instrument register and these four geometries are consulted separately; their legal correspondence is not assumed. Compatibility and restriction attributes are not current authorizations; unreported values remain unknown. The official Rural zoning query returned zero records; this does not establish absence of municipal rural planning. Under IGAC public cadastre, explore land records at zoom 16 or higher and select a record to read CODIGO, codigo_municipio and OBJECTID. Exploration is limited to the map view: reduce the area when results are partial or exceed the limit. “Search by NPN” queries the rural layer within the same municipality via POST and may return multiple matches; review each record and the partial-result or failure notices for the layer. An empty result does not establish parcel nonexistence. The NPN is excluded from the URL, shared links and analytics, and the query is not saved on reload. From the parcel record, press “Query POT across this parcel” to retrieve its IGAC geometry again without clipping or additional simplification and query integrated POT polygons intersecting the whole parcel. The white outline marks the queried geometry. A match may only touch a boundary; the query calculates neither affected areas nor percentages and certifies neither permitted uses, development rights nor building permits. The POT query includes activity areas only; rural zoning is not integrated.

54810 identifies the municipality in DANE. OBJECTID identifies records, not parcels or permits, and is not equivalent to CBML. IGAC records: PBOT2000, Agreement 28 (6 December 2000), status Current, validity Long-term validity expired. Register updated on 15 August 2026. These statuses are attributed to the register: they certify neither current validity nor that the geometries correspond to the most recent instrument. Under IGAC public cadastre, use “Search by NPN” with all 30 digits to query this municipality’s rural layer, independently of the map view. CODIGO preserves the published identifier as text, not a land-title folio or CBML. The database cut is 2026-08-31 and certifies neither ownership, precision nor parcel planning rules. General address search does not identify parcels. Verified samples and windows do not establish a complete municipal inventory. In the bounded review, 5067345 has nested polygon components. Original geometry is retained without repair; review the source before interpreting spatial results. The finding neither invalidates all data nor describes a complete inventory.

Local example: Activity areas · IGAC 2025 · latitude, longitude: 8.639891, -72.734496

Query guide for Tibú →

Frequently asked questions

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

Open “Activity areas · IGAC 2025” in Tibú: 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 ↗