OFFTOPIC: how to get geographic coordinates (LAT/LONG) of all stations of a centerline?
Hi, I know this question is offtopic but I could not think a better place to ask: how to get geographic coordinates (LAT/LONG) of all stations of a centerline? I have been asked to produced geographic coordinates of all stations of a centerline by some friends. Does anybody knows how to do it inTherion, Survex or whatever software? Thanks in advance for any help. Rodrigo
Hi Rodrigo, I use the export model -fmt shapefile. Then, in QGIS, I can view and use the latitude and longitude. Bye, Andrea
Il giorno 15 set 2025, alle ore 11:34, Rodrigo Severo via Therion <therion@speleo.sk> ha scritto:
Hi,
I know this question is offtopic but I could not think a better place to ask: how to get geographic coordinates (LAT/LONG) of all stations of a centerline?
I have been asked to produced geographic coordinates of all stations of a centerline by some friends.
Does anybody knows how to do it inTherion, Survex or whatever software?
Thanks in advance for any help.
Rodrigo _______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
Hi Rodrigo, Given a Survex 3d file, you can use dump3d and cs2cs on the command line. E.g. if the 3d file is in UTM33: dump3d myfile.3d | grep '^NODE' | cut -d' ' -f2-5 > myfile-stations.txt cs2cs -f "%.6f" +proj=utm +zone=33 +to +proj=longlat myfile-stations.txt > myfile-longlat.txt Cheers, Thomas On Mon, Sep 15, 2025 at 11:35 AM Rodrigo Severo via Therion <therion@speleo.sk> wrote:
Hi,
I know this question is offtopic but I could not think a better place to ask: how to get geographic coordinates (LAT/LONG) of all stations of a centerline?
I have been asked to produced geographic coordinates of all stations of a centerline by some friends.
Does anybody knows how to do it inTherion, Survex or whatever software?
Thanks in advance for any help.
Rodrigo _______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
KML output. xml format, but readable B. Thomas Holder <thomas@thomas-holder.de> ezt írta (időpont: 2025. szept. 15., H 12:19):
Hi Rodrigo,
Given a Survex 3d file, you can use dump3d and cs2cs on the command line.
E.g. if the 3d file is in UTM33:
dump3d myfile.3d | grep '^NODE' | cut -d' ' -f2-5 > myfile-stations.txt cs2cs -f "%.6f" +proj=utm +zone=33 +to +proj=longlat myfile-stations.txt > myfile-longlat.txt
Cheers, Thomas
On Mon, Sep 15, 2025 at 11:35 AM Rodrigo Severo via Therion <therion@speleo.sk> wrote:
Hi,
I know this question is offtopic but I could not think a better place to
ask: how to get geographic coordinates (LAT/LONG) of all stations of a centerline?
I have been asked to produced geographic coordinates of all stations of
a centerline by some friends.
Does anybody knows how to do it inTherion, Survex or whatever software?
Thanks in advance for any help.
Rodrigo _______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
_______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
Hi, Method 1: Export centerline to kml format in therion: export model -fmt kml -disable splay-shots -o your_cave_cl.kml Then you can use a GIS package to extract coordinates, or a simple text editor. Method 2: Export to database in therion and then convert cartesian coordinates to lat/long with help of GDAL/PROJ4/QGis: export database -o your_cave.sql at the bottom of your_cave.sql file you will have list of commands insert into STATION values (1, '0', 18, 387675.73, 6056702.67, 180.04); insert into STATION_FLAG values(1, 'fix'); insert into STATION values (2, '30', 18, 387690.02, 6056686.38, 181.05); insert into STATION values (3, '11', 18, 387696.58, 6056689.10, 179.76); ... so those triples are your output coordinate system locations. Usually the coordinate system is some sort of UTM over WGS84 ellipsoid (look at your survey which one), so you put that triple into txt file, separating values by spaces and run command line tool cs2cs from GDAL/PROJ4/QGis package: Following example converts cartesian coordinates in the LKS94 coordinate system, which has EPSG (SRID) code 3346 to lat-long over WG84, which has 4326 EPSG code, with precision up to 8 decimal digits (~1.1 mm accurate). cs2cs +init=epsg:3346 +to +init=epsg:4326 -f "%.8f" coords_file_lks94
coords_file_wgs84
On Mon, Sep 15, 2025 at 12:35 PM Rodrigo Severo via Therion < therion@speleo.sk> wrote:
Hi,
I know this question is offtopic but I could not think a better place to ask: how to get geographic coordinates (LAT/LONG) of all stations of a centerline?
I have been asked to produced geographic coordinates of all stations of a centerline by some friends.
Does anybody knows how to do it inTherion, Survex or whatever software?
Thanks in advance for any help.
Rodrigo _______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
On Mon, Sep 15, 2025 at 04:01:21PM +0300, Mykyta Kozlov wrote:
Following example converts cartesian coordinates in the LKS94 coordinate system, which has EPSG (SRID) code 3346 to lat-long over WG84, which has 4326 EPSG code, with precision up to 8 decimal digits (~1.1 mm accurate).
cs2cs +init=epsg:3346 +to +init=epsg:4326 -f "%.8f" coords_file_lks94
coords_file_wgs84
Whether it's actually *accurate* to about 1mm depends on whether the coordinate reprojection can be done that accurately. You can check this with projinfo: $ projinfo --summary -s EPSG:3346 -t EPSG:4326 Candidate operations found: 1 unknown id, Inverse of Lithuania 1994 + LKS94 to WGS 84 (1), 1 m, Lithuania - onshore and offshore. The "1 m" part is telling you this transformation is only accurate to 1 *metre* (which is not a problem for many uses e.g. plotting on a map or if you want to find an entrance using GPS). If you run without `--summary` you can see why this is the case here (amongst much other output): REMARK["LKS94 is a national realization of ETRS89 and coincident to WGS 84 within 1 metre. This transformation has an accuracy equal to the coincidence figure."]]], Some transformations are more accurate: $ projinfo --summary -s EPSG:3857 -t EPSG:4326 Candidate operations found: 1 INVERSE(EPSG):3856, Inverse of Popular Visualisation Pseudo-Mercator, 0 m, World. Some less: $ projinfo --summary -s EPSG:26922 -t EPSG:4326 Candidate operations found: 1 unknown id, Inverse of UTM zone 22N + NAD83 to WGS 84 (1), 4 m, North America - onshore and offshore: Canada - Alberta; British Columbia; Manitoba; New Brunswick; Newfoundland and Labrador; Northwest Territories; Nova Scotia; Nunavut; Ontario; Prince Edward Island; Quebec; Saskatchewan; Yukon. United States (USA) - Alabama; Alaska (mainland); Arizona; Arkansas; California; Colorado; Connecticut; Delaware; Florida; Georgia; Idaho; Illinois; Indiana; Iowa; Kansas; Kentucky; Louisiana; Maine; Maryland; Massachusetts; Michigan; Minnesota; Mississippi; Missouri; Montana; Nebraska; Nevada; New Hampshire; New Jersey; New Mexico; New York; North Carolina; North Dakota; Ohio; Oklahoma; Oregon; Pennsylvania; Rhode Island; South Carolina; South Dakota; Tennessee; Texas; Utah; Vermont; Virginia; Washington; West Virginia; Wisconsin; Wyoming. And some unknown: $ projinfo --summary -s EPSG:9712 -t EPSG:4326 Candidate operations found: 1 unknown id, Inverse of UTM zone 24N + Ballpark geographic offset from NAD83 to WGS 84, unknown accuracy, World, has ballpark transformation Cheers, Olly
Hi, I would like to thank you all for the great suggestions. I managed to provided the required info with your suggestions. Regards, Rodrigo -------- Mensagem original -------- Em 15/09/2025 17:55, Olly Betts via Therion <therion@speleo.sk> escreveu:
On Mon, Sep 15, 2025 at 04:01:21PM +0300, Mykyta Kozlov wrote:
Following example converts cartesian coordinates in the LKS94 coordinate system, which has EPSG (SRID) code 3346 to lat-long over WG84, which has 4326 EPSG code, with precision up to 8 decimal digits (~1.1 mm accurate).
cs2cs +init=epsg:3346 +to +init=epsg:4326 -f "%.8f" coords_file_lks94
coords_file_wgs84
Whether it's actually *accurate* to about 1mm depends on whether the coordinate reprojection can be done that accurately.
You can check this with projinfo:
$ projinfo --summary -s EPSG:3346 -t EPSG:4326 Candidate operations found: 1 unknown id, Inverse of Lithuania 1994 + LKS94 to WGS 84 (1), 1 m, Lithuania - onshore and offshore.
The "1 m" part is telling you this transformation is only accurate to 1 *metre* (which is not a problem for many uses e.g. plotting on a map or if you want to find an entrance using GPS).
If you run without `--summary` you can see why this is the case here (amongst much other output):
REMARK["LKS94 is a national realization of ETRS89 and coincident to WGS 84 within 1 metre. This transformation has an accuracy equal to the coincidence figure."]]],
Some transformations are more accurate:
$ projinfo --summary -s EPSG:3857 -t EPSG:4326 Candidate operations found: 1 INVERSE(EPSG):3856, Inverse of Popular Visualisation Pseudo-Mercator, 0 m, World.
Some less:
$ projinfo --summary -s EPSG:26922 -t EPSG:4326 Candidate operations found: 1 unknown id, Inverse of UTM zone 22N + NAD83 to WGS 84 (1), 4 m, North America - onshore and offshore: Canada - Alberta; British Columbia; Manitoba; New Brunswick; Newfoundland and Labrador; Northwest Territories; Nova Scotia; Nunavut; Ontario; Prince Edward Island; Quebec; Saskatchewan; Yukon. United States (USA) - Alabama; Alaska (mainland); Arizona; Arkansas; California; Colorado; Connecticut; Delaware; Florida; Georgia; Idaho; Illinois; Indiana; Iowa; Kansas; Kentucky; Louisiana; Maine; Maryland; Massachusetts; Michigan; Minnesota; Mississippi; Missouri; Montana; Nebraska; Nevada; New Hampshire; New Jersey; New Mexico; New York; North Carolina; North Dakota; Ohio; Oklahoma; Oregon; Pennsylvania; Rhode Island; South Carolina; South Dakota; Tennessee; Texas; Utah; Vermont; Virginia; Washington; West Virginia; Wisconsin; Wyoming.
And some unknown:
$ projinfo --summary -s EPSG:9712 -t EPSG:4326 Candidate operations found: 1 unknown id, Inverse of UTM zone 24N + Ballpark geographic offset from NAD83 to WGS 84, unknown accuracy, World, has ballpark transformation
Cheers, Olly _______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
Thank you for the clarification, certainly I am familiar with those parts of GDAL/PROJ coordinate conversion machinery. I misused term 'accurate', needed to use the term 'precise', mostly meaning the number of digits after the decimal dot, having the value to be 'precise', but not accurate. My native language does not have separate terms for accuracy and precision, so when translating to English the care must be taken, but I did not at that time :( On Mon, Sep 15, 2025 at 11:55 PM Olly Betts <olly@survex.com> wrote:
On Mon, Sep 15, 2025 at 04:01:21PM +0300, Mykyta Kozlov wrote:
Following example converts cartesian coordinates in the LKS94 coordinate system, which has EPSG (SRID) code 3346 to lat-long over WG84, which has 4326 EPSG code, with precision up to 8 decimal digits (~1.1 mm accurate).
cs2cs +init=epsg:3346 +to +init=epsg:4326 -f "%.8f" coords_file_lks94
coords_file_wgs84
Whether it's actually *accurate* to about 1mm depends on whether the coordinate reprojection can be done that accurately.
You can check this with projinfo:
$ projinfo --summary -s EPSG:3346 -t EPSG:4326 Candidate operations found: 1 unknown id, Inverse of Lithuania 1994 + LKS94 to WGS 84 (1), 1 m, Lithuania - onshore and offshore.
The "1 m" part is telling you this transformation is only accurate to 1 *metre* (which is not a problem for many uses e.g. plotting on a map or if you want to find an entrance using GPS).
If you run without `--summary` you can see why this is the case here (amongst much other output):
REMARK["LKS94 is a national realization of ETRS89 and coincident to WGS 84 within 1 metre. This transformation has an accuracy equal to the coincidence figure."]]],
Some transformations are more accurate:
$ projinfo --summary -s EPSG:3857 -t EPSG:4326 Candidate operations found: 1 INVERSE(EPSG):3856, Inverse of Popular Visualisation Pseudo-Mercator, 0 m, World.
Some less:
$ projinfo --summary -s EPSG:26922 -t EPSG:4326 Candidate operations found: 1 unknown id, Inverse of UTM zone 22N + NAD83 to WGS 84 (1), 4 m, North America - onshore and offshore: Canada - Alberta; British Columbia; Manitoba; New Brunswick; Newfoundland and Labrador; Northwest Territories; Nova Scotia; Nunavut; Ontario; Prince Edward Island; Quebec; Saskatchewan; Yukon. United States (USA) - Alabama; Alaska (mainland); Arizona; Arkansas; California; Colorado; Connecticut; Delaware; Florida; Georgia; Idaho; Illinois; Indiana; Iowa; Kansas; Kentucky; Louisiana; Maine; Maryland; Massachusetts; Michigan; Minnesota; Mississippi; Missouri; Montana; Nebraska; Nevada; New Hampshire; New Jersey; New Mexico; New York; North Carolina; North Dakota; Ohio; Oklahoma; Oregon; Pennsylvania; Rhode Island; South Carolina; South Dakota; Tennessee; Texas; Utah; Vermont; Virginia; Washington; West Virginia; Wisconsin; Wyoming.
And some unknown:
$ projinfo --summary -s EPSG:9712 -t EPSG:4326 Candidate operations found: 1 unknown id, Inverse of UTM zone 24N + Ballpark geographic offset from NAD83 to WGS 84, unknown accuracy, World, has ballpark transformation
Cheers, Olly
participants (6)
-
Andrea Corna -
Balambér Hakapesz -
Mykyta Kozlov -
Olly Betts -
Rodrigo Severo -
Thomas Holder