Skip to content
GEOSAT
← Jerusalén

Planning: IGAC activity areas in Jerusalén

Explore activity areas published for Jerusalén; check missing data and observations before interpretation.

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

Open this query ↗

Jerusalén · Public query

Planning activity areas

Open the prepared query, mark a point and compare results by layer.

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 Jerusalén 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 Jerusalén

Open the POT example and select “Query map center” to inspect OBJECTID 45543 under Activity areas. Read original observations; do not add overlapping areas. IGAC national cadastre returned zero urban and rural records for Jerusalén on 2026-10-11. Parcel queries and NPN search are not enabled; this result establishes neither an actual absence of parcels nor the absence of another municipal source. 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. Local orthophotography remains pending: the service advertised by IGAC returned HTTP 502 for metadata and footprint on 2026-10-11. No alternative was confirmed in the checked official directories. The access failure does not establish absence of imagery.

25368 identifies Jerusalén, Cundinamarca. 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. The IGAC register lists: EOT2001, Agreement 3 (2001-04-24), status repealed; EOT2024, Agreement 9 (2024-08-21), status current, validity reported current (short term). Declared register update: 2025-11-15. 4 complete records of activity areas with original EPSG:4326 coordinates. Rural zoning is not integrated: all 19 complete original records were retrieved, but 1 exceeds existing per-feature geometry or response limits. Geometries are neither simplified nor split and no incomplete selection is published. IGAC reports adjusting vectors because the instrument boundary differs from the reference municipal boundary; GeoSAT retains the published geometry unchanged. The repealed 2001 EOT remains separate from the 2024 EOT. The four activity areas retain reported compatible, conditional and prohibited uses; this does not establish a planning permit. The rural family remains pending because one geometry exceeds the limits. Compatible, conditional and prohibited uses reported by the source are retained; an empty field means neither allowed nor prohibited. Register statuses neither certify current legal validity nor assign acts to each polygon. IGAC national cadastre returned zero urban and rural records for Jerusalén on 2026-10-11. Parcel queries and NPN search are not enabled; this result establishes neither an actual absence of parcels nor the absence of another municipal source.

Local example: Planning: IGAC activity areas · latitude, longitude: 4.564487371008859, -74.6953118784983

Query guide for Jerusalén →

Frequently asked questions

How do I query “Planning: IGAC activity areas”?

Open “Planning: IGAC activity areas” in Jerusalén: 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 ↗