Release EDSM - Elite Dangerous Star Map

Can you detail? I didnot not understand!

This number does not update as logs are submitted, it changes only after 15-30 minutes.

2016-02-18_1857.png
 
Has there been an update of some sort for the db? The amount of systems that needs more coordinates have dropped by about 100k today (from ~160k to ~60k) , and it feels unlikely that its due to manual updates.
Yes some time ago we change a little our database because finding those started to take some time and it was not performant anymore.
What we did is that we added a static field for each system containing the number of known references, so we can ask for less systems at one point and have good performance.

At first that fiels was set to NULL, and it is populated when the system is asked. What I did in the last two days is running our bot against the database to check the coordinates.
It corresponds to the 100K, so they are now filled with the right number of known references.


This number does not update as logs are submitted, it changes only after 15-30 minutes.

http://content.screencast.com/users...31-4ed4-934c-4ac2f2879f06/2016-02-18_1857.png

That part is in cache :)
I changed it because I added the search input so people can transfer duplicate systems, so I took the home stat value which is cached.
 
It is not updated yet, but we should have 100000 systems with coordinates now :)

UPD: yep, 100118 atm! Yay!
 
Last edited:
What I did in the last two days is running our bot against the database to check the coordinates.
It corresponds to the 100K, so they are now filled with the right number of known references.

I was wondering how the systems missing coords could fill up so fast a few days ago, and suddenly take a huge dive starting yesterday. I imagined that the db algo had been upgraded, just wanted to check :)

On another note, it seems as there is some issue with the server atm, unable to open system data for trilateration

(which means that I have to look at approaching planets instead of filling distances :) )
 
Last edited:
I guess the server decided to celebrate milestone with some downtime :D

ps: Kzasch, EDDiscovery seems to be still working and able to send distances.
 
Last edited:
I guess the server decided to celebrate milestone with some downtime :D

ps: Kzasch, EDDiscovery seems to be still working and able to send distances.

edsm.net is working for me except the the system sites where you can enter the distances on the site itself. EDD still works.
 
seems to work again.

Since I add alot of distances to GU Muscae and apperently others do too I think it would be a good idea to
show the distances on multiple pages. More then 2000 distances on one page is some loading time.
 
That part is in cache :)
I changed it because I added the search input so people can transfer duplicate systems, so I took the home stat value which is cached.

Well, I am bypassing your cache because I need the accurate current number, so I am doing a fetch of all ~5800 logs on the API and counting them myself. :)
 
I really wish there was a 'wrong star entered' button, I just entered a bunch of coordinates for a star, thought I had the wrong star, then did it again... all my references are thus flagged as 'hidden' even though they're valid.

Alternatively 'this distance is hidden, unhide it?' button, maybe?

I have to go update HIP 72739 and Praea Euq JO-W B3-2 now.... and I can't use a half dozen systems I normally use because they're hidden.
 
After much investigation :p
It's a problem when playing around midnight !

EDD should keep track of the last hour in logs, if the hour goes from 23 to 0 (Better new hour inferior to the last hour); then one day should be added to the date.

Finally got time and tracked it down; it's more interesting than that. There's a whole pile of systems which were actually entered a full day later. They are in a different log file and everything. Not sure (yet) why EDD got confused. Is there a way to manually fix the dates? If I delete the incorrect entries and re-import, I'll lose my notes. I've also got to figure out a way to fix up my EDD database.
 
If your comments are synced with EDSM, they're safe. Tell me you CMDR name, and I'll take a look.

It's in my sig ;) - Myshka.

Here's some (there's plenty more) :

EDD (newer top):
Code:
[COLOR="#00FF00"]OK:
[/COLOR]13/02/2016 01:42:37	Speamoea LQ-U c4-31			28.58
13/02/2016 01:41:28	Speamoea RF-R b8-7			1525.24

[COLOR="#FF0000"]WRONG DATE:[/COLOR]
13/02/2016 01:37:14	Schienaei RT-O c7-23		31.00
13/02/2016 01:35:19	Schienaei KH-U d3-107		30.46
13/02/2016 01:33:30	Schienaei GB-W d2-381		30.60
13/02/2016 01:31:40	Schienaei NC-S c5-2			30.46
13/02/2016 01:28:19	Schienaei AF-A f89			

[COLOR="#00FF00"]OK:
[/COLOR]13/02/2016 01:19:33	Speamoea DE-Y c2-23			30.05
13/02/2016 01:18:03	Speamoea DE-Y c2-8			30.91

Elite Log:
Code:
[B]netLog.160213231003.01.log (14/02/2016 02:32):[/B]
{01:37:14} System:23(Schienaei RT-O c7-23) Body:0 Pos:(6.19111e+009,-9.32987e+009,-1.14993e+010) Supercruise
[B]
netLog.160212225018.01.log 13/02/2016 04:06):[/B]
{01:19:33} System:23(Speamoea DE-Y c2-23) Body:1 Pos:(-1.12057e+010,-7.42981e+009,-8.80149e+009) Supercruise
{01:41:28} System:7(Speamoea RF-R b8-7) Body:1 Pos:(-1.65693e+009,-1.5351e+010,-1.469e+009) Supercruise
{01:42:37} System:31(Speamoea LQ-U c4-31) Body:1 Pos:(-5.1661e+009,-1.46539e+010,3.43454e+009) Supercruise
{01:51:49} System:31(Speamoea LQ-U c4-31) Body:1 Pos:(-2.00059e+007,-8.50109e+008,-1.18352e+007) NormalFlight
{01:51:50} System:31(Speamoea LQ-U c4-31) Body:1 Pos:(-2.00059e+007,-8.50109e+008,-1.18352e+007) NormalFlight
{01:51:50} System:31(Speamoea LQ-U c4-31) Body:1 Pos:(-2.00059e+007,-8.50109e+008,-1.18352e+007) NormalFlight
{01:52:38} System:31(Speamoea LQ-U c4-31) Body:1 Pos:(-2.00081e+007,-8.50109e+008,-1.18372e+007) NormalFlight
...
{01:54:10} System:3(Speamoea FT-L b11-3) Body:1 Pos:(1.45133e+010,-4.2486e+009,-4.29585e+009) Supercruise
{03:28:32} System:543(Speamoea WU-E d12-543) Body:13 Pos:(-65132.3,-569151,-222745) NormalFlight
{03:28:33} System:543(Speamoea WU-E d12-543) Body:13 Pos:(-63298.4,-569277,-225727) NormalFlight

But anyway, I'll fix up my EDD database first - will it fix the entries in EDSM if I do a full sync again after that?
 
Last edited:
Didn't see your sig ;)
You have 207 comments stored at EDSM.
I'm unsure what gets synced in which directions, you should probably delete a wrong EDSM exploration log entry, fix the date in your local EDD DB, then sync again, and take a look at the result.
 
Didn't see your sig ;)
You have 207 comments stored at EDSM.
I'm unsure what gets synced in which directions, you should probably delete a wrong EDSM exploration log entry, fix the date in your local EDD DB, then sync again, and take a look at the result.

Yeah, fixing up my local EDD database, and going to go from there. Noticed that most (all?) of the incorrect entries are actually in the EDD DB twice, once assigned to a hidden Commander index "-2".
 
Error in distance between "Wredguia WG-Y b55-3" and "Wredguia QY-D b39-0"

The distance was calculated as 844.71 LY, it's actually 844.75 LY. Got a screenshot if you want confirmation.

Another issue is with Wredguia XI-T b58-5 , in order to get coordinates for it I had to remove/hide the correct distance to some system that I cant remember (968.64 LY or something), and then it complains for the measured distance of 67.70 LY to Wredguia JV-Y b55-2 , it instead wants it to be 67.77 LY.

Seems to be an sissue with Wredguia JV-Y b55-2 , another error now from Wredguia JO-X c28-10

Do you have a suggestion on what I should do with these errors, should I just hide the distances, or leave them visible and report when I find something?

I've also had some issues adding distances to the following systems, there's some issue with the system names:

Ghost of Jupiter Sector JR-W c1-4
HIP 101141
Wregeia XC-T b58-9
Plaa Euek FQ-A b55-1
Lupus Dark Region B Sector GG-Y d86
NLTT 5457
Lupus Dark Region B Sector PH-V b2-5
Ophiuchus Dark Region B Sector EB-X c1-7
Synuefai FZ-Z b49-0
Plaa Euek FQ-A b55-1
Core Sys Sector CB-0 a6-2
 
Last edited:
Back
Top Bottom