Discussion What is the most efficient way to crowdsource the 3D system coordinates

Is Elite: Dangerous being transformed to Elite: Hide n Seek? When did they move it again? I've been there about 12 hours ago, and the position was (80/47.84375/53.34375). I hope we don't have to check daily... ;)
 
Is Elite: Dangerous being transformed to Elite: Hide n Seek? When did they move it again? I've been there about 12 hours ago, and the position was (80/47.84375/53.34375). I hope we don't have to check daily... ;)

That's the current position, and the position FD provided in the spreadsheet. Sometime after release it moved to (66, 29.84375, 53.34375). That happened sometime between Jan 3 and Feb 15. Now it has returned to it's original position.
 
So I just submitted coords to Synuefe ZS-V b21-1 using http://robert.astronet.se/Elite/ed-systems/entry.html, and this was the log output:

Submitting Synuefe ZS-V b21-1 with 5 distances to the-temple.de:
Submitting Synuefe ZS-V b21-1 with 5 distances to TGC:
TGC: successful
TGC: Trilateration for Synuefe ZS-V b21-1: 401 Trilateration succesful.
the-temple.de: submission successful
the-temple.de: Trilateration for Synuefe ZS-V b21-1: 106 no match found for base system

Should I be worried about the fact that temple's complaining about no match found for base system?
 
Should I be worried about the fact that temple's complaining about no match found for base system?
No real worries. My coordinate calculation got some weak points. It will get tuned if I find some free time. Sometimes even with a lot of referencing distances it "shoots around the bull's eye" without hitting it, because of the 1/32 Ly grid. If TGC's trilateration is ok, my DB fetches the coordinates from there, after some time. Usually you're on a longer journey, and then it's sufficient to submit the distance to this system from your next stop. the-temple will calculate both coordinates then: your current position and the previous one.
TGC's trilateration got some different weak points. Sometimes TGC is fine, and the-temple complains, sometimes vice versa.
BTW: I still have no nice name for my project. The best candidate for now is "Star Map 42". Something like the answer to all your (coordinate & distance related) questions. Anyone here yelling out a good idea?
 
I still have no nice name for my project. The best candidate for now is "Star Map 42". Something like the answer to all your (coordinate & distance related) questions. Anyone here yelling out a good idea?

How about "Stellar Cartography"? That might have been used before, though. ��
 

wolverine2710

Tutorial & Guide Writer
How about "Stellar Cartography"? That might have been used before, though. ��

I've checked ED3PTT (see OP of my third party tools thread). I don't see a tool or thread with the name stellar cartography, not even one with only the name stellar in it. It most likely is NOT a complete overview of all tools/threads out there but it has a very decent amount of tools/threads. Current stats: 84 tools, 61 threads.

Stellar Cartography seems not to be used.
Even EDSC: ED Stellar Cartography could be a possibility.

That said Starmap 42 has a nice ring. Especially because of the number 42.

An alternative, like I've done with ED3PTT (codename). Create a thread, describe the functionality of the tool and ask for feedback for a good name. Some good names came out of it for me wrt ED3PTT.
 
Last edited:
Even EDSC: ED Stellar Cartography could be a possibility.

That said Starmap 42 has a nice ring. Especially because of the number 42.

Having "ED" in there is a good idea for search I think. So ED Cartographer, ED Stellar Cartographer, ED Starmap 42, ED Star Mapper all sound good to me. Or Dangerous Starmap 42?
 
Thanks guys, nice conversation here! That's what I needed.

ED Stellar Cartography is IMHO not a good choice because the abbrevation would be EDSC. And my database shall replace EDSC/TGC.

ED Stellar Map 42 sounds good in my ears. And yes, you know where the 42 comes from ;) If someone references my API, like RW's pages do, you may use EDSM or EDSM42 as a name. I'll rename the pages accordingly soon, depending on my time.

Edit: EDSM is good for ED Stellar Map and ED Star Map. Think I prefer Star instead of Stellar. I'll sleep about this.
 
Last edited:
I have made a trilateration routin in C# based on Redwizzards routine. It seems to work fine and fast.

The plan is to use it in EDDiscovery soon to have a build in trilateration function. Cmdr MAjkl has helped me with the UI and treletarion for this future function,


We can create a testversion soon if someone wants to test it.
 
I have made a trilateration routin in C# based on Redwizzards routine. It seems to work fine and fast.

The plan is to use it in EDDiscovery soon to have a build in trilateration function. Cmdr MAjkl has helped me with the UI and treletarion for this future function,


We can create a testversion soon if someone wants to test it.
Perhaps all of those who have already written such trilateration code and tested it well could pipe up with a set of test cases that ensure it catches all the edge and corner cases ?
 
Probably Finwen will do some tests using the known systems, either from EDSC API, Redwizzard's tgcxxx.json or my API, and pretend the coordinates are unknown, and check if his function finds the same coordinates that are saved already. That's what I did.
And I'm sure he will travel to some unknown systems and enter distances, then compare the three existing solutions to his code's results.
Edit: And yes, I am very interested in a testing version! Finwen knows already... ;)
 
Last edited:
referencelines.png

I and Cmdr Smacker and Cmdr Majkl have worked more on the build in trilaterationin EDDiscovery. Last days we have worked more on a system to suggest good reference stars.
Smacker modified the Star map so we can see the suggested stars in a fun way.

In short,
We take the last known position.
Divide the sky in 72 different sectors (by angels).
Loop through all stars with known position and add them to a sector as candidates

If we have any used reference stars we mark the sectors they are in.

To get a new reference star suggestion. Get one star from the sector at the most angular distance from the sector with used references.
Repeat last step until we have as any suggested stars as we need.

This way we get reference stars that have a good spread in different directions in a fast easy way.

Early test looks very good and we gets a trilateration in about 5 or 6 stars even far out from populated space.
 
I and Cmdr Smacker and Cmdr Majkl have worked more on the build in trilaterationin EDDiscovery. Last days we have worked more on a system to suggest good reference stars.
Smacker modified the Star map so we can see the suggested stars in a fun way.

In short,
We take the last known position.
Divide the sky in 72 different sectors (by angels).
Loop through all stars with known position and add them to a sector as candidates

If we have any used reference stars we mark the sectors they are in.

To get a new reference star suggestion. Get one star from the sector at the most angular distance from the sector with used references.
Repeat last step until we have as any suggested stars as we need.

This way we get reference stars that have a good spread in different directions in a fast easy way.

Early test looks very good and we gets a trilateration in about 5 or 6 stars even far out from populated space.

Good stuff. Would be interesting to compare with the algorithms I use. It just iterates through all known systems testing if the distance from that system to each of the best candidates is different for each candidate (meaning a distance to that reference would differentiate the current set of candidates). If it is then it's a good reference. It seems to work quite well.
 
As jump ranges just came up in conversation and I recalled someone working out that ~13ly range was enough to get anywhere in the sphere/pill we had back in beta... has anyone looked into this sort of thing for the full galaxy (ignore the fringes and too far up/down, I'm talking about inhabited space and the main disc here) ?

I recall someone was specifically filling in whole sectors with positional data. Anyone had chance to run the data through something to find the minimal jump range needed to get around in inhabited space ?
 
Its a new religion :) Now even with our own angels :) 72 is now the holy number or coord hunting :)

About the fringes, its a huge place and might be hard to decide. Maybe "most isolated populated system" as suggested would be the most usefull parameter.
 
Last edited:
As jump ranges just came up in conversation and I recalled someone working out that ~13ly range was enough to get anywhere in the sphere/pill we had back in beta... has anyone looked into this sort of thing for the full galaxy (ignore the fringes and too far up/down, I'm talking about inhabited space and the main disc here) ?

I recall someone was specifically filling in whole sectors with positional data. Anyone had chance to run the data through something to find the minimal jump range needed to get around in inhabited space ?
Note that if anyone has been filling in whole cubes/spheres at some point and can tell me where I'll have a look at the data myself to answer my question. I just don't want to look at the currently available data and try to guess if a volume is fully covered.
 
I did for a while around LHS 1914, but going for the entire populated space in ED would take a very long tim

Is SOL the center of the populated space, or is that "origo" in a different point (taking the extremes of human settlement, and find the center)? Should make a little brainsnack for someones afternoon :)
 
I did for a while around LHS 1914, but going for the entire populated space in ED would take a very long tim

Is SOL the center of the populated space, or is that "origo" in a different point (taking the extremes of human settlement, and find the center)? Should make a little brainsnack for someones afternoon :)
Eh, that should be easy enough if you just mean "how far do populated systems extend", as the last data dump we got from FD back in Gamma was /precisely/ all the systems with an economy, and thus populated. Just find the +/- limits on each co-ord in that and centre them. Slightly more complicated if you want it weighted to density of systems of course.

Code:
ed_stars=> SELECT MIN(x),MAX(x),MIN(y),MAX(y),MIN(z),MAX(z) FROM ed_stars WHERE commandercreate = 'FD';     min     |   max   |    min    |    max    |    min     |    max    
-------------+---------+-----------+-----------+------------+-----------
 -1098.90625 | 577.875 | -452.6875 | 909.96875 | -957.21875 | 214.53125

ed_stars=> SELECT name,x,y,z FROM ed_stars WHERE x=-1098.90625;
   name    |      x      |    y     |    z    
-----------+-------------+----------+---------
 HD 239729 | -1098.90625 | 72.53125 | -186.75
(1 row)


ed_stars=> SELECT name,x,y,z FROM ed_stars WHERE x=577.875;
    name    |    x    |     y     |    z    
------------+---------+-----------+---------
 BD-12 1172 | 577.875 | -452.6875 | -819.25
(1 row)


ed_stars=> SELECT name,x,y,z FROM ed_stars WHERE y = -452.6875;
    name    |    x    |     y     |    z    
------------+---------+-----------+---------
 BD-12 1172 | 577.875 | -452.6875 | -819.25
(1 row)


ed_stars=> SELECT name,x,y,z FROM ed_stars WHERE y = 909.96875;
     name     |    x     |     y     |     z      
--------------+----------+-----------+------------
 Gliese 398.2 | -61.1875 | 909.96875 | -531.40625
(1 row)


ed_stars=> SELECT name,x,y,z FROM ed_stars WHERE z = -957.21875;
   name    |     x     |    y     |     z      
-----------+-----------+----------+------------
 HIP 26889 | -103.9375 | 64.53125 | -957.21875
(1 row)


ed_stars=> SELECT name,x,y,z FROM ed_stars WHERE z = 214.53125;
   name    |    x    |     y     |     z     
-----------+---------+-----------+-----------
 HIP 90963 | 8.90625 | -50.96875 | 214.53125
(1 row)

And
Code:
-1098 + (1098/2 + 578/2)
-260.00000
-452 + (452/2 + 910/2)
229.00000
-957 + (957/2 + 215/2)
-371.00000
So, I make it to be around -260, 229, -371, but my DB has nothing in it anywhere near that. I've a feeling we have a REAL outlier above that's skewing the results. This is going to take doing some weighted (distance from origin) thing I think.
 
Last edited:
Oh, but maybe my DB has some error, because if I use my "where real stars should be in ED" tool then I'm told:
Code:
#	Distance	HIP	HD	HR	Gliese	Bayer Flamsteed	Proper Name	Spectrum	ED x	ED y	ED z1	17.31	36051	57201					F8	-252.51	243.68	-376.28
Someone checked for me and in-game that's at approx. -200 : 198 : -300.
 
Doing a naive "start at the origin, iterate over the stars moving half way towards each time" thing, with various orders of the data (ORDER BY in the SQL on various fields), yields an answer around 90 to 95 : -70 to -65 : 10 to 15. That's someplace around "Crucis Sector PC-V a2-0".
 
Back
Top Bottom