Public API

The daily (might not be updated every day) sov data can be found here:

1. JSON: echoes.meise.blue/sov/sov_data.json
2. JSON (zlib compressed): echoes.meise.blue/sov/sov_data.json.comp
3. Msgpack echoes.meise.blue/sov/sov_data.msgpack
4. Msgpack (zlib compressed): echoes.meise.blue/sov/sov_data.msgpack.comp
5. Eveeye CSV: echoes.meise.blue/sov/eveeye.csv

Please use the compressed versions if you can. They are smaller and faster to download. Example code usage can be found in this gist:

The file json and mgspack files contains all systems that has sov, as well as the data for the corporations and alliances that own them. The data is updated once a day, however the script might crash and not update the data. The system data includes the timestamp when the ownership was seen the first and last time. Use this to verify the data is up to date. The eveeye json data contains the latest timestamp as the value for Jita.

Notes on the map

The underlying algorithm is based on the one for Eve Online by Paladin Vent and Verite Rendition. Their version can be found here: verite.space. This is a rewrite in C++ and Cython/Python by Blaumeise03. The code is available on GitHub: github.com/Blaumeise03/bluemap and is pushed to PyPi as a python package.

The map does not show sov ownership over regions. It does show the influence of alliances (corps that do own systems and are not affiliated with an alliance are considered as their own alliance) over systems. This is an important distinction that causes some confusion for players. That's why the map does not look like the ingame sov map.

The way it works, every system gets a score based on its tech level (in Eve Online, the ADM score was used, but this is not available in Echoes, I am open to suggestions on how to improve this). In the first phase, for every system, the owner of the system gets this score as it's base influence. This influence is spread out to neighboring systems and decays over distance. As a result, every system has a list of alliances with an assigned influence.
In the second phase, for every pixel, the influence of all systems in a given radius (measured in spatial distance, not jumps) are weighted by their distance and summed up. The alliance with the highest influence score for this pixel is chosen to be rendered on the map.

This is in line with the influence maps for Eve Online (found here). For more details on the algorithm, please refer to the documentation of the source code. The algorithm details can be found here.