Boundaries mirror, with the platform's official boundaries

OrionAI 2.23.0Released 4 November 2026

Administrative boundaries for every country now come from Orion's own PostGIS mirror, with each unit linked to its parent, and the official UN OCHA COD-AB boundaries already on the platform fill the levels geoBoundaries doesn't publish.

Read the announcement: Every country's boundaries, inside OrionGIS

Changes since 2.22.2.

#New

  • Boundaries mirror: Orion Core keeps every country's administrative boundaries in its own PostGIS database. OrionAI, Map Studio and the statistics-table join read units from the mirror, without waiting on geoBoundaries or GitHub, and keep working when those services are slow or down. A new boundaries_mirror job in Orion Core's index worker loads every country (geoBoundaries gbOpen, CC BY 4.0, levels 0 to 5 where published) and refreshes sets older than 90 days every Sunday night.
  • The platform's official boundaries: 129 boundary layers already in Orion's catalogue, the UN OCHA Common Operational Datasets (COD-AB, via HDX) and Kenya's IEBC 2019 sets for 40 countries, are copied into the mirror. They fill the levels geoBoundaries doesn't publish, for example Madagascar's 17,465 fokontany (level 4) and the level-4 units of Sierra Leone, Tunisia, Uganda and South Africa. Only staff-owned, public layers are used, and never GADM.
  • Parents on every unit: each unit now carries its parent at the next coarser level. Platform units take it straight from their official p-codes; geoBoundaries units are placed inside the parent that holds their inside point. "The wards of a county" can be filtered by name, not only by geometry.
  • GET /api/v1/boundaries/{iso3} lists the levels and sources the mirror holds for a country.

#Improved

  • geoBoundaries remains the default wherever it publishes a level, so every existing map, join and level number means exactly what it did before. Boundaries downloaded on demand are written to the mirror as well as the file cache.