Newcomer / Intro Galaxy Mapping question and First Discovery Question

1. I often use Inara, EDDB, EDDiscovery, and other 3rd-party tools to find the nearest station or fleet carrier which supplies an item or service (often Universal Cartographics) as I explore outside the bubble. The results are given in table form. Is there a way to obtain a 3d plot instead of a table? I often do not want the very closest entry (which might take me "backwards") but rather the nearest entry along my current intended route.

2. Is there a simple way using in-game or 3rd party tools to find my first discoveries and first mappings? I've seen this question asked many times in the past few years but not recently and I'm rather surprised that it seems that as of a few years ago there was still no easy way to accomplish this.
 
1) Probably the nearest you'll get to this is the 3D map in EDSM but YMMV using that... I'm also aware EDDiscovery has a 3D tool you can add as a tab on the main program. I,'ve never used it so I can't really advise as to its functionality or usefulness I'm afraid.

2) Not really and, to be honest, FDev have missed a trick here. However, EDSM does record systems for which you are the first discoverer* and, I think, the site allows you to export your flight log to a spreadsheet. If it does, and again I've never tried, you could use data sorts or a pivot table to glean the info you need.

* Caveat: not everyone uses EDSM so its first disco flag applies to EDSM data only and not necessarily to in-game discos.

Lastly, I apologise for the vague answers and I'm sure someone will come along with corrections and/or a better solution.
 
1. I often use Inara, EDDB, EDDiscovery, and other 3rd-party tools to find the nearest station or fleet carrier which supplies an item or service (often Universal Cartographics) as I explore outside the bubble. The results are given in table form. Is there a way to obtain a 3d plot instead of a table? I often do not want the very closest entry (which might take me "backwards") but rather the nearest entry along my current intended route.

2. Is there a simple way using in-game or 3rd party tools to find my first discoveries and first mappings? I've seen this question asked many times in the past few years but not recently and I'm rather surprised that it seems that as of a few years ago there was still no easy way to accomplish this.
If outside the bubble or Colonia and wanting to find somewhere for repair or Universal Cartographics on my travel route, I'd open up edsm.net galaxy map and enable the POIs for Deep Space Outpost for stations and Independent Outpost which shows where the DSSA Fleet Carriers are on station. Then its knowing about Explorers Anchorage very close to Sag A* if that is where you are headed.
 
I'm rather surprised that it seems that as of a few years ago there was still no easy way to accomplish this.
I don't think we're going to see this capability in this current incarnation of Elite - it simply hasn't been designed with this in mind. I believe it has to do with the database maintained of explored systems.

The ED galaxy is mostly procedurally-generated - it's the only way to create a full-scale replica of an entire galaxy with 400 billion stars in it (and if each star system has an average of 10 planets, that's 4 trillion planets), and not need a real-world planet-sized supercomputer to keep track of all the data for it. But there is a tiny subset of the galaxy that has actually been explored and visited by players, and it is this set that there needs to be a "database" for.

This database is large - of those 4 trillion planets, probably about a billion have now been mapped and tagged in some form - so it's got to be simple. To store First Discovery data for a planet, you need to save three numbers: the unique star system number, the planet number within that star system, and the unique commander ID number of the discoverer. The question then arises, for a giant database, which of those three fields do you use as your primary sort option?

The game needs to know the discoverers of specific star systems quickly, because it needs to look this up whenever a player enters a star system, or loads up the system map for a system they've already visited. The game doesn't actually need to quickly know a specific commander's list of first-discovered planets. Therefore, the database is sorted by star system number.

This in turn means that in order to request a specific individual commander's list of discoveries, you'd need to search through the entire database, looking at every single planet and star in the database, seeking the ID number of that specific commander. For a database with a billion or so entries, that could take a while. Oh, and it has to do this three times, because there's three databases now: Discovered, Mapped, and Footfalled.

Personally, I wouldn't mind the option of spending five minutes or more, pausing the game while it searches the entire galaxy's databases and generates such a list - especially if it then saved that list locally for perusal at leisure, until I requested an updated list. If resources are the problem, I'd even pay real-world cash to be given that option. But apparently, FD believe nobody would want to wait that long for their own personal discovery list to be generated.
 
FD probably use relational database method - AWS caters for several relational database engines.

It is inefficient to just have a massive database of stuff (makes searches very resource intensive) - by using sets of tables which have predefined relationships to each other it is easier to search within these "subsets" of data - results inherantly link to other subsets (tables).

I left working with this stuff over 30 years ago so I am not in-touch with current use but I would have thought that it would not be particularly onerous a task to interrogate such a database for commander-specific data like firsts etc.
 
Last edited:
Couldn't this database issue be solved straightforwardly by an "index" on the commander column?

https://en.wikipedia.org/wiki/Database_index
We tried to run a relational database on some stuff at work once and set up too many keys or indexes, it was nearly 40 years ago and I forget the terms, we ran out of storage space and computer capacity. Ok it was only a minicomputer not a mainframe but even now I suspect you could get into some expensive bills for server time capacity given the numbers involved even in the fraction of the galaxy that has been discovered.
 
Back
Top Bottom