JavaScript Mapping Library
Donald Trump’s administration is floating the idea that Ukraine should give up the Donbas to Russia in exchange for NATO membership. But how would you feel if it were your country being asked to surrender a fifth of its territory?
That’s the question posed by Russian Occupation – What if it were your country?, an interactive map that brings the reality of territorial occupation much closer to home. Created by Nini and Levan, a Georgian couple who witnessed the 2008 war in Georgia, the project has a simple but powerful idea: make the scale of Russian occupation tangible by showing it in places that people know.
Choose your country and the map highlights an area equivalent to approximately 20% of its territory in red. It provides a hypothetical illustration of what losing a fifth of the country might look like. It’s a particularly effective way of communicating the sheer geographical scale of occupation. Rather than looking at an unfamiliar map of eastern Ukraine or the Caucasus, you can see what losing a fifth of your own country might mean. The red area suddenly becomes a collection of familiar places, cities and landscapes.
But this is more than a geographical thought experiment. The project also documents the real history of Russian occupation in Moldova, Georgia and Ukraine. The Story Mode takes you through a series of chapters, beginning with the 1992 conflict in Moldova, moving on to the August 2008 war in Georgia, Russia’s annexation of Crimea in 2014, and the full-scale invasion of Ukraine in 2022. For Ukraine, you can also explore a sequence of dated territorial-control maps based on archived DeepState data.
These historical chapters give the project an important context. The hypothetical comparisons help visitors imagine the scale of losing territory, while the maps of Georgia, Moldova and Ukraine show that this is not an imaginary scenario for the people who live there.
One slight drawback with Russian Occupation (the map not Russian invasions) is that it can be quite slow to load. I investigated this using developer tools and discovered that the problem isn’t really the amount of data being downloaded. The three largest files – the world boundaries (world.json), the hypothetical country comparisons (comparisons.json) and the Globe.gl JavaScript library – total around 1.16 MB. That’s not particularly excessive.
The bigger problem appears to be what happens after those files have downloaded. A performance recording showed almost 26 seconds of JavaScript execution, with one function inside Globe.gl accounting for more than 18 seconds of that time. This suggests that the initial preparation of geographical polygons and their conversion into geometry for the 3D globe may be responsible for much of the delay. Once this work has been completed, the country comparisons are readily available, which would explain why subsequent selections are so quick.
I suspect there are two ways this initial loading time could be improved. Firstly, the geographical data could be simplified using a tool such as Mapshaper. Country and regional boundaries often contain far more coordinate points than are necessary for an interactive visualisation. Removing unnecessary vertices would reduce both the size of the GeoJSON files and the amount of geometry that needs to be processed. Secondly, the visualisation could be rebuilt using MapLibre GL JS rather than Globe GL. MapLibre is designed specifically for rendering interactive geographical data and doesn’t need to construct a 3D globe and all its associated geometry.
Maps Mania
You must be logged in to post a comment.
This site uses Akismet to reduce spam. Learn how your comment data is processed.