We maintain NoEscape 2.0 (https://nemap.fyi/), a public map built from Ukraine’s open court registry: decisions describing border-crossing attempts (mostly article 204-1) are geocoded and published as derived points - never exact coordinates, never personal data.

Three mapping-side notes: 1. Geocoding uses oblast boundaries plus border-sign numbers with distances from decision texts; settlements are the fallback. Cases without any anchor stay off the map - incompleteness is explicitly stated, not hidden. 2. Our offline checklist (https://nemap.fyi/offline-map) sends users to pre-downloaded OsmAnd / Organic Maps terrain: there is no honest operator-coverage offline map, so we say so instead of faking one. 3. Method and dataset notes are public: https://nemap.fyi/methodology and https://nemap.fyi/dataset. Questions on the geocoding trade-offs welcome.

We maintain NoEscape 2.0 (https://nemap.fyi/), a public map built from Ukraine’s open court registry: decisions describing border-crossing attempts (mostly article 204-1) are geocoded and published as derived points - never exact coordinates, never personal data.

Three mapping-side notes: 1. Geocoding uses oblast boundaries plus border-sign numbers with distances from decision texts; settlements are the fallback. Cases without any anchor stay off the map - incompleteness is explicitly stated, not hidden. 2. Our offline checklist (https://nemap.fyi/offline-map) sends users to pre-downloaded OsmAnd / Organic Maps terrain: there is no honest operator-coverage offline map, so we say so instead of faking one. 3. Method and dataset notes are public: https://nemap.fyi/methodology and https://nemap.fyi/dataset. Questions on the geocoding trade-offs welcome.