EVE Technology Lab

I've skimmed through the patch notes, but didn't find it mentioned somewhere, so I ask it here:

1) Which API provides the citadel's location? Would those be included in ConquerableStationList?

2) What "magic number(s)" - if any, is necessary for calculating the citadel's solar system from an asset's locationID?

Yeah, saw your thread, Pete, but as it hasn't got an answer, I thought I might menion it elsewhere (here) again.

Or are you implying with your post that the locations are indeed in crest.industry.facilities, as Mr. mac suggested there? If so, that would totally break EWA ... :-(

@CCP Tellus
region.staticdata for each region is missing the radius. Are we supposed to calculate that from the given info?
constallation and solarsystem staticdata files include that info however.

Shouldn't the formula be radius = √((xMax - x)^2 + (yMax - y)^2 + (zMax - z)^2) ?

OK. I assumed that a region is a sphere so I had to calculate the distance from the center, which apparently is incorrect.

Fiddling around the formula becomes radius = (√((xMax - xMin)^2 + (yMax - yMin)^2 + (zMax - zMin)^2)) / 2. This gives me fairly the same numbers as the old universe format. Still need to figure out some rounding.

Sorry for all the confusion. Took a stab at this and this is what I get:

From the universe data SQLite file, we have that the radius is 5.57645447335415e+16.

sqlite> select regionID, regionName, radius from mapRegions where regionName = 'A821-A';
regionID    regionName  radius              
----------  ----------  --------------------
10000019    A821-A      5.57645447335415e+16

By letting x1, y1, and z1 be the region's 'max' coordinates, and x2, y2, and z2 be the region's 'min' coordinates, we get:

>>> math.sqrt((x1 - x2)**2 + (y1 - y2)**2 + (z1 - z2)**2) / 2
5.576454473354151e+16

This matches the radius of the region in the legacy SDE. It also turns out I was wrong about dividing by the square root of two. Terribly sorry. I should test code before reaching a conclusion. :(

Hope this helps.

That's a really strange definition of a "radius". That's half the diagonal of a cube.

Pretty much.

After 5 long days battling with the new SDE format I'm finally done.
CCP Tellus I know I have become a pain in your bud but you had it coming (joking).

Here are my findings:

Negative points (errors)
- provide 'radius' info in region.staticdata for each region (already been discussed in this thread why it should be provided)
- landmarks are missing landmarkName, description (instead their ID counterparts are provided)
- constellation 'Tranquility' in Curse is named 'Tranquillity' (notice the double 'l')
- constellation 'G-C00324' in G-R00031 is named 'G-C00311' (which is correct?)
- solar system 'J170376' in 'C-R00015 > C-C00146' is named 'J140208' (which is correct?)
- provide 'orbitIndex' info in order to be able to produce the correct itemName for mapDenormalize (mainly for asteroid belts and moons)
- provide the special name of a celestial (sun, planet, moon etc) if exists (i.e. Uplingur IV (Ndoria), New Caldari I (Matigu), New Caldari III (Orieku), New Caldari V (Oniteseru))
- provide the npcStations name in order to be able to produce the correct itemName for mapDenormalize (please don't tell me that it can be found in staStations, legacy sde provided that without needing staStations). ownerID is provided, if you can provide ownerName too, it will be super.

Positive points
- Landmarks iconID can be now placed in the correct column (in legacy SDE it's falsely placed in radius column)
- mapCelestialStatistics 'pressure' info are more precise (it's truncated in legacy)
- A lot more data is available in new SDE format (but I'll stick on providing what was in legacy for EVESDEToSQL, at least for now)

Questions
- In legacy mapDenormilize table stargates and NPCStations have a number in radius. Where do we find that in the new SDE format?

Steve, sorry man but you don't get it. Universe data need to be independent as they always were.
Use case? If someone wants to import only the universe data back to a DB, he ends up with missing data. UniverseData sqlite was independent and could be used as such, so should the new format. About region radius we already discussed that in length with CCP Tellus in this thread (read previous posts). Numbers only match if you use Python. As for orbitIndex, it's because I tried to calculate them, I'm asking about that info to be included. The index order isn't the same for all celestials and it gets all messed up.Same case as with celestial names.Still same case as celestial names. Independency.