sdi

sdi (Static Data Importer) is a command-line tool that downloads CCP's official EVE Online Static Data Export (SDE), parses it, and loads it into a local, query-ready SQLite database (EVE.db).

Instead of hand-parsing CCP's JSONL exports every time you need map, item, or industry data, run sdi and get a normalized SQLite file you can query directly with convenience views already built for the most common lookups (system/region/constellation info, stargate connections, blueprint materials and products).

Features

• Checks CCP's latest published build number and only downloads/rebuilds the database when a newer SDE is available.
• Downloads and extracts the official sde.jsonl.zip archive.
• Parses the following SDE datasets:
  • Map: regions, constellations, solar systems, stargates (plus a small hardcoded "galaxy" grouping known space, wormhole space, abyssal deadspace, Jove space, and the global market region per CCP's ID range documentation).
  • Entity: categories, groups, types.
  • Industry: activities, blueprints (manufacturing, invention, copying, reactions, and research), materials, products, and skill requirements.
• Writes everything into a normalized SQLite schema and builds several convenience views for common queries.
• Works around a small number of known bugs in CCP's SDE data (see Known SDE quirks below).

Requirements

• Rust (edition 2024).
• Internet access to developers.eveonline.com to fetch build info and the SDE archive.

Building

git clone https://github.com/WilliamWeist/static-data-import
cd sdi
cargo build --release

Usage

Run the compiled binary from the directory where you want EVE.db to be created:

./target/release/sdi

On each run, sdi will:

1. Fetch CCP's current SDE build number and compare it against the build recorded in your local EVE.db (if one exists).
2. If a newer build is available (or no local database exists yet), download and extract the SDE archive to a temporary directory.
3. Parse the map, entity, and industry data.
4. Build a fresh SQLite database in the temp directory and populate it.
5. Replace the local EVE.db with the newly built database.

If your local database is already up to date, sdi exits without making any changes.

Output: EVE.db

EVE.db is a standard SQLite file. Some notes on its structure:

Shared/common tables

• build the SDE build number and release date currently loaded.
• name, description multilingual name/description strings (en, de, es, fr, ja, ko, ru, zh), referenced by ID from other tables.

Map tables

• map_galaxy, map_region, map_constellation, map_solar_system, map_stargate
• map_position, map_position_2d

Entity tables

• entity_category, entity_group, entity_type

Industry tables

• industry_activity, industry_blueprint, industry_material, industry_product, industry_skill

Convenience views

• v_map solar system joined with its constellation, region, galaxy, security status, and coordinates.
• v_stargate stargate connections resolved to human-readable "from system → to system" pairs.
• v_entity published types joined with their group and category names.
• v_blueprint_catalog blueprints joined to the activity and product(s) they produce.
• v_blueprint_materials blueprint material requirements.

Feel free to query EVE.db directly with any SQLite client, or embed it as a read-only reference database in your own application.

Known SDE quirks

CCP's static data occasionally contains dangling references. sdi currently works around two known issues by skipping the affected rows rather than failing the whole import:

• A handful of blueprint entries reference a material_id that doesn't exist in the SDE.
• A larger set of blueprint entries reference a product_id that doesn't exist in the SDE.

These workarounds are documented and maintained in src/sde/quirks.rs. If CCP fixes the underlying data in a future SDE release, the corresponding IDs can simply be removed from that file.

🤖 AI Usage & Assistance

• Documentation: The README.md was structured and generated using Claude.ai.
• Coding Assistants: Coding assitants was used for code review.
• AI Agents: No AI agents was used for this project, all code was generated by human.

Author

William Weist (wiweist@gmail.com)

License

This project is licensed under the MIT License, see the LICENSE file for details.