ED Astrometrics: Maps and Visualizations

That's been the case for, well more years than I have been playing the game, and that's a long time, didn't realise that's what you were commenting on. There are weird entries, I have come across quite a few myself, they haven't been fixed and probably won't be because while we players find a few odd things, with 400b stars and most of the galaxy unexplored there are probably tens of thousands or even millions of examples that players have not yet come across and that would take a long time and a lot of dev time and effort to go through. They will probably never be fixed, the others I have come across haven't been.
To be clear, I wasn't the one complaining about it, for the purposes of this data dump it's a non-issue. Other tools like EDSM do have the correct coordinates for the star CRYPTON1X mentioned, so there might be something in the data pipeline for Orvidius to take a look at. But there's a ton of ways that can happen; I'd tend to initially suspect bad journal data from some player's client.
 
To be clear, I wasn't the one complaining about it, for the purposes of this data dump it's a non-issue. Other tools like EDSM do have the correct coordinates for the star CRYPTON1X mentioned, so there might be something in the data pipeline for Orvidius to take a look at. But there's a ton of ways that can happen; I'd tend to initially suspect bad journal data from some player's client.

A lot of data from early reports was done manually, that is by manually entering the data into forms before the API was available for automatic updating, so that's probably where a lot of erroneous data originates, people make mistakes, but there are areas where the data is impossible to correct due to actual data in the galmap, systems with identical names but different 64 bit ID's for instance cause many issues. I think in an undertaking the size of the galaxy simulation there are going to be odd problems, I mean it is the first time it's ever been done, and no-one has tried to duplicate it since.
 
Yeah, there are tons of ways to get erroneous data. If someone travels there and sends the correct coordinates to EDDN, we should get the update.
 
Yeah, there are tons of ways to get erroneous data. If someone travels there and sends the correct coordinates to EDDN, we should get the update.

Yeah I traveled around a lot when I first started playing correcting some old data, I still do it for the suspicious data spreadsheet in Astrometrics, although a some of it can't really be fixed due to the problem of identical star system names causing problems.
 
I noticed that the standard deviations and averages for the radii of black holes and neutron stars are brouken and show exactly 0. Perhaps the result is so small that it is being rounded off
 

Attachments

  • изображение_2025-09-29_222149658.png
    изображение_2025-09-29_222149658.png
    22.7 KB · Views: 32
  • изображение_2025-09-29_222314379.png
    изображение_2025-09-29_222314379.png
    22.7 KB · Views: 25
Hello,

Astrometrics is such a great site - love it!

When looking at short-period-planets.csv (literally orbital periods of one hour or less) I see "Orbital Period" values between 13 and 999613. Would you please help me understand this value?
 
Hello,

Astrometrics is such a great site - love it!

When looking at short-period-planets.csv (literally orbital periods of one hour or less) I see "Orbital Period" values between 13 and 999613. Would you please help me understand this value?
It's "four hours or less", not "one hour or less."

Also the values of the orbital period are between 0.00326545 (ignoring the ridiculous low value of the systemless body) and 0.169998 - so what are you talking about?
 
It's "four hours or less", not "one hour or less."
You're right - I downloaded from this old link which mentions 1 hour or less. This got upgraded to 4 hr it seems.
Also the values of the orbital period are between 0.00326545 (ignoring the ridiculous low value of the systemless body) and 0.169998 - so what are you talking about
Thanks to your comment, I rechecked the file - it seems Excel got the import incorrect. Sorry - never trust MS :)
1762111592014.png
 
The solution seems to be avoiding any locale possible error:
  1. open .csv in text editor
  2. replace all ',' with sth else like '|'
  3. replace all '.' with locale decimal point (in my case ',')
  4. save
  5. import in Excel
Now I can use the sheet to find a suitable view to park when logging off
1762199280882.png
 
Or just use the importer...


And also change the decimal separator (before importing I guess):

 
Back
Top Bottom