[Request] Include body scanned and mapped timestamps in API download

[Darkcyde13]

When updating utilities by downloading a players EDSM logs, can you include the scanned and mapped timestamps of bodies please?

I use a 3rd party utility called EDDI, which I can use to obtain my EDSM logs that are then included in it's database. There have been a couple of occasions where some data has become corrupted in that database. A recent update accidentally voided some body scanned and mapped timestamps, and I had hoped that by reobtaining my EDSM logs, that I could repair that 'damage'. However, I found out that those two properties are not included in the EDSM log downloads, and so I am unable to rectify the issue that way.

So, I was wondering if they could be included at some point in the future please? EDSM records them, so I think it would make sense to include them.

Thankyou for your hard work on EDSM! :)

[klightspeed]

I think that would require EDSM to take an optional commanderName and apiKey parameters to the api-system-v1/bodies API endpoint, and use those to get commander-specific data for bodies in the system, and EDDI to be updated to set those parameters and update the scanned and mapped times from the returned data.

Perhaps as an alternative, it might be an idea to ask in https://github.com/EDCD/EDDI/issues if it'd be possible to add the option to re-generate the stored system data from the journal files on your computer.

[Darkcyde13]

Thank you for the reply. I must confess I don't really know what the EDSM API is capable of supplying to 3rd party programs, and it was a dev from EDDI that suggested I make the request here. I imagine that kind of info needs to be made available first, before EDDI can be updated to use it.

I will make your alternative suggestion on the EDDI page, and see what they think. Thank you! 😄

Edit: I just occurred to me, that EDDI rescanning the Journal files wouldn't work if the Journals are missing (after a reinstall, for example). EDDI downloads all of the players logs from EDSM, when requested to do so, so doesn't that already have a method of identifying the Commander to be able to do this?

[Tkael]

Re-scanning old journals is not currently part of EDDI's design structure (and could end up being a complicated solution as a result), but we'll certainly consider that option as well.

Perhaps the data could be added to the https://www.edsm.net/api-logs-v1/get-logs endpoint? This is already a personal exploration / travel focused endpoint that requires commanderName and apiKey parameters. I think this API powers the https://www.edsm.net/en/user/flight-logs/... section of the website and if so then the same information could be used to expand that section of the website to include more detailed exploration data (e.g. where was that Earth-like I found the other day?).