Eve Frontier — static data (era 5 cycle 4)
Snapshot taken: 2026-01-23
This folder contains extracted static/reference data used by the EVE Frontier tooling and indexer. The files are plain JSON exports and summary reports intended for lookup, debugging and analysis.
Source: https://github.com/VULTUR-EveFrontier/eve-frontier-tools
bom_summary.json— Bill-of-Materials summary produced from blueprint/material mappings; useful for quick inventory or production planning.clean_blueprints_to_materials.json— Blueprint -> material mapping cleaned and normalized for import into tools or databases.clean_materials_to_blueprints.json— Inverse mapping of materials to blueprints that consume them.constellation_labels.json— Human-readable names and short metadata for constellations.pipeline_results.json— Output summary from the data extraction pipeline (checks, counts, warnings).region_labels.json— Human-readable names and metadata for regions.stellar_cartography.json— Hierarchical map data used for rendering or spatial queries (regions → constellations → systems).stellar_constellations.json— Full constellation records with IDs and relationships.stellar_labels.json— Labels for stars/objects used in the cartography data.stellar_regions.json— Full region records with IDs and relationships.stellar_systems.json— Solar system records including IDs, names and location coordinates (TEXT to preserve precision).stellar_systems_lagrande.json- Contains alternative or augmented system coordinates used by the Lagrange mapping step.system_labels.json— Short display labels for solar systems.type_extraction_summary.json— Summary statistics from the types extraction process (counts, missing fields).type_names_all.json— Full list of extracted type names (includes unpublished / internal types).type_names_published.json— Filtered list of published/visible type names suitable for UI lists.types_by_group.json— Types grouped by their item groups for easier lookups and category pages.
- These are static JSON files — open them with any JSON-aware tool, import into a local database, or consume directly from scripts.
- Example (Python):
import json
with open('stellar_systems.json') as f:
systems = json.load(f)
print(len(systems))- Coordinates and very large numeric IDs are stored as strings (
TEXT) in outputs to avoid precision loss when moving between systems. - The pipeline output (
pipeline_results.json) contains helpful diagnostics if you need to re-run or debug extraction steps.