Skip to content

Interactive simulation

Simulation of a geospatial lab

The same set of incidents tells different stories depending on how it is drawn. Switch between official boundaries, patrol sectors, hexagons, clusters and coverage radii, and draw your own area to measure it.

GEOSPATIAL LAB · MEXICO CITY

Borough polygons

Choropleth over the official boundaries of the 16 boroughs.

Incident type

5,175 incidents with current filters

Incidents per area

  • 560 – 1,236
  • 344 – 559
  • 172 – 343
  • 46 – 171
  • 15 – 45
  • No incidents

Boroughs with the most incidents

  1. 1. Cuauhtémoc1,236
  2. 2. Iztapalapa772
  3. 3. Gustavo A. Madero642
  4. 4. Miguel Hidalgo559
  5. 5. Venustiano Carranza411
  6. 6. Coyoacán368
Loading map…

Fictitious incidents on real OpenStreetMap cartography. Borough boundaries: INEGI. Use Ctrl or Cmd + scroll to zoom.

Try it

  1. 1In "Heat map" tap "Play the day" and watch hotspots shift hour by hour.
  2. 2Switch the map type in the top bar and compare how the same data looks.
  3. 3In "Patrol grid" change the cell size; in "3D hexagons" tilt the map with the compass control.
  4. 4In "Base coverage" tap the map to add bases until the red points are covered, and in "Draw an area" trace a polygon to count what falls inside.

What you are seeing

Official boundaries

Boroughs use INEGI's geostatistical framework; in your system they can be neighborhoods, sectors or your own patrol areas.

Coded sectors

Each cell has a code so it can be assigned to a shift or a unit.

Measurable coverage

The share of incidents within each base's radius is recalculated as you move bases or change the radius.

Custom areas

Any polygon you draw becomes a filter for reports, alerts or geofences.

Simulation with fictitious data that runs entirely in your browser. The real system is configured with each institution's catalogs, roles and integrations.

Can you picture this with your data?

We set up a demo with the catalogs and real cases from your operations.