Static Data Export: Difference between revisions

Line 1:

{{Update|2025-09-22: CCP has reworked the SDE ([https://developers.eveonline.com/blog/reworking-the-sde-a-fresh-start-for-static-data Reworking the SDE: a fresh start for static data]). This rework is '''not backwards compatible'''.}}

CCP provides developers a series of static files, known as the Static Data Export(SDE), which contains static data from the Tranquility server. The SDE is currently exported as .yaml and .static files, however, different and easier to use formats(mentioned below) are made by the community. The SDE can be found at the EVE developers [https://developers.eveonline.com/docs/services/sde/ Services and Resource] page. All resources provided by CCP are subject to the [https://developers.eveonline.com/license-agreement developer license agreement].

== Fuzzwork SDE Conversions ==

To aide fellow developers and players in consuming this data without having to extract or convert from YAML or static format every time Steve Ronuken has hosted conversions in PostgreSQL, SQLite, MySQL, MSSQL, and CSV formats. They can be found at [https://www.fuzzwork.co.uk Fuzzwork] under SDE or more directly at [https://www.fuzzwork.co.uk/dump www.fuzzwork.co.uk/dump]. Individual table data can be found in [[:wikipedia:Comma-separated values|CSV]] and [[:wikipedia:SQL|SQL]] (MySQL) formats here [https://www.fuzzwork.co.uk/dump/latest www.fuzzwork.co.uk/dump/latest].

Line 7:

Line 10:

== How does the ESI fit into all this? ==

The [[EVE Swagger Interface]] intends to have endpoints to account for all of the SDE, currently, it's not quite there yet, and the SDE is needed for many projects. The progress can be tracked [https://github.com/esi/esi-issues/issues/1103 ~~here~~].

The [[EVE Swagger Interface]] intends to have endpoints to account for all of the SDE; currently, it's not quite there yet, and the SDE is needed for many projects. The progress can be tracked on the [https://github.com/esi/esi-issues/issues/1103 SDE parity checklist] at the [https://github.com/esi ESI] GitHub.

== How to implement the original SDE into your application ==

=== Step 0: Preface ===

This is not a guide to Python or programming, if you don't know how to program, there are tons of resources to learn to code, there are a few of my favorites in the External ~~Links~~ section ~~down below~~.

This is not a guide to Python or programming, if you don't know how to program, there are tons of resources to learn to code, there are a few of my favorites in the [[#External links|External links]] section.

=== Step 1: Opening the file ===

Firstly, find the file containing the data you need, for this example, I'm going to use fsd/blueprints.yaml. This file contains all the information required to build an industry cost predictor. Next, open the file using your desired programming language, I'm going to use python, so to open this I'll run ''with open("fsd/blueprints.yaml", "r") as f:''. The file is open! To the next step!

Firstly, find the file containing the data you need, for this example, I'm going to use fsd/blueprints.yaml. This file contains all the information required to build an industry cost predictor. Next, open the file using your desired programming language, I'm going to use python, so to open this I'll run <code>with open("fsd/blueprints.yaml", "r") as f:</code>. The file is open! To the next step!

=== Step 2: Reading the file ===

==== Step 2.1: Installing PyYAML ====

Assuming you're using pip, this should be as simple as ''pip install pyyaml''. If you having issues have a look at [https://stackabuse.com/reading-and-writing-yaml-to-a-file-in-python/ ~~this article~~].

Assuming you're using pip, this should be as simple as <kbd>pip install pyyaml</kbd>. If you having issues have a look at [https://stackabuse.com/reading-and-writing-yaml-to-a-file-in-python/ Reading and Writing YAML to a File in Python] on stackabuse.

==== Step 2.2: Interpreting the file ====

Now that PyYAML is installed, we need to use it to parse our file, we have already opened it, so it should just be a matter of parsing it with PyYAML, which can be done by ''blueprints = yaml.load(f, Loader=yaml.FullLoader)'', remember to have ''import yaml'' at the top of your .py file. Hopefully now if you print out the blueprints variable, your console will be filled with sweet, sweet data and the taste of success. The data will be a dictionary, and the rest from here should be relatively simple, it should just be navigating through the data as if it was a dictionary.

Now that PyYAML is installed, we need to use it to parse our file, we have already opened it, so it should just be a matter of parsing it with PyYAML, which can be done by <code>blueprints = yaml.load(f, Loader=yaml.FullLoader)</code>, remember to have ''import yaml'' at the top of your .py file. Hopefully now if you print out the blueprints variable, your console will be filled with sweet, sweet data and the taste of success. The data will be a dictionary, and the rest from here should be relatively simple, it should just be navigating through the data as if it was a dictionary.

=== Step 3: Postface ===

Line 653:

Line 655:

* [https://www.youtube.com/channel/UCCezIgC97PvUuR4_gbFUs5g Corey Schafer]

* EVE Online Discord Dev Chat [https://discord.com/channels/940573867192221696/972841377798946896 3rd-party-dev-and-esi] - I read most messages sent here, if you need help that StackOverflow can't provide, here is your best bet.

[[Category:Applications]]

@@ Line 1: / Line 1: @@
+{{Update|2025-09-22: CCP has reworked the SDE ([https://developers.eveonline.com/blog/reworking-the-sde-a-fresh-start-for-static-data Reworking the SDE: a fresh start for static data]). This rework is '''not backwards compatible'''.}}
 CCP provides developers a series of static files, known as the Static Data Export(SDE), which contains static data from the Tranquility server. The SDE is currently exported as .yaml and .static files, however, different and easier to use formats(mentioned below) are made by the community. The SDE can be found at the EVE developers [https://developers.eveonline.com/docs/services/sde/ Services and Resource] page. All resources provided by CCP are subject to the [https://developers.eveonline.com/license-agreement developer license agreement].
 == Fuzzwork SDE Conversions ==
 To aide fellow developers and players in consuming this data without having to extract or convert from YAML or static format every time Steve Ronuken has hosted conversions in PostgreSQL, SQLite, MySQL, MSSQL, and CSV formats. They can be found at [https://www.fuzzwork.co.uk Fuzzwork] under SDE or more directly at [https://www.fuzzwork.co.uk/dump www.fuzzwork.co.uk/dump]. Individual table data can be found in [[:wikipedia:Comma-separated values|CSV]] and [[:wikipedia:SQL|SQL]] (MySQL) formats here [https://www.fuzzwork.co.uk/dump/latest www.fuzzwork.co.uk/dump/latest].
@@ Line 7: / Line 10: @@
 == How does the ESI fit into all this? ==
-The [[EVE Swagger Interface]] intends to have endpoints to account for all of the SDE, currently, it's not quite there yet, and the SDE is needed for many projects. The progress can be tracked [https://github.com/esi/esi-issues/issues/1103 here].
+The [[EVE Swagger Interface]] intends to have endpoints to account for all of the SDE; currently, it's not quite there yet, and the SDE is needed for many projects. The progress can be tracked on the [https://github.com/esi/esi-issues/issues/1103 SDE parity checklist] at the [https://github.com/esi ESI] GitHub.
 == How to implement the original SDE into your application ==
 === Step 0: Preface ===
-This is not a guide to Python or programming, if you don't know how to program, there are tons of resources to learn to code, there are a few of my favorites in the External Links section down below.
+This is not a guide to Python or programming, if you don't know how to program, there are tons of resources to learn to code, there are a few of my favorites in the [[#External links|External links]] section.
 === Step 1: Opening the file ===
-Firstly, find the file containing the data you need, for this example, I'm going to use fsd/blueprints.yaml. This file contains all the information required to build an industry cost predictor. Next, open the file using your desired programming language, I'm going to use python, so to open this I'll run ''with open("fsd/blueprints.yaml", "r") as f:''. The file is open! To the next step!
+Firstly, find the file containing the data you need, for this example, I'm going to use fsd/blueprints.yaml. This file contains all the information required to build an industry cost predictor. Next, open the file using your desired programming language, I'm going to use python, so to open this I'll run <code>with open("fsd/blueprints.yaml", "r") as f:</code>. The file is open! To the next step!
 === Step 2: Reading the file ===
 ==== Step 2.1: Installing PyYAML ====
-Assuming you're using pip, this should be as simple as ''pip install pyyaml''. If you having issues have a look at [https://stackabuse.com/reading-and-writing-yaml-to-a-file-in-python/ this article].
+Assuming you're using pip, this should be as simple as <kbd>pip install pyyaml</kbd>. If you having issues have a look at [https://stackabuse.com/reading-and-writing-yaml-to-a-file-in-python/ Reading and Writing YAML to a File in Python] on stackabuse.
 ==== Step 2.2: Interpreting the file ====
-Now that PyYAML is installed, we need to use it to parse our file, we have already opened it, so it should just be a matter of parsing it with PyYAML, which can be done by ''blueprints = yaml.load(f, Loader=yaml.FullLoader)'', remember to have ''import yaml'' at the top of your .py file. Hopefully now if you print out the blueprints variable, your console will be filled with sweet, sweet data and the taste of success. The data will be a dictionary, and the rest from here should be relatively simple, it should just be navigating through the data as if it was a dictionary.
+Now that PyYAML is installed, we need to use it to parse our file, we have already opened it, so it should just be a matter of parsing it with PyYAML, which can be done by <code>blueprints = yaml.load(f, Loader=yaml.FullLoader)</code>, remember to have ''import yaml'' at the top of your .py file. Hopefully now if you print out the blueprints variable, your console will be filled with sweet, sweet data and the taste of success. The data will be a dictionary, and the rest from here should be relatively simple, it should just be navigating through the data as if it was a dictionary.
 === Step 3: Postface ===
@@ Line 653: / Line 655: @@
 * [https://www.youtube.com/channel/UCCezIgC97PvUuR4_gbFUs5g Corey Schafer]
 * EVE Online Discord Dev Chat [https://discord.com/channels/940573867192221696/972841377798946896 3rd-party-dev-and-esi] - I read most messages sent here, if you need help that StackOverflow can't provide, here is your best bet.
 [[Category:Applications]]