Release EDSM - Elite Dangerous Star Map

I think system DM99 49 has wrong coordinates. I should be somewhere near 374, -299, -1367.7.
http://www.edsm.net/show-system/index/id/54379/name/DM99+49

DM99 49 - TYC 705-795-1 is one of the wrong distances. It should be around 50 LY, not 12.
There are 2 systems with that name in the game. I addeed the new one under DM99 49 (Alternative) and divided the distances to the systems.

- - - - - Additional Content Posted / Auto Merge - - - - -

Now I have something to do for today, only 13 Jumps away from Thailae AR-T d4-44.
Real hard nut. Trilat for the third time now. We have 2 distances now with an error of 0.01 Ly and one very wrong.
 
I am still in that system if you need any confirmation.

edit: checked the distance to sol again, was a typo from me, looks good now
 
Last edited:
More:

HD 152002
Ploi Aics RY-H d10-0

Ploi Aics RY-H d10-0 seems the same as Thailae AR-T d4-44. Coordinates may be a bit off and sometimes you get a good distance and another times you get a wrong one by one or two decimals.
 
Real hard nut. Trilat for the third time now. We have 2 distances now with an error of 0.01 Ly and one very wrong.
Thailae JU-J c11-2's trilateration was based on old Thailae AR-T d4-44's coordinates. So the error propagated and they are a bit off. This may also apply to the second incorrect system.
 
I'm curious about the two amber distances to Thailae AR-T d4-44 & Fine Ring Sector WE-Q b5-5.

The distances to Fine Ring Sector WE-Q b5-5 & Thailae JU-J c11-2 (i think you mean this two) are having rounding errors. Their userinput is correct in both cases. I used the check suspicous distance feature to confirm them on the site.
 
More:

HD 152002
Ploi Aics RY-H d10-0

Ploi Aics RY-H d10-0 seems the same as Thailae AR-T d4-44. Coordinates may be a bit off and sometimes you get a good distance and another times you get a wrong one by one or two decimals.
HD 152002 had a wrong name. Sorted, pushed, tnx.
Ploi Aics RY-H d10-0 was a bit wrong, looks good now.

- - - - - Additional Content Posted / Auto Merge - - - - -

The distances to Fine Ring Sector WE-Q b5-5 & Thailae JU-J c11-2 (i think you mean this two) are having rounding errors. Their userinput is correct in both cases. I used the check suspicous distance feature to confirm them on the site.


Yes, I meant those two. Thanks for verifying. I think there is still a strange error or race condition when calculating the distances.
 
Yes, I meant those two. Thanks for verifying. I think there is still a strange error or race condition when calculating the distances.
I still think this is a propagated error. Thailae AR-T d4-44 had wrong coordinates for one reason or another. Some other systems were trilaterated based on these coordinates resulting in their coordinates being wrong as well.

Thailae JU-J c11-2:
Coordinates found for that system: 1756.09375 / -253.3125 / 4545.25
Coordinates mismatch with stored coordinates: 1756.09375 / -253.28125 / 4545.25

Fine Ring Sector WE-Q b5-5:
Coordinates found for that system: 525.84375 / 9.0625 / 877.09375
Coordinates mismatch with stored coordinates: 525.84375 / 9.03125 / 877.09375
 
Last edited:
Could someone post some extra distances for http://www.edsm.net/show-system/index/id/22564/name/Sifi+BL-A+c16 - but be careful! Galaxy map may default to Sifi BL-A c16-0 instead of c16 only. This system's been taunting me for a while now, but I'm not being helpful spamming distances only from roughly one direction it seems...

Also username Angel Tweed has a rather long chain of single decimal distances starting from that system in both directions, although at some point they do change into two decimal distances; might be worth looking into in any case?
 
Could someone post some extra distances for http://www.edsm.net/show-system/index/id/22564/name/Sifi+BL-A+c16 - but be careful! Galaxy map may default to Sifi BL-A c16-0 instead of c16 only. This system's been taunting me for a while now, but I'm not being helpful spamming distances only from roughly one direction it seems...

Also username Angel Tweed has a rather long chain of single decimal distances starting from that system in both directions, although at some point they do change into two decimal distances; might be worth looking into in any case?
Pushed it to front, needs more distances.
And for small distances with one decimal only (mostly probably from nav panel or HUD instead of GM) we can only wait until more referencing distances have been collected. But thanks for pointing there, will watch.

- - - - - Additional Content Posted / Auto Merge - - - - -

i accedently found a bug on EDDiscovery and submitted wrong data. fixed it on the site but need new calculation since the check wrong distances funvtion doesn't do this doesn't do this.
http://www.edsm.net/show-system/index/id/520557/name/Thailae+PO-T+b22-3
It checks, and it tells the coordinates are wrong, but a "normal" user can't reset the coordinates to make them calculated once more. Maybe we'll increase the tiny circle of "coordinate's masters" in future.
Good now, tnx.
 
Last edited:
Pushed it to front, needs more distances.
And for small distances with one decimal only (mostly probably from nav panel or HUD instead of GM) we can only wait until more referencing distances have been collected. But thanks for pointing there, will watch.

I am not sure but i think EDDiscovery submits only one decimal when the second one is a Zero (like 32.20 would be 32.2) .

Because I found a distance from me that has only one decimal and I always type in both. In that case the decimal is correct and also works as intended.
 
i've accidentally inserted distances for trilaterate the wrong system and now i don't know how to remove.
The wrong system is: Bleia Eohn OF-I b29-1 (490932)

Sorry
 
I am not sure but i think EDDiscovery submits only one decimal when the second one is a Zero (like 32.20 would be 32.2) .

Because I found a distance from me that has only one decimal and I always type in both. In that case the decimal is correct and also works as intended.

This is true. But when someone has a dozen distances in a row with only one decimal, one starts to suspect they have not taken readings from galaxy map with two decimals, but instead just typed in whatever cockpit HUD gives you (which gives you 1 decimal accuracy for distances >=10, or 2 decimals for distances <10)

Also cockpit HUD calculates distance based on your current position within a given system, so you only get accurate reading with two decimals if you're relatively near (well, within 160k or so LS) the main star of the system. It is inadvisable to use cockpit HUD/NAV computer display for distances unless you really know what you're doing.
 
Last edited:
This is true. But when someone has a dozen distances in a row with only one decimal, one starts to suspect they have not taken readings from galaxy map with two decimals, but instead just typed in whatever cockpit HUD gives you (which gives you 1 decimal accuracy for distances >=10, or 2 decimals for distances <10)

Also cockpit HUD calculates distance based on your current position within a given system, so you only get accurate reading with two decimals if you're relatively near (well, within 160k or so LS) the main star of the system. It is inadvisable to use cockpit HUD/NAV computer display for distances unless you really know what you're doing.


As I said, that is the only case in that one decimal is ok. But when there are a bunch of distances with only one decimal and the distance is under 30ly from the same CMDR (afaik the hud doesn't show Systems further away unless you mark it on the GM) it is very suspicous and have to be checked.
 
I am not sure but i think EDDiscovery submits only one decimal when the second one is a Zero (like 32.20 would be 32.2) .
Yes, it does. And this is ok. EDSM doesn't show the second decimal if it's a "0", f.ex. 123.40 Ly is displayed as 123.4 Ly. I have some distances submitted without any decimal, and they're correct. OK, happens 1 of 100 times... ;)

BTW, main reason for posting: We just passed the mark of 1.000.000 flight log entries!
 
Last edited:
Back
Top Bottom