Discussion What is the most efficient way to crowdsource the 3D system coordinates
- Thread starter wolverine2710
- Start date
Where do you get the coordinates from? What's your source?
Col 285 Sector IA-Z b29-0 is located at (17.75/85.40625/294.8125)
COL 285 SECTOR SW-W B17-0 is not in my database at all.
Whamboi IH-U e3-507 is located at (-1628.75/1148.15625/18799.15625)
Whamboi XP-V d3-503 has some wrong distances in TGC, coordinates unknown.
Col 285 Sector IA-Z b29-0 is located at (17.75/85.40625/294.8125)
COL 285 SECTOR SW-W B17-0 is not in my database at all.
Whamboi IH-U e3-507 is located at (-1628.75/1148.15625/18799.15625)
Whamboi XP-V d3-503 has some wrong distances in TGC, coordinates unknown.
They came form various sources (EDDB/Redwizard)
Col 285 Sector IA-Z b29-0 => From Redwizard (TGC OK)
COL 285 SECTOR SW-W B17-0 => Came from EDDB (TGC/Redwizard Unknown) => From history, it cames from Starchart => Checked in galaxy game map
Whamboi IH-U e3-507 => From Redwizard (TGC OK)
Whamboi XP-V d3-503 => From EDDB and found in Redwizard (Does not have the TGC unlocated flag)
=>
"id": 39514,
"name": "Whamboi XP-V d3-503",
"coord": [
-1628.75,
1148.15625,
18799.15625
],
"cr": 2,
"commandercreate": "Finwen",
"createdate": "2015-05-10 22:50:02",
"commanderupdate": "Finwen",
"updatedate": "2015-05-10 22:50:02"
The problem with that pair is that a bunch of distances were entered for Whamboi XP-V d3-503 when they were actually for Whamboi IH-U e3-507. Whamboi XP-V d3-503 is a real system so I haven't deleted it, but it now doesn't have enough distances to trilaterate. If my correction process can't locate a system that has a location in TGC it uses that so the result is the duplication:
Whamboi IH-U e3-507 - located by my process and in the correct location
Whamboi XP-V d3-503 - not located by my process so gets the location from TGC which is the location of the other system.
The reason I use TGC locations when I can't trilaterate myself is that TGC doesn't report all distances so it may have more info than I have for a particular system (i.e. many of the locations it has that I don't are correct). TGC doesn't report new distances for certain reference systems that have somehow got duplicated (IIRC there are about 6, including Sol).
OK I see, thanks for the head-up !
I'll add it to the ignore list until the coords changes then.
One good gui API should provide the entered distances when you enter a system, thus we can delete those who seems illegitimate !
Exactly. That's why im coding http://the-temple.de
You wanna see a list of all wrong systems & distances?
http://the-temple.de/public/hidden.php
In JSON format:
http://the-temple.de/public/hiddensys.php
http://the-temple.de/public/hiddendists.php
You have a SQL query dump on the confirmation page
I'll give it a try, the absence of design tend to block me a little but I can wait, or help if you need
I really like it ! Even without design, but it tends to be hard to read the systems name !
That's exactly what I have in mind, Do you have a documentation page where all your API is resumed ?
The web FE register/confirmation part is not very smooth right now and will be cleaned up next week. At least it's working, and it is only ment for manual distance cleanup, spelling corrction etc. And the SQL statement is only for debugging... ;-)
The hidden[sys|dist].php aren't documented right now, I guess. I should do that, too. But I thought they're way too simple to need documentation.
The main API part is (as far as it's ready) documented here: http://the-temple.de/public/api.php
Return values of submitdistance.php are WIP right now. And if you have any ideas/suggestions, pls let me know.
The hidden[sys|dist].php aren't documented right now, I guess. I should do that, too. But I thought they're way too simple to need documentation.
The main API part is (as far as it's ready) documented here: http://the-temple.de/public/api.php
Return values of submitdistance.php are WIP right now. And if you have any ideas/suggestions, pls let me know.
Last edited:
Yeah, I've done the same more than once.
- - - Updated - - -
I'll set the coords to null in my fixes, that'll prevent the incorrect value from TGC being used.
My stuff has sysinfo.html which shows existing entered distances.
Improved approach to crowdsourcing 3d coordinates?
Hi All
I have an idea about how we could potentially hugely expand the triangulation of uncharted systems. I am presuming EDSC is still the de-facto place to log new systems? If not please reply and tell me the better option(s)!
So, on to my idea....
The current approach is that every star you visit, if you suspect it might not be charted yet, you visit EDSC and type in its name to find out. If it isn't charted you spend a few minutes in the Galaxy map finding distances to a few reference systems, and enter them into EDSC (or another tool).
The problem with this is that it takes quite a time out of gameplay, so is not not done as much as we would like. It's also a pain having to check if the system is unknown.
So, if we had a list of unknown systems (I'll come on to that...) and posted it on a site somewhere, then public spirited CMDRs could visit the site and punch in the distance from wherever they happen to be to a few unknown systems. Once enough CMDRs report distances to an individual unknown system, it can be submitted to EDSC for triangulation using EDSC's API.
So how do we get the list of unknown systems?
In the various apps that use the IOS API (I use EDCE), the retrieved JSON contains a JSON array of every system you have ever visited, it is here in the JSON 'stats'->'explore'->'visited'->>'starsystem'
I have been inserting my saved JSON CMDR data from EDCE into a Postgres database I have built from EDDBs nightly dumps, this means that with a relatively simple query, I can list all the systems I have visited that are not currently in EDDB (Postgres has excellent JSON support)...
My results are below - if a few of the more adventurous explorers out there tried this we would have a huge list of unknown systems I think?
The site would need a page to submit a list of unknown systems - could be automated like EDCE submission of prices, and a page in which CMDRs could submit distances.
Maybe one of the excellent systems already out there could add this functionality to save writing from scratch?
Apologies if this is already out there, but there are 152 pages on this thread to trawl to find out!
Your thoughts....
CMDR Zoy
Hi All
I have an idea about how we could potentially hugely expand the triangulation of uncharted systems. I am presuming EDSC is still the de-facto place to log new systems? If not please reply and tell me the better option(s)!
So, on to my idea....
The current approach is that every star you visit, if you suspect it might not be charted yet, you visit EDSC and type in its name to find out. If it isn't charted you spend a few minutes in the Galaxy map finding distances to a few reference systems, and enter them into EDSC (or another tool).
The problem with this is that it takes quite a time out of gameplay, so is not not done as much as we would like. It's also a pain having to check if the system is unknown.
So, if we had a list of unknown systems (I'll come on to that...) and posted it on a site somewhere, then public spirited CMDRs could visit the site and punch in the distance from wherever they happen to be to a few unknown systems. Once enough CMDRs report distances to an individual unknown system, it can be submitted to EDSC for triangulation using EDSC's API.
So how do we get the list of unknown systems?
In the various apps that use the IOS API (I use EDCE), the retrieved JSON contains a JSON array of every system you have ever visited, it is here in the JSON 'stats'->'explore'->'visited'->>'starsystem'
I have been inserting my saved JSON CMDR data from EDCE into a Postgres database I have built from EDDBs nightly dumps, this means that with a relatively simple query, I can list all the systems I have visited that are not currently in EDDB (Postgres has excellent JSON support)...
Code:
with systems as (
select to_timestamp(tstamp),
data->'stats'->'explore'->'visited'->>'starsystem' as visited
from "ED_STG"."STG_CMDR_SAVE" s
order by tstamp desc limit 1),
visited as (
select x.* from systems s, json_array_elements_text(s.visited::json) x)
select value as system
from visited
where value not in(select name from "ED_MAIN"."DTA_SYSTEM");My results are below - if a few of the more adventurous explorers out there tried this we would have a huge list of unknown systems I think?
Alrai Sector LH-V b2-3
GL Virginis
DG Canum Venaticorum
Alrai Sector VI-T a3-1
Alrai Sector WI-T a3-0
Core Sys Sector GH-M a7-3
Crucis Sector DL-Y d163
Antliae Sector IM-W d1-96
HIP 57931
Antliae Sector IM-W d1-103
Col 285 Sector ER-R b19-4
Col 285 Sector NS-J c9-30
Crucis Sector FQ-Y b2
HR 3404
Col 285 Sector JM-A b15-2
BD+62 722
BD+54 886
Hyades Sector RU-N b7-3
Hyades Sector QZ-N b7-3
LTT 12193
SPOCS 398
Hyades Sector RU-M b8-0
HIP 44926
Col 285 Sector SO-P c6-13
Sharru Sector ZE-A d98
Col 285 Sector TK-B b15-1
HIP 55192
HIP 56381
HIP 57091
Col 285 Sector MZ-B b15-1
Col 285 Sector LZ-B b15-0
Col 285 Sector EY-W b16-4
Col 285 Sector GJ-V b17-7
Col 285 Sector ID-I c10-3
Col 285 Sector RG-Q b20-7
Col 285 Sector ID-I c10-17
Herculis Sector RO-R b4-4
Alrai Sector IC-U b3-1
Alrai Sector UE-Q b5-6
Alrai Sector TE-Q b5-6
Col 285 Sector KP-K b23-3
Col 285 Sector HE-M b22-9
Col 285 Sector YO-G a40-2
Col 285 Sector XB-R b19-8
Pegasi Sector YU-O b6-4
Pegasi Sector KH-V c2-23
Pegasi Sector KH-V c2-17
Pegasi Sector JR-V b2-2
Pegasi Sector FL-X b1-6
Arietis Sector WK-O b6-2
Arietis Sector TE-Q b5-2
Arietis Sector KC-V c2-7
HIP 8067
Piscium Sector DQ-Y b4
Tascheter Sector IH-V a2-2
LP 356-14
Tascheter Sector RE-Q a5-2
Hyades Sector XZ-P c5-20
ICZ XO-A c16
ICZ ZJ-Z b3
ICZ CQ-Y d119
ICZ IW-V b2-3
Col 285 Sector OS-Q b19-6
Col 285 Sector XJ-H c10-19
HIP 11972
Shui Wei Sector XO-R b4-2
Shui Wei Sector KR-W c1-22
Col 285 Sector MR-T b17-0
Col 285 Sector MB-V b16-3
Synuefe HJ-W b48-0
HIP 11514
HIP 5564
ICZ OX-U b2-2
ICZ PI-T b3-1
ICZ OI-T b3-1
ICZ FB-X b1-0
ICZ DL-Y d115
ICZ DL-Y d113
Col 285 Sector KI-P b20-9
Zibel
Puppis Sector ZE-A d118
Hyades Sector CM-K b9-4
HIP 42248
Hyades Sector CG-X d1-69
Hyades Sector LN-S c4-7
Sharru Sector FB-X b1-3
LHS 2320
Tascheter Sector LN-T a3-1
WISE J0254+0223
Tascheter Sector ZK-O a6-0
Crucis Sector IX-T b3-5
Tascheter Sector GR-M a7-2
Puppis Sector MX-U b2-5
Agelasta
Crucis Sector NY-R b4-3
Crucis Sector NY-R b4-0
Scorpii Sector CV-Y a1
Col 285 Sector EC-R b19-6
Col 285 Sector DC-R b19-8
Capricorni Sector EG-X b1-3
Capricorni Sector AV-Y b4
Pegasi Sector YU-O b6-3
Pegasi Sector NX-T b3-6
Pegasi Sector JR-V b2-3
Arietis Sector KC-V c2-20
Arietis Sector KC-V c2-25
Piscium Sector BQ-Y b0
Piscium Sector AV-Y b6
Marte
Tascheter Sector LS-T a3-3
Hyades Sector PL-H a25-1
Puppis Sector DW-N a6-1
LHS 1070
Crucis Sector DW-N a6-2
Col 285 Sector QP-G a40-4
Crucis Sector HH-M a7-2
LP 475-70
Piscium Sector XZ-X a1-3
Dymiay
Tascheter Sector WE-Q a5-2
Tascheter Sector GR-M a7-0
Puppis Sector ZP-P a5-1
Puppis Sector FW-N a6-1
Puppis Sector KC-M a7-1
Crucis Sector PC-V a2-3
CD-59 1706
Col 285 Sector DW-N a36-1
Col 285 Sector WE-Q d5-107
Antliae Sector IM-W d1-127
Antliae Sector XU-P b5-4
Hydrae Sector KM-W c1-17
Crucis Sector ND-S b4-3
LFT 325
Shui Wei Sector DS-Q a6-0
Crucis Sector UD-T a3-4
Crucis Sector DV-P a5-5
Col 285 Sector CG-T b18-7
Col 285 Sector ER-R b19-1
Col 285 Sector ER-R b19-8
Crucis Sector DL-Y d165
Crucis Sector MS-T b3-7
Crucis Sector JX-T b3-4
Crucis Sector AP-R a4-3
Tascheter Sector UE-Q a5-2
LP 658-2
EV Lacertae
Piscium Sector VK-N a7-1
Piscium Sector WF-N a7-4
Pegasi Sector VO-Q b5-1
HIP 113438
Pegasi Sector QI-T c3-18
HIP 113782
Pegasi Sector YE-Q b5-0
Arietis Sector XK-O b6-1
HIP 6975
Arietis Sector WZ-P b5-2
StKM 1-276
Tascheter Sector LX-U b2-1
VVO 35
Tascheter Sector RY-R a4-0
Trianguli Sector FM-V b2-6
Trianguli Sector KS-T b3-4
Puppis Sector ZJ-A b0
Hyades Sector UZ-N b7-3
Hyades Sector LD-Q b6-3
Col 285 Sector OT-E b13-3
Sharru Sector CG-X b1-0
LHS 2657
LTT 1877
Shui Wei Sector WO-A c23
ICZ YJ-Z b5
Shui Wei Sector PO-Q b5-7
Col 285 Sector JI-P b20-2
Col 285 Sector KD-P b20-2
Col 285 Sector WZ-P d5-86
CD-29 18093
Capricorni Sector CQ-Y c19
Capricorni Sector WO-A b1
Pegasi Sector KX-K b8-5
Pegasi Sector KX-K b8-0
Pegasi Sector JX-K b8-6
Pegasi Sector GM-M b7-1
Gliese 1269
GL Virginis
DG Canum Venaticorum
Alrai Sector VI-T a3-1
Alrai Sector WI-T a3-0
Core Sys Sector GH-M a7-3
Crucis Sector DL-Y d163
Antliae Sector IM-W d1-96
HIP 57931
Antliae Sector IM-W d1-103
Col 285 Sector ER-R b19-4
Col 285 Sector NS-J c9-30
Crucis Sector FQ-Y b2
HR 3404
Col 285 Sector JM-A b15-2
BD+62 722
BD+54 886
Hyades Sector RU-N b7-3
Hyades Sector QZ-N b7-3
LTT 12193
SPOCS 398
Hyades Sector RU-M b8-0
HIP 44926
Col 285 Sector SO-P c6-13
Sharru Sector ZE-A d98
Col 285 Sector TK-B b15-1
HIP 55192
HIP 56381
HIP 57091
Col 285 Sector MZ-B b15-1
Col 285 Sector LZ-B b15-0
Col 285 Sector EY-W b16-4
Col 285 Sector GJ-V b17-7
Col 285 Sector ID-I c10-3
Col 285 Sector RG-Q b20-7
Col 285 Sector ID-I c10-17
Herculis Sector RO-R b4-4
Alrai Sector IC-U b3-1
Alrai Sector UE-Q b5-6
Alrai Sector TE-Q b5-6
Col 285 Sector KP-K b23-3
Col 285 Sector HE-M b22-9
Col 285 Sector YO-G a40-2
Col 285 Sector XB-R b19-8
Pegasi Sector YU-O b6-4
Pegasi Sector KH-V c2-23
Pegasi Sector KH-V c2-17
Pegasi Sector JR-V b2-2
Pegasi Sector FL-X b1-6
Arietis Sector WK-O b6-2
Arietis Sector TE-Q b5-2
Arietis Sector KC-V c2-7
HIP 8067
Piscium Sector DQ-Y b4
Tascheter Sector IH-V a2-2
LP 356-14
Tascheter Sector RE-Q a5-2
Hyades Sector XZ-P c5-20
ICZ XO-A c16
ICZ ZJ-Z b3
ICZ CQ-Y d119
ICZ IW-V b2-3
Col 285 Sector OS-Q b19-6
Col 285 Sector XJ-H c10-19
HIP 11972
Shui Wei Sector XO-R b4-2
Shui Wei Sector KR-W c1-22
Col 285 Sector MR-T b17-0
Col 285 Sector MB-V b16-3
Synuefe HJ-W b48-0
HIP 11514
HIP 5564
ICZ OX-U b2-2
ICZ PI-T b3-1
ICZ OI-T b3-1
ICZ FB-X b1-0
ICZ DL-Y d115
ICZ DL-Y d113
Col 285 Sector KI-P b20-9
Zibel
Puppis Sector ZE-A d118
Hyades Sector CM-K b9-4
HIP 42248
Hyades Sector CG-X d1-69
Hyades Sector LN-S c4-7
Sharru Sector FB-X b1-3
LHS 2320
Tascheter Sector LN-T a3-1
WISE J0254+0223
Tascheter Sector ZK-O a6-0
Crucis Sector IX-T b3-5
Tascheter Sector GR-M a7-2
Puppis Sector MX-U b2-5
Agelasta
Crucis Sector NY-R b4-3
Crucis Sector NY-R b4-0
Scorpii Sector CV-Y a1
Col 285 Sector EC-R b19-6
Col 285 Sector DC-R b19-8
Capricorni Sector EG-X b1-3
Capricorni Sector AV-Y b4
Pegasi Sector YU-O b6-3
Pegasi Sector NX-T b3-6
Pegasi Sector JR-V b2-3
Arietis Sector KC-V c2-20
Arietis Sector KC-V c2-25
Piscium Sector BQ-Y b0
Piscium Sector AV-Y b6
Marte
Tascheter Sector LS-T a3-3
Hyades Sector PL-H a25-1
Puppis Sector DW-N a6-1
LHS 1070
Crucis Sector DW-N a6-2
Col 285 Sector QP-G a40-4
Crucis Sector HH-M a7-2
LP 475-70
Piscium Sector XZ-X a1-3
Dymiay
Tascheter Sector WE-Q a5-2
Tascheter Sector GR-M a7-0
Puppis Sector ZP-P a5-1
Puppis Sector FW-N a6-1
Puppis Sector KC-M a7-1
Crucis Sector PC-V a2-3
CD-59 1706
Col 285 Sector DW-N a36-1
Col 285 Sector WE-Q d5-107
Antliae Sector IM-W d1-127
Antliae Sector XU-P b5-4
Hydrae Sector KM-W c1-17
Crucis Sector ND-S b4-3
LFT 325
Shui Wei Sector DS-Q a6-0
Crucis Sector UD-T a3-4
Crucis Sector DV-P a5-5
Col 285 Sector CG-T b18-7
Col 285 Sector ER-R b19-1
Col 285 Sector ER-R b19-8
Crucis Sector DL-Y d165
Crucis Sector MS-T b3-7
Crucis Sector JX-T b3-4
Crucis Sector AP-R a4-3
Tascheter Sector UE-Q a5-2
LP 658-2
EV Lacertae
Piscium Sector VK-N a7-1
Piscium Sector WF-N a7-4
Pegasi Sector VO-Q b5-1
HIP 113438
Pegasi Sector QI-T c3-18
HIP 113782
Pegasi Sector YE-Q b5-0
Arietis Sector XK-O b6-1
HIP 6975
Arietis Sector WZ-P b5-2
StKM 1-276
Tascheter Sector LX-U b2-1
VVO 35
Tascheter Sector RY-R a4-0
Trianguli Sector FM-V b2-6
Trianguli Sector KS-T b3-4
Puppis Sector ZJ-A b0
Hyades Sector UZ-N b7-3
Hyades Sector LD-Q b6-3
Col 285 Sector OT-E b13-3
Sharru Sector CG-X b1-0
LHS 2657
LTT 1877
Shui Wei Sector WO-A c23
ICZ YJ-Z b5
Shui Wei Sector PO-Q b5-7
Col 285 Sector JI-P b20-2
Col 285 Sector KD-P b20-2
Col 285 Sector WZ-P d5-86
CD-29 18093
Capricorni Sector CQ-Y c19
Capricorni Sector WO-A b1
Pegasi Sector KX-K b8-5
Pegasi Sector KX-K b8-0
Pegasi Sector JX-K b8-6
Pegasi Sector GM-M b7-1
Gliese 1269
The site would need a page to submit a list of unknown systems - could be automated like EDCE submission of prices, and a page in which CMDRs could submit distances.
Maybe one of the excellent systems already out there could add this functionality to save writing from scratch?
Apologies if this is already out there, but there are 152 pages on this thread to trawl to find out!
Your thoughts....
CMDR Zoy
Hi,
Feeling a bit of a n00b askign this as you guys discuss JSON whatsits etc, but...
Have you got any tips on reference systems to achieve trilateration against quickly.
Currently I'm having to add at least 15 distances in to get the new system added and often many more, using (entirely arbitrarily):-
Leesti, Huldr, Witchhaul, Sol, Shinrarta Deszra
12 Andromedae, 23 Areiti, 234 G. Carinae, 45 C Bootis, 56 Cygni
Abaana, Shibboleth, CC eri, Addo, Aequeelg
I guess I need a better spread of reference systems, but how to find it???
thanks Fellamee
Feeling a bit of a n00b askign this as you guys discuss JSON whatsits etc, but...
Have you got any tips on reference systems to achieve trilateration against quickly.
Currently I'm having to add at least 15 distances in to get the new system added and often many more, using (entirely arbitrarily):-
Leesti, Huldr, Witchhaul, Sol, Shinrarta Deszra
12 Andromedae, 23 Areiti, 234 G. Carinae, 45 C Bootis, 56 Cygni
Abaana, Shibboleth, CC eri, Addo, Aequeelg
I guess I need a better spread of reference systems, but how to find it???
thanks Fellamee
Try this site , it has a nice preset and suggests good ref systems as you put more in http://robert.astronet.se/Elite/ed-systems/entry.html
Anything you add will be sent to EDSC
Thanks will do
brilliant!
This is something CMDR Inhumierer might be interested in. Check-out his site here: http://the-temple.de/
It already does a lot of what you mention.
Thanks, I took a look and you are right, I will follow up!
Short answer (long one is prepared on notebook, but couldn't finish because they found a WW2 bomb): Finding coordinates using EDSC works but is a PITA, because it doesnt trilaterate backwards (always). So if you're at system A, and systems x, y & z have unknown coordinates, and you want to transmit distances, you can't submit A-X A-Y & A-Z at once. You need to switch to expert mode and transmit X-A, then Y-A and then Z-A.
And the mirror of RedWizzard's Java page at astronet.se is a bit old, it smells Use my mirror, polled at every full hour from GIT: http://the-temple.de/rw/ed-systems/entry.html The actual version of his page already submits distances to EDSC and my page.
- - - Updated - - -
And the mirror of RedWizzard's Java page at astronet.se is a bit old, it smells
Use my mirror, polled at every full hour from GIT: http://the-temple.de/rw/ed-systems/entry.html The actual version of his page already submits distances to EDSC and my page.- - - Updated - - -
If you set (or give me) your CMDR name I can merge the distances you submitted to EDSC, so you may delete or hide your typos.