ED Astrometrics: Maps and Visualizations

The file-scanner is looking for journal-formatted files specifically. I don't think EDSM exports in the game's journal format. Although technically, my importer cheats and doesn't care if it's properly formatted JSON, as long as each jump is a line in the file containing a few of the right strings. Lots of ways that could be faked, I suppose. I might be able to add some capability to support additional formats too.

EDIT: Looking at EDSM, I see an export button for the flight log, but it wants to do the "importstars.txt" format, which is just a bunch of system names. I'd need a file that contains the actual coordinates for this, since it doesn't have access to the database.
 
Would you mind giving an exact example how it looks like in EDSM and how it shall look like so that your filescanner can use it?
I can do the conversion myself.

So e.g.
EDSM => needed
"Ogainks HD-Q d6-2807" => 1617.28125, 1049.1875, 20034
(just the coordinates instead of the name)

or is it rather
"Ogainks HD-Q d6-2807" => {'x': 1617.28125, 'y': 1049.1875, 'z': 20034}

Edit: Argh … the EDSM file doesn't have the _ path _ just the star systems where I've been :(
Edit 2: But I might be able to scrape the necessary data … it's barely 200 pages for me and with 10 seconds between requests that can be done in less than an hour without putting to much of a burden onto the EDSM server.
Edit 3: and you wrote that several files can be imported. Will the path have different colours per file? Because than I can see where I've used which ship. … Ah damn … I might have another project.
 
Last edited:
EDSM literally gives a list of systems.

Code:
Kyloall SS-B d6831
Kyloall SS-B d7482
Kyloall RS-B d5193
Kyloall RS-B d1633
Eoch Pruae ZG-B d14-491
Eoch Pruae ZG-B d14-7295
Eoch Pruae YG-B d14-1639
Eoch Pruae KC-V f2-998
Eoch Pruae YK-O e6-622
Eoch Pruae UA-D d13-4030
Eoch Pruae TA-D d13-6889
Eoch Pruae TA-D d13-6259

And an jump event that can be processed by third party tools looks like

JSON:
{ "timestamp":"2021-06-09T12:31:04Z", "event":"FSDJump", "Taxi":false, "Multicrew":false, "StarSystem":"Blia Chria YO-A c11", "SystemAddress":3064761269250, "StarPos":[-25504.43750,111.00000,52719.00000], "SystemAllegiance":"", "SystemEconomy":"$economy_None;", "SystemEconomy_Localised":"None", "SystemSecondEconomy":"$economy_None;", "SystemSecondEconomy_Localised":"None", "SystemGovernment":"$government_None;", "SystemGovernment_Localised":"None", "SystemSecurity":"$GAlAXY_MAP_INFO_state_anarchy;", "SystemSecurity_Localised":"Anarchy", "Population":0, "Body":"Blia Chria YO-A c11", "BodyID":0, "BodyType":"Star", "JumpDist":64.342, "FuelUsed":4.994932, "FuelLevel":27.005068 }

So given Orvidius comment the minimum that he needs is:

JSON:
{ "timestamp":"2021-06-09T12:31:04Z", "event":"FSDJump", "StarSystem":"Blia Chria YO-A c11", "StarPos":[-25504.43750,111.00000,52719.00000] }

(But I think the timestamp isn't really relevant.)
 
It just draws the line in white, for now. Normally there is a separate file per play session, so I have thousands of them (for example). I'll think about ways of maybe choosing a color when you import, or something. I'll give it some thought.

But yeah, that latter JSON is basically the right idea. You can leave out the timestamp and the system name. As long as it gets the event name and StarPos section, it should work.
 
If you're running EDDiscovery then you can export a journal view as a file of JSON journal entries, so just filter a view to jumps only and export it as journals and you have one big journal file with all the info Orvidius needs.

(It's an option in the dialog that pops up if you click the button for export to excel, just to keep it nicely hidden :D)
 
OK, I managed to hack in a color selector. Just make sure to select the color before the files, because it starts drawing immediately when files are selected.

EDIT: Fun fact: The color buttons still work while it's importing a long list of files. The change will be noticed on the next file it draws.
 
Last edited:
I've made a lot of spaghetti around the bubble over the last 4 years. It's amusing that the large tangled mess going out to the upper left isn't aimed at Colonia, but rather the Temple region, Crescent Nebula, etc. A good bulk of it is from the Glorious HIPs, since that contains both of my slices in that huge knot.

EDIT: I've been stress-testing it with my own data. It seems to handle 4 years of journals.

bubble-orvidius.png
 
Last edited:
I've changed the interactive galaxy map a little bit. I've split out the sector/region overlays to be actual overlays, instead of baked into a few maps. This means you can use any of the base maps with them, and you can even turn on both sets of overlays together. Here's an example using the alternate/indexed heat map, and both overlays:

https://edastro.com/galmap/?layer=indexedheat&overlay=regionlines,sectorlines
 
Do you have any plans to include political maps, by allegiance or government type?

So far I haven't been tracking those at all, and there wouldn't be a lot to see at the galactic scale. Some bubble-focused maps might be possible. So I'd say "no" in the short term, but it's still possible. I'd have to add tracking for it first though.
 
I'm flying on PS4, so sadly no third party tools (except the ones that are web-based).
And thank you for the help to all of you :)
I'm assuming you actually managed to sort this yourself by now, but if not (or if anyone else is in a similar position) I've added the ability to EDJP to read a text file of systems (say, from the EDSM "Export" option) and look up the coordinates with a dump of the "Systems With Coordinates" file from EDSM Nightly dumps and export those as CSV or JSON; you'd want JSON. You don't need to do the other bits for EDJP; reading journals etc - this bit just needs the system list text file and the EDSM dump.

Rather than pollute the EDAstro thread further, throw any queries/problems in the EDJP thread
 
I'm probably not going to leave this on the server for long, so if you want it, go ahead and grab it sooner rather than later. I may delete it at the end of the week or something.

Anyway, I have a file of candidate landables for Odyssey from the existing body data. This is looking specifically at surface pressure between 0.001 and 0.1 atmospheres. Not all of these will actually be landable, and of the ones that are, not all of them will allow disembarking on foot either (for instance, maybe due to temperature or gravity limits). It's 21 million bodies, with information about parent orbits and stars, presence of rings, etc.

Currently 1.7 GB as a ZIP file, 8 GB uncompressed CSV.

https://edastro.com/tmp/odyssey-landable-candidates.zip
 
Another small update-- The travel history video creator will now also generate a small CSV spreadsheet of your jump stats, broken out by ship type.

I ran my entire set of journals through it as a test. Heh, I'm not all that surprised that the AspX is still my most used ship... except that I've only used it in short bursts for the last few years, and probably the bulk of its use was back in 2017 when I explored with it pretty exclusively (and a little with the Anaconda). Yikes.

CommanderShipJumpsLightyears
OrvidiusAll
62483​
4238917.304​
OrvidiusAlliance Chieftain
269​
9404.647862​
OrvidiusAnaconda
5078​
460585.2509​
OrvidiusApex Taxi
50​
797.4945228​
OrvidiusAsp Explorer
14784​
780092.3467​
OrvidiusBeluga Liner
3779​
292494.7978​
OrvidiusCobra Mk.III
515​
9071.728845​
OrvidiusCobra Mk.IV
9​
238.3267118​
OrvidiusDiamondback Explorer
1864​
114046.7081​
OrvidiusDolphin
33​
1227.655201​
OrvidiusEagle
118​
3660.847409​
OrvidiusFederal Assault ship
67​
1354.196381​
OrvidiusFederal Corvette
568​
9503.704638​
OrvidiusFederal Gunship
4​
55.18923478​
OrvidiusFer de Lance
143​
2160.703294​
OrvidiusHauler
36​
987.1106269​
OrvidiusImperial Clipper
726​
35140.87227​
OrvidiusImperial Courier
2950​
122085.1428​
OrvidiusImperial Cutter
557​
14294.41358​
OrvidiusImperial Eagle
235​
9104.159784​
OrvidiusKeelback
6​
210.119002​
OrvidiusKrait Mk.II
10414​
806553.9631​
OrvidiusKrait Phantom
6214​
631527.3747​
OrvidiusMamba
9​
307.3845428​
OrvidiusOrca
2423​
202373.3743​
OrvidiusPython
3737​
240038.8285​
OrvidiusSidewinder
18​
237.3030779​
OrvidiusType-10 Defender
304​
8254.655011​
OrvidiusType-6 Transporter
1263​
48282.61693​
OrvidiusType-7 Transporter
3762​
257988.4733​
OrvidiusType-9 Heavy
2496​
176310.1677​
OrvidiusViper Mk.IV
41​
386.0758282​
OrvidiusVulture
11​
141.6713575​
 
Top Bottom