These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

Solar system sovereignty sources

Author
Parra Doxx
New Civil Fleet
#1 - 2017-02-06 07:50:31 UTC
Greetings,

In working up a mapping app, I have a few questions...

1. I've concluded that I must use one of the sovereignty/structures APIs to determine which alliance is controlling a particular nullsec solar system -- is that correct/best practice or am I missing something?

2. Am I correct in using the Incursions API for determining faction sovereignty in Contested systems?

3. As for hi/lo sec solar systems, I can find no static tables nor reference in any of the APIs which will let me identify which faction has sovereignty in each of the 3k+ stable solar systems of empire space. I have the Factions table, but haven't found a use for it. What am I missing -- do I simply assume, for example, that all the solar systems in Metropolis are Minmatar sov unless contested?

Thanks!
Blacksmoke16
Imperial Academy
#2 - 2017-02-06 15:14:18 UTC
There is an XML endpoint that i think is better. It lists solarSystemName, ID, and then factionID, allianceID and corpID:

https://api.eveonline.com/map/Sovereignty.xml.aspx

It also includes high sec systems as well.
Parra Doxx
New Civil Fleet
#3 - 2017-02-06 19:17:13 UTC
DOH! With the advancement of ESI beside CREST, I was treating the XML API as deprecated and expected its features to be in the other two -- lesson learned! Thank you!
Althalus Stenory
Flying Blacksmiths
#4 - 2017-02-07 08:49:34 UTC
Parra Doxx wrote:
DOH! With the advancement of ESI beside CREST, I was treating the XML API as deprecated and expected its features to be in the other two -- lesson learned! Thank you!

It will, soon™ :) (within 12-14month)
XML API is ~deprecated~ in the way it will disappear at the end of the ESI dev, but until then there are still many and many only available there.

EsiPy - Python 2.7 / 3.3+ Swagger Client based on pyswagger for ESI