CETI (CH3X's EDSM Toolkit Interface)

[Ch3x]

Greetings CMDRs,

Some weeks ago I posted a small script to the QTFR thread that reads the copy/paste clipboard to check EDSM for the visitation status of a system, via the copy to clipboard button from the galaxy map in-game. I have finished it (mostly) and released it as a package or the raw source for you all to use how you'd like. Assuming a system has not been logged on the database, the system is deemed "Not Visited". If it is visited, the EDSM button turns green and you can click it to pull up the webpage for that system. The keybind toggle minimizes/maximizes the interface, thus match this keybind to the one you use for the galaxy map. A csv file is created to save the configuration (keybind & colors) of the interface along with any copied systems that you want to save by pressing the save button. The "Find Nearby" button prompts the user to input the galactic coordinates of the system as seen from the galaxy map, just target focus the system and input to the best of your ability along with a radius to check for a the nearest visited system. Any bugs or issues can be raised in this thread. o7

EDIT:
Version 1.3 is now out, no more copy/paste clipboard monitor. The app now monitors the player journal for if the galaxy map is open and reads the selected target ie. the next system in route or targeted. Did some organizing for the next update where I will add more databases to be queried like Spansh and Edastro.

Github repo/release:

GitHub - carsonbfl/CETI: CH3X's EDSM Toolkit Interface (CETI). Overlay tool for Elite: Dangerous that checks system visitation status via the EDSM API.

CH3X's EDSM Toolkit Interface (CETI). Overlay tool for Elite: Dangerous that checks system visitation status via the EDSM API. - carsonbfl/CETI

github.com

Not visited system check:

Find Nearby Summary:

 

[marx]

Hey, that's quite nice. Thanks! As a feature request, would you mind extending this to sites that have more systems in their database than EDSM does? You see, EDSM automatically deletes systems from its database, those from EDSM accounts which were auto-purged if they haven't logged in in two years. As far as I know, no other site does data auto-removals like this.

Your best bet might be EDAstro (see their API documentation here), since it still watches the EDSM database dumps and adds systems from there, also those that EDSM doesn't send to EDDN. Spansh is also good, but they no longer import data from EDSM.

Mind you, the difference isn't huge, right now it's 1.2 million visited systems missing from EDSM - but it does mean that you could query a system that was uploaded before but isn't returned as found by EDSM today. So, extending your tool to cover more sites would mean better results.

 

[LCU No Fool Like One]

Hey, that's quite nice. Thanks! As a feature request, would you mind extending this to sites that have more systems in their database than EDSM does? You see, EDSM automatically deletes systems from its database, those from EDSM accounts which were auto-purged if they haven't logged in in two years. As far as I know, no other site does data auto-removals like this.

Your best bet might be EDAstro (see their API documentation here), since it still watches the EDSM database dumps and adds systems from there, also those that EDSM doesn't send to EDDN. Spansh is also good, but they no longer import data from EDSM.

Mind you, the difference isn't huge, right now it's 1.2 million visited systems missing from EDSM - but it does mean that you could query a system that was uploaded before but isn't returned as found by EDSM today. So, extending your tool to cover more sites would mean better results.

It looks like it is using the edsm sphere systems API to find systems within a sphere. You could probably use the spansh API to do a similar search. I think a limitation might be that for you to have the x,y,z coordinates to search on, the reference system would need to be in the database already.

 

[Addinator]

I gave your repo a star, because I like projects like these, nice work.

 

[Ch3x]

It looks like it is using the edsm sphere systems API to find systems within a sphere. You could probably use the spansh API to do a similar search. I think a limitation might be that for you to have the x,y,z coordinates to search on, the reference system would need to be in the database already.

So as of now, the reference system in the search is just whatever was copied last, not necessarily what XYZ you input. Therefore, the EDSM api handles the search given the coords alone and it was a bit of an oversight on my part, but it does indeed work in that regard. Currently, I am writing a new release to incorporate Spansh, Edastro, etc. Additionally, I have been told that the journal has a targeted system event that I could use instead of the copy/paste clipboard, which is how SRV Survey does it, so I will add that option as well. The idea of this script was for quick observations of systems at a glance, and if you target a system in the galmap, the camera refocuses and is a bit slower than pressing the copy to clipboard button. I appreciate the kind feedback and suggestions o7.