Flood hazard in Bogotá
Explore flood-hazard polygons published by IDIGER: categories, scenarios, land classes and locality, planning-unit and cadastral-sector references where available.
Hazard mapping for planning, without real-time alerts or observations. It does not determine individual parcel risk or safety; an absent polygon does not establish absence of hazard. The source declares no overall update date. Queries cover the visible area and are limited to 500 records and 2 MiB per response. Intersecting polygons retain their complete geometry; statistics describe loaded records. Service verification dates are not data dates.
Frequently asked questions
What does Flood hazard include in the Bogotá geovisor?
In Bogotá’s Flood hazard you can explore 1 layer: Flood hazard · IDIGER. Each layer states its source, date and use limits.
Can I reuse the Flood hazard data?
According to each layer’s published license: Public consultation; official terms: “Consulta”. Reuse license not specified. Check the exact license on the layer record before reuse.
How current are the Flood hazard data?
No dataset-wide date has been verified for these layers; check each source’s limits. Last GeoSAT verification: 2026-10-05.
How do I explore Flood hazard in the viewer?
Click “Explore these layers” to open the prepared Flood hazard query; review enabled layers under Layers. Filter by exact field and value, select features to read their records, and export received results with attribution and dates.
Who publishes the Flood hazard data?
Layers come from Instituto Distrital de Gestión de Riesgos y Cambio Climático · IDIGER / SIRE, retrieved and adapted by GeoSAT with per-record attribution and provenance.
Which other themes can I explore?
Other themes in the Bogotá geovisor: Land and planning, District protected areas, and Recorded mass movements.
Bogotá · Public query
Flood hazard
Explore flood-hazard polygons published by IDIGER: categories, scenarios, land classes and locality, planning-unit and cadastral-sector references where available.
Open Bogotá map →How to use the map
- Open the prepared query for this theme in the viewer. Locate an area using latitude, longitude coordinates or general place and address search.
- Review enabled layers and zoom to their query scale. Check each layer’s scope: it may query the visible area or the full municipal extent. An empty or unavailable service does not establish that no conditions apply.
- Select a feature on the map or in the Results list. Check its attributes, retrieval time and any partial-result notice.
- Choose a field and exact value to filter the layer. Export includes received results, with attribution and dates. Its coverage depends on the query scope and filters.
Local search and identifiers
Locate an area by coordinates or general address and place search; a match does not identify or certify a parcel. Enable layers, select a polygon and read its attributes. Parcel planning reports and official land-use queries are provided by SINUPOT.
Bogotá uses CHIP and BARMANPRE in cadastral sources. GeoSAT does not search parcels by these identifiers or convert them to Medellín’s CBML. Use the official Cadastre and Planning channels to locate and consult a parcel by its identifier.
Query guide for Bogotá →Sources, dates and limits
Each source’s verification date appears in the table. Retrieval time is not the data update date. Small city-wide layers use the full extent; larger layers depend on the visible area. Reference publications retain their original retrieval date. Each response contains up to 500 features and 2 MB. Reference publications load matching pages, up to 5,000 features and 8 MB per query. External services may return partial samples, identified in the viewer.
| Layer and source | Data date | Reuse |
|---|---|---|
| Flood hazard · IDIGERInstituto Distrital de Gestión de Riesgos y Cambio Climático · IDIGER / SIRE Hazard mapping for planning, without real-time alerts or observations. It does not determine individual parcel risk or safety; an absent polygon does not establish absence of hazard. The source declares no overall update date. Queries cover the visible area and are limited to 500 records and 2 MiB per response. Intersecting polygons retain their complete geometry; statistics describe loaded records. Service verification dates are not data dates. | No dataset-wide date declared; check individual recordsSource checked: | Public consultation; official terms: “Consulta”. Reuse license not specified |
Display transformations and adaptations are described for each source; precision and methods differ between sources. Obtain official mapping if you need surveying accuracy or documents with administrative validity.