# ESI SDE parity progress

**URL:** <https://forums.eveonline.com/t/esi-sde-parity-progress/346625>\
**Category:** Third Party Developers\
**Created:** [January 20, 2022, 9:45am UTC](https://forums.eveonline.com/t/esi-sde-parity-progress/346625 "2022-01-20T09:45:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zoiie](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/zoiie/32/292363_2.png) [@Zoiie](https://forums.eveonline.com/u/Zoiie)\
**Post date:** [January 20, 2022, 9:45am UTC](https://forums.eveonline.com/t/esi-sde-parity-progress/346625/1 "2022-01-20T09:45:49Z")

</div>

> <https://github.com/esi/esi-issues/issues/1103>
>
> This checklist consists of all the files from the SDE, a short description of th…eir contents, and the current status of an ESI replacement for them, with the purpose of showing how close ESI is to achieving SDE parity.
> 
> Checked boxes indicate that a part of the SDE has an ESI equivalent or is in some way obsolete, while unchecked ones mean that more work is required to reach parity. If you disagree on my judgement on some of them, or think I've missed something, feel free to comment on this issue.
> 
> \- \[\] \`blueprints.yaml\`
> Blueprint details.
> Not available: https://github.com/esi/esi-issues/issues/501
> \- \[x\] \`categoryIDs.yaml\`
> Inventory category definitions.
> Available: https://esi.evetech.net/ui/?version=\_dev#/Universe/get\_universe\_categories\_category\_id
> \- \[\] \`certificates.yaml\`
> Mastery certificate definitions.
> Not available.
> \- \[x\] \`graphicIDs.yaml\`
> Some kind of graphics stuff.
> Available: https://esi.evetech.net/ui/?version=\_dev#/Universe/get\_universe\_graphics\_graphic\_id
> \- \[x\] \`groupIDs.yaml\`
> Inventory group definitions.
> Available: https://esi.evetech.net/ui/?version=\_dev#/Universe/get\_universe\_groups\_group\_id
> \- \[x\] \`iconIDs.yaml\`
> Icon ID to file mapping.
> Icons should be available through the image server.
> \- \[\] \`skinLicenses.yaml\`, \`skinMaterials.yaml\`, \`skins.yaml\`
> SKIN details.
> Not available.
> \- \[x\] \`tournamentRuleSets.yaml\`
> Tournament rules, including banned ships, ship point values, and team sizes. 
> Should be given the same treatment as the CREST tournament endpoints.
> \- \[x\] \`typeIDs.yaml\`
> Inventory type definitions.
> Available: https://esi.evetech.net/ui/?version=\_dev#/Universe/get\_universe\_types\_type\_id
> \- \[\] \`universe\`
> Multiple levels of folders (universe, region, constellation, solar system) containing .staticdata files describing their properties. The files for solar systems also contain details of all celestials inside that system.
> Available under various endpoints, but with some attributes missing:
> - \[\] Regions: faction, wormhole class, coordinates
> - \[\] Constellations: radius, min/max coordinates
> - \[\] Systems: radius, min/max coordinates, disallowed anchoring, various positional properties (border, corridor, fringe, hub...)
> - \[x\] Stars
> - \[x\] Stargates
> - \[\] Planets and moons: radius, celestial index, statistics
> - \[\] Asteroid belts: statistics
> \- \[\] \`landmarks\`
> Important locations that are shown in space on the old map. No way to resolve the name and description IDs to strings.
> Not available.
> \- \[\] \`agtAgentTypes.yaml\`, \`agtAgents.yaml\`, \`agtResearchAgents.yaml\`
> NPC agent details.
> Not available: https://github.com/esi/esi-issues/issues/863 https://github.com/esi/esi-issues/issues/1064
> \- \[x\] \`chrAncestries.yaml\`
> Character ancestries.
> Available: https://esi.evetech.net/ui/?version=\_dev#/Universe/get\_universe\_ancestries
> \- \[x\] \`chrAttributes.yaml\`
> Skill attribute descriptions.
> Not available, unused.
> \- \[\] \`chrBloodlines.yaml\`
> Character bloodlines.
> Available: https://esi.evetech.net/ui/?version=\_dev#/Universe/get\_universe\_bloodlines
> Missing male/female descriptions and short descriptions.
> \- \[x\] \`chrFactions.yaml\`
> NPC factions.
> Available: https://esi.evetech.net/ui/?version=\_dev#/Universe/get\_universe\_factions
> \- \[\] \`chrRaces.yaml\`
> Character races.
> Available: https://esi.evetech.net/ui/?version=\_dev#/Universe/get\_universe\_races
> Missing short descriptions, only returning the four playable races.
> \- \[x\] \`crpActivities.yaml\`
> Activities which NPC corporations engage in, don't appear to be referenced anywhere else.
> Not available, unused.
> \- \[x\] \`crpNPCCorporationDivisions.yaml\`
> Percentages of the corporations' agents belonging to each division.
> Not available, redundant.
> \- \[x\] \`crpNPCCorporationResearchFields.yaml\`
> Fields in which the corporations have research agents.
> Not available, redundant.
> \- \[x\] \`crpNPCCorporationTrades.yaml\`
> Types which NPC corporations sell on the market.
> Not available, but can be seen on the market itself.
> \- \[\] \`crpNPCCorporations.yaml\`
> Available: https://esi.evetech.net/ui/?version=\_dev#/Corporation/get\_corporations\_npccorps https://esi.evetech.net/ui/?version=\_dev#/Corporation/get\_corporations\_corporation\_id
> Missing various lore trivia, unable to get NPC corp faction ID: https://github.com/esi/esi-issues/issues/765 https://github.com/esi/esi-issues/issues/917
> \- \[\] \`crpNPCDivisions.yaml\`
> NPC corp division names.
> Should be enumified.
> \- \[\] \`dgmAttributeCategories.yaml\`
> Dogma attribute category definitions.
> Not available.
> \- \[x\] \`dgmAttributeTypes.yaml\`
> Dogma attribute definitions.
> Available: https://esi.evetech.net/ui/?version=\_dev#/Dogma/get\_dogma\_attributes\_attribute\_id
> \- \[x\] \`dgmEffects.yaml\`
> Dogma effect definitions.
> Available: https://esi.evetech.net/ui/?version=\_dev#/Dogma/get\_dogma\_effects\_effect\_id
> \- \[\] \`dgmExpressions.yaml\`
> Another piece of the dogma puzzle.
> Not available: https://github.com/esi/esi-issues/issues/1021
> \- \[x\] \`dgmTypeAttributes.yaml\`
> Dogma attribute values.
> Available: https://esi.evetech.net/ui/?version=\_dev#/Universe/get\_universe\_types\_type\_id
> \- \[x\] \`dgmTypeEffects.yaml\`
> Dogma effect assignments.
> Available: https://esi.evetech.net/ui/?version=\_dev#/Universe/get\_universe\_types\_type\_id
> \- \[\] \`eveUnits.yaml\`
> Units used by dogma attributes.
> Not available: https://github.com/esi/esi-issues/issues/404
> \- \[\] \`invContrabandTypes.yaml\`
> Types considered illegal in space of certain factions.
> Not available.
> \- \[\] \`invControlTowerResourcePurposes.yaml\`, \`invControlTowerResources.yaml\`
> Describes the fuel types, including charters, used by control towers.
> Not available.
> \- \[x\] \`invFlags.yaml\`
> Names of inventory location flags.
> Available: https://github.com/esi/eve-glue/blob/master/eve\_glue/location\_flag.py
> \- \[x\] \`invItems.yaml\`
> Inventory contents of CCP created EVE entities.
> Not available, unused.
> \- \[x\] \`invMarketGroups.yaml\`
> Market group definitions.
> Available: https://esi.evetech.net/ui/?version=\_dev#/Market/get\_markets\_groups\_market\_group\_id
> \- \[\] \`invMetaGroups.yaml\`
> Meta group definitions.
> Not available.
> \- \[\] \`invMetaTypes.yaml\`
> Meta group values.
> Not available.
> \- \[x\] \`invNames.yaml\`
> Names of EVE entities.
> Available on individual endpoints.
> \- \[x\] \`invPositions.yaml\`
> Coordinates of all the items from invItems.yaml.
> Not available, unused.
> \- \[\] \`invTypeMaterials.yaml\`
> Reprocessing output.
> Not available: https://github.com/esi/esi-issues/issues/664
> \- \[x\] \`invTypeReactions.yaml\`
> Old style reaction details.
> Not available, unused.
> \- \[x\] \`invUniqueNames.yaml\`
> Subset of invNames.yaml with type categories added.
> \- \[x\] \`mapUniverse.yaml\`
> Not available, unused.
> \- \[\] \`planetSchematics.yaml\`, \`planetSchematicsPinMap.yaml\`, \`planetSchematicsTypeMap.yaml\`
> PI schematic details.
> Not available: https://github.com/esi/esi-issues/issues/646 https://github.com/esi/esi-issues/issues/1066
> \- \[\] \`ramActivities.yaml\`
> Industrial activity type definitions.
> Should be enumified: https://github.com/esi/esi-issues/issues/894 https://github.com/esi/esi-issues/issues/997
> \- \[x\] \`ramAssemblyLineStations.yaml\`, \`ramAssemblyLineTypeDetailPerCategory.yaml\`, \`ramAssemblyLineTypeDetailPerGroup.yaml\`, \`ramAssemblyLineTypes.yaml\`, \`ramInstallationTypeContents.yaml\`
> Old slot-based industry definitions.
> Unused.
> \- \[\] \`staOperationServices.yaml\`, \`staOperations.yaml\`
> Used to assign station names, descriptions, and available services.
> Available, missing station descriptions: https://esi.evetech.net/ui/?version=\_dev#/Universe/get\_universe\_stations\_station\_id
> \- \[\] \`staServices.yaml\`
> Station service definitions.
> Enumified in https://esi.evetech.net/ui/?version=\_dev#/Universe/get\_universe\_stations\_station\_id
> Not available in https://github.com/esi/eve-glue
> \- \[\] \`staStationTypes.yaml\`
> Undock point position and orientation for stations.
> Not available.
> \- \[x\] \`staStations.yaml\`
> Available: https://esi.evetech.net/ui/?version=\_dev#/Universe/get\_universe\_stations\_station\_id
> \- \[x\] \`trnTranslationColumns.yaml\`, \`trnTranslationLanguages.yaml\`, \`trnTranslations.yaml\`
> Individual endpoints should have translation built in.
> \- \[x\] \`warCombatZoneSystems.yaml\`, \`warCombatZones.yaml\`
> Contains information about original owners of FW systems.
> Available: https://esi.evetech.net/ui/?version=\_dev#/Faction%20Warfare/get\_fw\_systems

Is there an ETA for when we can expect the shipped SDE blobs to be depreciated?

It seems to be taking forever with no end in sight and updates?

This also adds bloat when git cloning repos placing it into the half gigabyte territory, for example, almost 500mb for cloning Evemon.

---

<div class="post-metadata">

**Author:** ![Paz\_Lammaschtu](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/paz_lammaschtu/32/264397_2.png) [@Paz\_Lammaschtu](https://forums.eveonline.com/u/Paz_Lammaschtu)\
**Post date:** [January 20, 2022, 2:34pm UTC](https://forums.eveonline.com/t/esi-sde-parity-progress/346625/2 "2022-01-20T14:34:35Z")

</div>

I am not aware of any statement from CCP that a full SDE parity with ESI is their goal. It might be very comfortable from our perspective, but constantly crawling a lot of (mainly) static information is not very great for them regarding ressource usage.  
For me it is a third party’s developer responsibility to handle the static dumps and for example only load what you need, programmatic updating etc.  
Fuzzwork’s work gives such a great foundation to do that.

---

<div class="post-metadata">

**Author:** ![Zoiie](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/zoiie/32/292363_2.png) [@Zoiie](https://forums.eveonline.com/u/Zoiie)\
**Post date:** [January 20, 2022, 2:35pm UTC](https://forums.eveonline.com/t/esi-sde-parity-progress/346625/3 "2022-01-20T14:35:49Z")

</div>

I will simply try to do without the blob then and dev around it. I don’t want a huge git repo with binary blobs like that.

If it’s not on the ESI API then it won’t be used by me.

As for crawling static information, caching is a thing, I won’t be storing it in my git repo.

I could force users to download the static file at runtime, that would be worse for everybody but this blob will NOT be in my git repo or shipped package.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/eveonline/original/3X/4/1/41ec4921cbaca7a6f9ea556e7cc20018461eae5e.png) [@system](https://forums.eveonline.com/u/system)\
**Post date:** [April 20, 2022, 2:36pm UTC](https://forums.eveonline.com/t/esi-sde-parity-progress/346625/4 "2022-04-20T14:36:37Z")

</div>

Closed on April 20, 2022, 2:36pm UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
