Every dataset you find is ready for a map

Changes since 2.23.2.

#New

• Tables join to regions as well as countries. A table that reports on East Africa, West Africa, Asia or another region, by Orion's, the UN's or the World Bank's names and codes (Sub-Saharan Africa, "(SDGRC) Eastern Africa"), is drawn on the outline of the region's member countries. When a table lists countries and regions together, the map shows the countries, so no shapes overlap, and every region row is joined to its region in the full table and its downloads.
• Tables join to every admin level a country has: provinces, regions, counties, sub-counties, districts, wards and finer, up to five levels deep (Kenya's 1,452 wards, Rwanda's cells, France's 35,000 communes).
• Tables join to areas across many countries. A table of ISO 3166-2 codes (KE-43, US-CA) or of a country next to its province, county, district or ward names is placed on each country's own areas, so two areas with the same name in different countries stay apart.
• Tables that mix levels keep every row. When some rows give a ward and others only a sub-county or county, the map shows the finest level and every coarser row is joined to its own area in the full table and its downloads.
• Each area shows its latest figures. When reporting dates or operations differ from country to country, every area keeps its own latest value instead of the map shrinking to one country.
• World Bank, UNICEF and HDX HAPI tables can go on the map. Their rows are read live from each API when the data is used, then joined to OrionGIS boundaries.
• Bigger tables. OrionGIS now reads statistics tables of up to 1 million cells and 150 MB (was 100,000 cells and 50 MB), and every row of an HDX HAPI table, so national censuses and UN datasets with hundreds of thousands of rows go on the map whole.
• Countries are matched by name as well as code (ISO2 and ISO3), and admin areas by name or code.

#Fixed

• The on-the-map rule now applies to every table, however old. No table that isn't on the map is listed in Data Explorer, shown to search engines or offered to OrionAI. Tables already in the catalogue that weren't on the map have been taken out of view and are being processed again: each one returns as soon as OrionGIS has placed it.
• Records that ship a map file are published from that file. A dataset with a GeoJSON, shapefile, KML, GeoPackage, imagery or map service next to a CSV was sometimes filed as a table because the CSV was read first. Map files are now read first, and the CSV stays available as a download.
• Maps from tables with many breakdowns no longer come out empty or show one area. Number columns are treated as values rather than categories, and a join that draws only a few of the areas it matched is never published.
• Tables with only national figures are drawn on their country's outline.