Implement star system data retrieval from Spansh?

[Tkael]

What happens now

Star system data is sourced from EDSM. EDSM data is bound to user accounts and may not be retained for accounts deactivated due to inactivity. Further, the EDSM API is rate limited and rate limiting has a dramatic impact on service query search times.

What I'd like to happen

Consider transitioning from EDSM to a more comprehensive / more complete data source.

How it can happen

It is possible to access system data via the Spansh API using id64 / system address, e.g. https://www.spansh.co.uk/api/system/263303726260. The complementary user-friendly version of the page is at https://www.spansh.co.uk/system/263303726260.

Similarly, station data is available using market ID: https://www.spansh.co.uk/api/station/3707582976 and body data is available via body id64: https://www.spansh.co.uk/api/body/36029060322690228.

Body id64 is calculated from: (bodyId << 55) + systemAddress.

EDDI Version

4.0.1

[Tkael]

Buy/sell locations are available with a query like: https://spansh.co.uk/api/commodity/sell/Sol/Platinum/100 or https://spansh.co.uk/api/commodity/buy/Sol/Platinum/100

Reference system (results are ordered by distance to this location, case sensitive): Sol Commodity: Platinum (case sensitive, ref. name from https://github.com/EDCD/FDevIDs/blob/master/commodity.csv) Amount to sell/buy: 100

[Tkael]

Type-ahead endpoint: https://spansh.co.uk/api/systems/field_values/system_names?q=sol Quick search endpoint (returns systems, bodies, and stations): https://spansh.co.uk/api/search?q=sol Dump endpoint (returns the same data available from the line in the dump file, which includes almost all journal fields but no additional data seeded from other sources): https://www.spansh.co.uk/api/dump/10477373803