This is my latest project, inspired by @Lance 'Spacecat' D.'s thread here to "[Clean] up the Galaxy's bad data".
Whenever I fly from A to B, I am trying to make sure that as many of the intervening stars are in EDSM's set of those with estimated coordinates.
You can find the list of estimated coordinates within EDSM's systemsWithoutCoordinates JSON. It contains both those systems without any coordinates, represented as, for example,
{"id":45890,"id64":215763307643,"name":"Nyeajoa YQ-B d14-6","date":"2015-06-01 03:51:19"},
as well as those where the coordinates are estimated based on distances manually entered and such; for example:
{"id":45892,"id64":2277305391266,"name":"Nyeajaae AT-U c18-8","estimatedCoordinates":{"x":-3325,"y":-445,"z":7435,"precision":35},"date":"2015-06-01 03:51:19"}
Note the different name for the field, it's "coords" in the "proper" systems.
So I have a few suggestions based on other topics here, if people would like to help me^H^H EDSM clear out this inaccurate data.
Warning: long-term project - there's currently just under 1.9 million of them, and that's only those with estimates.
FIrst, @Spansh: you provide a route plotter which can plot a route using Neutron Stars, which the pilot has to manually fill in with jumps calculated using the in-game Galaxy Map. If you were to use these estimatedCoordinates as input to a similar plotter, then perhaps people could do more automatically what I'm kinda doing now - determine an overall route to wherever using your plotter but which will take in estimated systems along the way.
Second, I was going to suggest a vistedStars.txt version of the file, but apparently FDev have disabled this working (see here). However, if they do restore it at some point, a similar file could be produced for PC users based upon the estimated systems, then people can check for them in the Galaxy Map while they're roaming. However, I don't know any more about this, if it works with just system names then fine, but if it requires the coordinates too then of course by definition that is a problem! Also, some kind of filtering tool to produce a file based on, say, a radius around the current position, or within one game sector, would probably be useful. Just putting the idea out there.
Third, there is @Esvandiary's system coordinate generator on their EDTS Web site, which can give estimated coordinates for procgen systems. Now I'm not suggesting that the site is hammered with millions of requests to fill in estimated coordinates for those systems with no coordinates (making them include-able in the above suggestions), but perhaps Esvandiary could produce an estimated coordinates file based upon the no-coordinate systems in EDSM's data, or the code from that site incorporated in other data stores to do the same to their locally-held data, and then visibility of the systems to be cleared is increased.
Anyway, that's just my thoughts at the moment, if anyone's interested in joining in!
Stay safe o7
Whenever I fly from A to B, I am trying to make sure that as many of the intervening stars are in EDSM's set of those with estimated coordinates.
You can find the list of estimated coordinates within EDSM's systemsWithoutCoordinates JSON. It contains both those systems without any coordinates, represented as, for example,
{"id":45890,"id64":215763307643,"name":"Nyeajoa YQ-B d14-6","date":"2015-06-01 03:51:19"},
as well as those where the coordinates are estimated based on distances manually entered and such; for example:
{"id":45892,"id64":2277305391266,"name":"Nyeajaae AT-U c18-8","estimatedCoordinates":{"x":-3325,"y":-445,"z":7435,"precision":35},"date":"2015-06-01 03:51:19"}
Note the different name for the field, it's "coords" in the "proper" systems.
So I have a few suggestions based on other topics here, if people would like to help me^H^H EDSM clear out this inaccurate data.
Warning: long-term project - there's currently just under 1.9 million of them, and that's only those with estimates.
FIrst, @Spansh: you provide a route plotter which can plot a route using Neutron Stars, which the pilot has to manually fill in with jumps calculated using the in-game Galaxy Map. If you were to use these estimatedCoordinates as input to a similar plotter, then perhaps people could do more automatically what I'm kinda doing now - determine an overall route to wherever using your plotter but which will take in estimated systems along the way.
Second, I was going to suggest a vistedStars.txt version of the file, but apparently FDev have disabled this working (see here). However, if they do restore it at some point, a similar file could be produced for PC users based upon the estimated systems, then people can check for them in the Galaxy Map while they're roaming. However, I don't know any more about this, if it works with just system names then fine, but if it requires the coordinates too then of course by definition that is a problem! Also, some kind of filtering tool to produce a file based on, say, a radius around the current position, or within one game sector, would probably be useful. Just putting the idea out there.
Third, there is @Esvandiary's system coordinate generator on their EDTS Web site, which can give estimated coordinates for procgen systems. Now I'm not suggesting that the site is hammered with millions of requests to fill in estimated coordinates for those systems with no coordinates (making them include-able in the above suggestions), but perhaps Esvandiary could produce an estimated coordinates file based upon the no-coordinate systems in EDSM's data, or the code from that site incorporated in other data stores to do the same to their locally-held data, and then visibility of the systems to be cleared is increased.
Anyway, that's just my thoughts at the moment, if anyone's interested in joining in!
Stay safe o7
