# Reference Data
The Reference Data set is a collection of data from the EVE Online SDE, ESI, and Hoboleaks data. It aims to be a single source, combining all the available data into one. It does this by taking the latest SDE (opens new window), ESI scrape (opens new window), and Hoboleaks export (opens new window) and merging them into one common format.
The Reference Data is available as a REST API with full OpenAPI spec and as a full download (opens new window).
# Development
The reference data is currently in development. While changes should be minimal, they may occur at any time.
# REST API
The full OpenAPI spec is available on Github (opens new window).
Some example paths:
- https://ref-data.everef.net/blueprints (opens new window)
- https://ref-data.everef.net/blueprints/999 (opens new window)
- https://ref-data.everef.net/categories (opens new window)
- https://ref-data.everef.net/categories/4 (opens new window)
- https://ref-data.everef.net/dogma_attributes (opens new window)
- https://ref-data.everef.net/dogma_attributes/37 (opens new window)
- https://ref-data.everef.net/dogma_effects (opens new window)
- https://ref-data.everef.net/dogma_effects/11 (opens new window)
- https://ref-data.everef.net/groups (opens new window)
- https://ref-data.everef.net/groups/18 (opens new window)
- https://ref-data.everef.net/icons (opens new window)
- https://ref-data.everef.net/icons/67 (opens new window)
- https://ref-data.everef.net/market_groups (opens new window)
- https://ref-data.everef.net/market_groups/1857 (opens new window)
- https://ref-data.everef.net/meta_groups (opens new window)
- https://ref-data.everef.net/meta_group/6 (opens new window)
- https://ref-data.everef.net/mutaplasmids (opens new window)
- https://ref-data.everef.net/mutaplasmids/52225 (opens new window)
- https://ref-data.everef.net/regions (opens new window)
- https://ref-data.everef.net/regions/10000002 (opens new window)
- https://ref-data.everef.net/schematics (opens new window)
- https://ref-data.everef.net/schematics/65 (opens new window)
- https://ref-data.everef.net/skills (opens new window)
- https://ref-data.everef.net/skills/3336 (opens new window)
- https://ref-data.everef.net/types (opens new window)
- https://ref-data.everef.net/types/645 (opens new window)
- https://ref-data.everef.net/units (opens new window)
- https://ref-data.everef.net/units/1 (opens new window)
# Motivation
Two primary datasets are available for third-party developers of EVE Online: the SDE and ESI. While comprehensive, these two are not equal. There is data in the SDE which isn't in the ESI, and vice-versa. Additionally, Hoboleaks provides data extracted from the EVE Online client files.
EVE Ref was originally built on taking all three sources and combining them into one, making it as comprehensive as possible. The Reference Data set is an attempt at publishing this data for other developers to consume.
# Data sources
This table show the available data and where to get it.
| Data | Reference data | SDE | ESI | Hoboleaks |
|---|---|---|---|---|
| Accounting entry types | accountingentrytypes.json | |||
| Agent | npcCharacters.yaml | |||
| Agent in space | agentsInSpace.yaml | |||
| Agent types | agentTypes.yaml | agenttypes.json | ||
| Ancestors | ancestries.yaml | universe/ancestries.yaml | ||
| Asteroid belts | mapAsteroidBelts.yaml | universe/asteroid_belts.yaml | ||
| Bloodlines | bloodlines.yaml | universe/bloodlines.yaml | ||
| Blueprints | /blueprints | blueprints.yaml | blueprints.json | |
| Certificates | certificates.yaml | |||
| Character attributes | characterAttributes.yaml | |||
| Clone states | clonestates.json | |||
| Compressible types | compressibletypes.json | |||
| Constellations | mapConstellations.yaml | universe/constellations.yaml | ||
| Contraband types | contrabandTypes.yaml | |||
| Control tower resources | controlTowerResources.yaml | |||
| Corporation activities | corporationActivities.yaml | |||
| Dbuffs | dbuffCollections.yaml | dbuffs.json | ||
| Dogma attributes | /dogma_attributes | dogmaAttributes.yaml | dogma/attributes.yaml | localization_dgmattributes.json |
| Dogma attributes categories | dogmaAttributeCategories.yaml | |||
| Dogma effects | /dogma_effects | dogmaEffects.yaml | dogma/effects.yaml | |
| Dogma expressions | ||||
| Dogma type attributes | /types | typeDogma.yaml | universe/types.yaml | |
| Dogma type effects | dogmaEffects.yaml | universe/types.yaml | ||
dogmaeffectcategories.json | ||||
attributeorders.json | ||||
| Dogma units | dogmaUnits.yaml | dogmaunits.json | ||
| Dynamic attributes | /mutaplasmids | dynamicitemattributes.json | ||
| Expert systems | expertsystems.json | |||
| Factions | factions.yaml | universe/factions.yaml | ||
| Graphic material sets | graphicmaterialsets.json | |||
| Graphics | graphics.yaml | universe/graphics.yaml | ||
| Icons | icons.yaml | |||
| Industry activities | industryactivities.json | |||
| Industry assembly lines | industryassemblylines.json | |||
| Industry installation types | industryinstallationtypes.json | |||
| Industry modifier sources | industrymodifiersources.json | |||
| Industry target filters | industrytargetfilters.json | |||
| Inventory categories | /categories | categories.yaml | universe/categories.yaml | |
| Inventory flags | bsd/invFlags.yaml in old files | |||
| Inventory groups | /groups | groups.yaml | universe/groups.yaml | |
| Inventory items | bsd/invItems.yaml in old files | |||
| Inventory names | bsd/invNames.yaml in old files | |||
| Inventory type masteries | /types | masteries.yaml | universe/types.yaml | |
| Inventory type traits | /types | typeBonus.yaml | universe/types.yaml | |
| Inventory types | /types | types.yaml | universe/types.yaml | Adds repackagedvolumes.json |
| Inventory unique names | bsd/invUniqueNames.yaml in old files | |||
| Landmarks | landmarks.yaml | |||
| Languages | translationLanguages.yaml | Yes, indirectly | localization_languages.json | |
| Loyalty offers | Yes | |||
| Market groups | /market_groups | marketGroups.yaml | market/groups.yaml | |
| Meta groups | /meta_groups | metaGroups.yaml | ||
| Moons | mapMoons.yaml | universe/moons.yaml | ||
| NPC corporation | npcCorporations.yaml | |||
| NPC corporation divisions | npcCorporationDivisions.yaml | |||
| Opportunity groups | opportunities/groups.yaml | |||
| Opportunity tasks | opportunities/tasks.yaml | |||
| Planet resources | planetResources.yaml | |||
| Planetary schematics | /schematics | planetSchematics.yaml | universe/schematics.yaml | |
| Planets | mapPlanets.yaml | universe/planets.yaml | ||
| Races | races.yaml | universe/races.yaml | ||
| Regions | /regions | mapRegions.yaml | universe/regions.yaml | |
| Reprocessing | /types | typeMaterials.yaml | typematerials.json | |
| School map | schoolmap.json | |||
| Schools | schools.json | |||
| Skill plans | skillplans.json | |||
| Skills | /skills | types and dogma | types and dogma | |
| Skin licenses | skinLicenses.yaml | |||
| Skin material names | skinmaterialnames.json | |||
| Skin materials | skinMaterials.yaml | skinmaterials.json | ||
| Skins | skins.yaml | skins.json | ||
| Sovereignty upgrades | sovereigntyUpgrades.yaml | |||
| Stargate | mapStargates.yaml | universe/stargates.yaml | ||
| Stars | mapStars.yaml | universe/stars.yaml | ||
| Station operation | stationOperations.yaml | |||
| Station services | stationServices.yaml | |||
| Station standing restrictions | stationstandingsrestrictions.json | |||
| Stations | pcStations.yaml | universe/stations.yaml | ||
| Systems | mapSolarSystems.yaml | universe/systems.yaml | ||
| Tournament rule sets | fsd/tournamentRuleSets.yaml in old files |
- The ESI filenames refer to the names in the ESI scrape, minus the language suffix.
# Data structure
- Field names will be
snake_case, since that's how the ESI does it and all other data on EVE Ref Data comes from there.
It makes sense to continue that format. - URLs will be
snake_case, because that's how the ESI does it. - The JSON layout will be structured in a way mostly inspired by the ESI, though that may not always be possible.
- Prefer keyed objects to arrays - the final object merger should be kept as simple as possible.
Since it's not possible to merge arrays in a predictable way while preventing data duplication, keyed objects are preferred. - Names and descriptions will use a language map like the SDE, rather than multiple endpoints/files like the ESI.
# Corrections (TBD)
It would be possible to maintain a series of corrections and additions to the data.
For instance, there are Dogma attributes which have no categories and these could be added.
There are also cases where Dogma values are stored "incorrectly". For instance, sometimes the number 10% is stored as 10.0 and other times as 0.1,
even though the unit for the attribute is "percentage".
These could be corrected.
- Pro: The data is more accurate, consistent, and useful.
- Con: The data isn't a direct copy of the SDE or ESI.