Argh, spent like ten minutes searching for this on Exploration forum... whenever did this get moved to the API section.
Anyway, system named 2 MASS J02360396+6125070 in EDSM has a space in "2 MASS", while Elite Dangerous galaxy map designation is 2MASS (without space) - problems mainly with copypaste and "nothing found" then spend a few minutes wondering what's wrong.
Anyway, system named 2 MASS J02360396+6125070 in EDSM has a space in "2 MASS", while Elite Dangerous galaxy map designation is 2MASS (without space) - problems mainly with copypaste and "nothing found" then spend a few minutes wondering what's wrong.
Thanks, system renamed.
I did something similar for my XTE/GRS/OGLE project.
There are a number of systems that are impossible to reach. Not "just need some jumponium" distance, but "Not a chance in hell of ever reaching". A number of these are binary systems with a black hole companion and are outside the plane of the Galaxy.
eg. Cyngi X-3 is over 30,000ly from Sol. WAY beyond the edge of the galactic arm.
I took multiple measurements from a large number of systems among my way to lock down those coordinates. In lieu of visiting the systems in question, multiple distance readings from a spread of systems will yield results.
That's why Cygni X-3, KY Ursae Majoris, MM Velorum and other " impossible " systems are available to trilaterate against. The more systems that use them to trilaterate coordinates, the greater their "trust" becomes as their coordinates are constantly being reverified.
Hi,
I just came across a bit of a typo:
drojia mj-o d7 -21 (571698) http://www.edsm.net/show-system/index/id/571698/name/drojia+mj-o+d7+-21
Should be Drojia MJ-O D7-21 (no space after D7)
thanks
I just came across a bit of a typo:
drojia mj-o d7 -21 (571698) http://www.edsm.net/show-system/index/id/571698/name/drojia+mj-o+d7+-21
Should be Drojia MJ-O D7-21 (no space after D7)
thanks
Tnx to everyone who points up errors, typos etc., too many to mention everyone. I think we fixed everything reported until now. If we missed or overlooked something, or find anything new, please keep on reporting!
So I've been playing with EDSM for the past few days and came up to an idea. It might not be easy to do, so I'm not insisting. 
Whenever you input some letters to search box - it is trying to guess which system do you mean by suggesting several system names that start on these letters.
My suggestion is: somehow define guessed systems in the list (either by green/yellow background color, or by some symbol) so you could easily tell which of them have known coordinates and which don't.
Thank you for your attention.
Whenever you input some letters to search box - it is trying to guess which system do you mean by suggesting several system names that start on these letters.
My suggestion is: somehow define guessed systems in the list (either by green/yellow background color, or by some symbol) so you could easily tell which of them have known coordinates and which don't.
Thank you for your attention.
I entered distance data for one system into another system:
http://www.edsm.net/show-system/index/id/103014/name/Omega+Sector+YU-O+b6-5
I've hidden my original incorrect numbers and re-entered the same systems with correct distances and then entered another bunch of distances, but EDSM refuses to recalculate the position.
There should be a better way for me to fix my own mistakes than posting to a forum...
http://www.edsm.net/show-system/index/id/103014/name/Omega+Sector+YU-O+b6-5
I've hidden my original incorrect numbers and re-entered the same systems with correct distances and then entered another bunch of distances, but EDSM refuses to recalculate the position.
There should be a better way for me to fix my own mistakes than posting to a forum...
Yeah, I know about that. But I don't see/find any description of the response-json from a submit-distance. It seems to consists of three objects ("basesystem", "distances" and "systems") but there is no description for them.
There will be at some point. But forum is good for now.
We cannot let anyone change the coordinates but we have tools to track them.
Anyway it is fixed.
Do you need a description? I should redo those documentation some day.
Can clarify on Monday, if needed, I'm not at home right now.
A description (or just a full example/schema of an response json) would be nice, yes. Maddavo asked me to update the old EDSC script of TD for EDSM, but I failed at the distance response.
I ended up causing some incorrect data for Wredguia VA-R b49-0 ( http://www.edsm.net/show-system/index/id/587480/name/Wredguia+VA-R+b49-0 ). I have attempted to correct the mistake and added correct information in. When I run check coordinates it gives the correct coordinates, but continues to show with the incorrect ones. I get this result:
Coordinates found for that system: -683.1875 / 658.625 / -4.125
Coordinates mismatch with stored coordinates: -680.59375 / 639.78125 / -93.71875
Is there something I could do through the interface to fix this, or can it only be corrected by an admin of the system?
Nox
Coordinates found for that system: -683.1875 / 658.625 / -4.125
Coordinates mismatch with stored coordinates: -680.59375 / 639.78125 / -93.71875
Is there something I could do through the interface to fix this, or can it only be corrected by an admin of the system?
Nox
Last edited:
Thank you for constantly fixing bugs we report and make!
Here is another batch of false system pairs. Correct are marked green, incorrect - red.
Cephei Sector DL-Y c14 Cephei Sector ZE-A c15 -126.40625 / 20.09375 / -57.3125
Eagle Sector EL-Y d203 Byeia Eurk ID-F b39-3 -2036.8125 / 99.65625 / 6687.0625
Eagle Sector EL-Y d203 Plaa Aescs EB-G b11-5 -2036.8125 / 99.65625 / 6687.0625
Byeia Eurk ID-F b39-3 Plaa Aescs EB-G b11-5 -2036.8125 / 99.65625 / 6687.0625
Col 359 Sector ZF-P b9-0 Col 285 Sector VS-L b23-3 -331.34375 / 326.90625 / 322.4375
Antilae Sector CB-X c1-10 Antliae Sector CB-X c1-10 126.3125 / 114.65625 / 36.6875
(typo, Antliae is correct spelling)
Omega Sector YA-N b7-10 Byeia Eurk PC-M d7-127 -1449.46875 / -60.90625 / 5363.09375
Wredguia UB-U b30-2 Wredguia PV-V b29-4 -441.6875 / -4.375 / -415.21875
Preae Aec OT-Z d17 Preae Aec OT-Z d21 2516.21875 / 656.25 / 7982.09375
Wredguia OJ-G d11-10 Wredguia VA-R b49-0 -680.59375 / 639.78125 / -93.71875
(already reported)
Plaa Aescs FO-H b24-9 Ploi Aewsy UF-F d11-78 -1724.0625 / 124.59375 / 7135.28125
(Plaa Aescs FI-H b24-9 looks good but there are some incorrect distances there...)
Blae Eaec VY-Q d5-796 Blae Eaec IG-F b28-45 -1498.125 / -645.5 / 14902.40625
--------------------------
There are more systems that require "2 MASS" -> "2MASS" renaming or removal. I'm talking about removal because some of them already have correctly spelled counterpart with distances and coordinates. Some examples:
http://www.edsm.net/show-system/index/id/445652/name/2+MASS+J02211701+5708426 (with space)
http://www.edsm.net/show-system/index/id/440191/name/2MASS+J02211701+5708426 (without space)
(AFAIK 2MASS never has space between 2 and MASS)
http://www.edsm.net/show-system/index/id/445646/name/2+MASS+J02214692+5709538 (with space)
http://www.edsm.net/show-system/index/id/439669/name/2MASS+J02214692+5709538 (without space)
I'm not trying to enumerate all such entries. I think admins can query database much better than ordinary users.
Here is another batch of false system pairs. Correct are marked green, incorrect - red.
Cephei Sector DL-Y c14 Cephei Sector ZE-A c15 -126.40625 / 20.09375 / -57.3125
Eagle Sector EL-Y d203 Byeia Eurk ID-F b39-3 -2036.8125 / 99.65625 / 6687.0625
Eagle Sector EL-Y d203 Plaa Aescs EB-G b11-5 -2036.8125 / 99.65625 / 6687.0625
Byeia Eurk ID-F b39-3 Plaa Aescs EB-G b11-5 -2036.8125 / 99.65625 / 6687.0625
Col 359 Sector ZF-P b9-0 Col 285 Sector VS-L b23-3 -331.34375 / 326.90625 / 322.4375
Antilae Sector CB-X c1-10 Antliae Sector CB-X c1-10 126.3125 / 114.65625 / 36.6875
(typo, Antliae is correct spelling)
Omega Sector YA-N b7-10 Byeia Eurk PC-M d7-127 -1449.46875 / -60.90625 / 5363.09375
Wredguia UB-U b30-2 Wredguia PV-V b29-4 -441.6875 / -4.375 / -415.21875
Preae Aec OT-Z d17 Preae Aec OT-Z d21 2516.21875 / 656.25 / 7982.09375
Wredguia OJ-G d11-10 Wredguia VA-R b49-0 -680.59375 / 639.78125 / -93.71875
(already reported)
Plaa Aescs FO-H b24-9 Ploi Aewsy UF-F d11-78 -1724.0625 / 124.59375 / 7135.28125
(Plaa Aescs FI-H b24-9 looks good but there are some incorrect distances there...)
Blae Eaec VY-Q d5-796 Blae Eaec IG-F b28-45 -1498.125 / -645.5 / 14902.40625
--------------------------
There are more systems that require "2 MASS" -> "2MASS" renaming or removal. I'm talking about removal because some of them already have correctly spelled counterpart with distances and coordinates. Some examples:
http://www.edsm.net/show-system/index/id/445652/name/2+MASS+J02211701+5708426 (with space)
http://www.edsm.net/show-system/index/id/440191/name/2MASS+J02211701+5708426 (without space)
(AFAIK 2MASS never has space between 2 and MASS)
http://www.edsm.net/show-system/index/id/445646/name/2+MASS+J02214692+5709538 (with space)
http://www.edsm.net/show-system/index/id/439669/name/2MASS+J02214692+5709538 (without space)
I'm not trying to enumerate all such entries. I think admins can query database much better than ordinary users.
Thanks, it's fixed.
I'll send an email, when such mismatch are found.
For now, we can only make them by hand, cause I found 2 cases where the algorithm was correcting badly, should work now,
but better to check ourselves than having some systems moved without noticing.
Feature Request: Show distance between systems in log, if known, not just distance to Sol for triangulated systems.
I submit (almost) every jump distance, but only trilaterate every X'th system when "fast travelling". It would be nice to have the distances shown in my EDSM log. It would also be nice to either get a dump of my data in some format (CSV) so that I can do some analysis on it (eg, average time for a jump; actual distance travelled, etc)
If this is beyond the remit for the site, I guess I'll have to start coding up a tool. Are there Best Practices for using the API (eg, limit to the number of requests-per-second etc)?
I submit (almost) every jump distance, but only trilaterate every X'th system when "fast travelling". It would be nice to have the distances shown in my EDSM log. It would also be nice to either get a dump of my data in some format (CSV) so that I can do some analysis on it (eg, average time for a jump; actual distance travelled, etc)
If this is beyond the remit for the site, I guess I'll have to start coding up a tool. Are there Best Practices for using the API (eg, limit to the number of requests-per-second etc)?
So I've been playing with EDSM for the past few days and came up to an idea. It might not be easy to do, so I'm not insisting.
Whenever you input some letters to search box - it is trying to guess which system do you mean by suggesting several system names that start on these letters.
My suggestion is: somehow define guessed systems in the list (either by green/yellow background color, or by some symbol) so you could easily tell which of them have known coordinates and which don't.
Thank you for your attention.
Added to the suggestions
Enjoy.