Skip to content
GEOSAT
← Planadas

Activity areas · IGAC 2025 in Planadas

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

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

Open this query ↗

Planadas · 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 Planadas 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 Planadas

Open the POT example and select “Query map center” to inspect OBJECTID 1596 under Activity areas. The rural example lets you inspect OBJECTID 4894. Read original observations; do not add overlapping areas. Search a 30-digit NPN in IGAC public cadastre and query the available POT layers across the original parcel geometry. Urban and rural examples are verified. Samples do not establish complete municipal coverage. Nominal data cut 2026-08-31, retrieved 2026-10-11; CC BY-SA 4.0 according to the source item. CODIGO is not a land-title folio, owner or address. NPN is excluded from URLs, shared links and analytics and does not persist on reload. Review partial results and limits. Address search does not identify parcels. PlanetScope 2024 pixels were verified at municipal sample locations: 3 m satellite imagery under CC BY 4.0, not aerial orthophotography. Samples do not certify complete coverage, cloud-free imagery or current conditions. Select Orthoimage to view local imagery above PlanetScope; hide it using the Local imagery button. Check date, footprint and CC BY 4.0 terms in its source.

73555 identifies Planadas, Tolima. The complete IGAC municipal boundary was retrieved on 2026-10-11 without simplification under CC BY 4.0; source EPSG:9377, response EPSG:4326. The source advises against exact point positioning and area or distance calculations using this boundary; no scale or cartographic date is inferred. Instruments retrieved from the IGAC register: PBOT2004: Agreement 10 (2004-04-03), Adoption; register: Repealed, Published; PBOT2021: Agreement 6 (2021-05-27), Review following expiry of the long-term period; register: Current, Current, Published; PBOT2021: Agreement 24 (2020-07-25), Exceptional amendment in the public interest; register: Not published. Two urban records and four rural records lack use; eight rural records lack category. The register associates PBOT2021 with Agreement 24 dated 2020-07-25, earlier than its recorded adoption; this is neither corrected nor assigned to polygons by inference. Compatible, conditional and prohibited uses are unreported; empty fields mean neither allowed nor prohibited. Register statuses neither certify current legal validity nor assign acts to each polygon. Search a 30-digit NPN in IGAC public cadastre and query the available POT layers across the original parcel geometry. Urban and rural examples are verified. Samples do not establish complete municipal coverage. Nominal data cut 2026-08-31, retrieved 2026-10-11; CC BY-SA 4.0 according to the source item. CODIGO is not a land-title folio, owner or address. NPN is excluded from URLs, shared links and analytics and does not persist on reload. Review partial results and limits.

Local example: Activity areas · IGAC 2025 · latitude, longitude: 3.2016781984302822, -75.64585594803123

Query guide for Planadas →

Frequently asked questions

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

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