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

If I don't search for a specific system, that's ok. But if I do search for a specific system, and enter the complete system name into the search field, it should take me to exactly this system and nowhere else. I already found this irritating that it jumps to other systems in series when clicking multiple times, but now it STARTS at a wrong system - it jumps to the second system in series at the beginning, omitting the system I want to see.
 
In the meantime, great alternatives to EDCE that use the Companion API are EDMC and EDAPI. You may have better luck with them if python is an issue.
EDMC installer starts on my Win 8.1 Notebook, and then nothing happens. Will try later at home, using Win 7.
Edit: Runs at home, curious to see the results...
Edit 2: Runs fine, but where do I find any interesting data, except the market data?
Edit 3: Now it runs on my Win 8.1 notebook, too. Strange. Still searching for visited systems list etc.

EDAPI needs Python 3.4, too, and some more.
 
Last edited:
Redwizzard, RedWizzard, RedWizzard! (Does that work for summoning?)

Sooooo, brand new to this game, tried my hand at contributing to system data via http://robert.astronet.se/Elite/ed-systems/entry.html. I made a mess of the Hyades Sector UY-R b4-3 coordinates (measured while not in system like a dumbass). Smacker in #eddb recommended confessing my crime here as the fastest way to get data fixed. Can you help? Is there any other information you need from me?

Thanks in advance!
 
Redwizzard, RedWizzard, RedWizzard! (Does that work for summoning?)

Sooooo, brand new to this game, tried my hand at contributing to system data via http://robert.astronet.se/Elite/ed-systems/entry.html. I made a mess of the Hyades Sector UY-R b4-3 coordinates (measured while not in system like a dumbass). Smacker in #eddb recommended confessing my crime here as the fastest way to get data fixed. Can you help? Is there any other information you need from me?

Lol, yep, I can sort it out. I should be able to figure it out from what's there, will let you know if I need any more info.
 
Hehe, nice! I've done that by myself, and more than once.
I moved the wrong distances to Candhari (should be the system where you measured the distances), and the remaining distances are sufficient to calculate the position of Hyades Sector UY-R b4-3 to (24.09375/-114.9375/-178.09375).
 
I couldn't see if this had been posted previously - sorry if this has been covered.

It appears that BACTONDINKS and CORNGARI have moved in v1.3 . Does someone have a list of any others? Here is what I have...

Code:
OLD Coords:
'BACTONDINKS',47.40625,-60.90625,54.21875,'Gamma','2014-11-27 11:33:44'
'CORNGARI',84.3125,-99.03125,93.0625,'Gamma','2014-11-27 11:33:44'

NEW Coords:
'BACTONDINKS',82.90625,-85.90625,11.3125,'Gamma','2014-11-27 11:33:44'
'CORNGARI',66.09375, -27.125, 68.40625,'Gamma','2014-11-27 11:33:44'
 
These coords were known for some weeks, n.p. Tnx 4 the hint anyway.
But something is strange with Veil West Sector KC-V c2-4 - I think I'll take a quick journey to investigate... ;)
 
I couldn't see if this had been posted previously - sorry if this has been covered.

It appears that BACTONDINKS and CORNGARI have moved in v1.3 . Does someone have a list of any others? Here is what I have...

Bactondinks was new to me. Several others have come up before, and I found a couple more today while checking the coordinates for all the FD systems we have enough distances to. The complete list of the cases I know of:
Code:
Agastani
Bactondinks
Corngari
Kamba
Lu Yupik
Macalites
Oguninksmii
Osira
Padhyas
Pareco
 
Last edited:
Y & Z coordinates were wrong by 1/16 and 1/32 Ly. I don't know why. I had several correct distances and 6 or 8 distances with a very small error, so I traveled there and checked them. All were entered correct. I removed the coordinates (set them to null) and had them calculated again. Now all distances are correct.
Veil West Sector KC-V c2-4 is located at (-1404.71875/-195.5/416.4375).

Edit: Tried the same with Col 285 Sector ZN-M b22-2, there is one distance difference between submission & calculation. Didn't work, there must be another reason ;)
 
Last edited:
Bactondinks was new to me. Several others have come up before, and I found a couple more today while checking the coordinates for all the FD systems we have enough distances to. The complete list of the cases I know of:
Code:
Agastani
Bactondinks
Corngari
Kamba
Lu Yupik
Macalites
Oguninksmii
Osira
Padhyas
Pareco

Tks! ... and just found another:

BAIJUNDH was -42.5,-37.0,140.21875 now -63.0625,-102.8125,173.46875
 
Y & Z coordinates were wrong by 1/16 and 1/32 Ly. I don't know why. I had several correct distances and 6 or 8 distances with a very small error, so I traveled there and checked them. All were entered correct. I removed the coordinates (set them to null) and had them calculated again. Now all distances are correct.
Veil West Sector KC-V c2-4 is located at (-1404.71875/-195.5/416.4375).

Those coordinates are what I have. It's possible the original set of distances resulted in a bad trilateration but with the merged distances it's ok. TGC doesn't seem to have coordinates for any of them.
 
Re: KAMBA

There are two systems called KAMBA in-game. The first one to pop up is uninhabited. The 2nd one is inhabited and the one that FD listed - coords are correct.
 
Tks! ... and just found another:

BAIJUNDH was -42.5,-37.0,140.21875 now -63.0625,-102.8125,173.46875

Thanks. I'm sure there are others - there are a lot of FD supplied systems that we don't have any distances for.

- - - Updated - - -

Re: KAMBA

There are two systems called KAMBA in-game. The first one to pop up is uninhabited. The 2nd one is inhabited and the one that FD listed - coords are correct.

Khan is also duplicated. Not sure what to do about these cases.
 
Duplicate names are a real PITA. I don't know how to handle them, too.

Oguninksmii must have been moved lately, most of the distances for the old position are from RedWizzard, dated 2015-04-08.
Pareco got wrong coordinates, too. I still wonder why does FD move systems. I can't see any obvious reason.

When my API or web FE asks for distances to verify coordinates, I omit systems provided by FD. Maybe I should include them?
 
Well, obviously all these duplicate names and apparent moves of systems (if not simply due to duplicate names) should get reported to FD support so that they can get fixed.

I recall MB stating that they no longer used the spreadsheet he sourced the co-ordinates from for us, so there'll be little to no chance of a fresh dump from FD of such data.

And MB has also stated that the API is on the faaaaaaaaaaaar back burner, so no hope there of an easy way to get star co-ordinates.

I think it might be time to once more push for FD to spend 30 minutes of a dev's time to have the current star system's co-ordinates go into the net or debug log files when you enter SC in it. That way we could more easily gather game-correct co-ordinates for systems and somewhat automate corrections as well.
 
time to once more push for FD to spend 30 minutes of a dev's time to have the current star system's co-ordinates go into the net or debug log files when you enter SC in it. That way we could more easily gather game-correct co-ordinates for systems and somewhat automate corrections as well.
Oh I'd open a bottle of [enter your preferred alcoholic drink here] if they would dump system's name & coords - and I doubt it will take 30 minutes ;-)
Anyway some part of automation will come with one of the next EDDiscovery versions. At least the system's name will get caught with correct spelling, and (besides the renaming and duplicates PITA) may get checked against the databases.
 
Back
Top Bottom