From aa0563a86bbd4900ece9e7082fcc5c97c3761499 Mon Sep 17 00:00:00 2001 From: Expo on server Date: Fri, 17 May 2024 11:57:49 +0100 Subject: [PATCH] indent - online edit of handbook/troggle/scriptscurrent.html --- handbook/troggle/scriptscurrent.html | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/handbook/troggle/scriptscurrent.html b/handbook/troggle/scriptscurrent.html index 3d20754b6..5a28e8aee 100644 --- a/handbook/troggle/scriptscurrent.html +++ b/handbook/troggle/scriptscurrent.html @@ -105,7 +105,7 @@ Get the OCAML file from GitHub gpx2survex and make_svx.sh

In :loser:/gpx/

Regenerates the surface tracks as survex files from GPS .gpx files. Also requires the gpx2survex program. -

We use the OCAML program gpx2survex but we now also have a python equivalent gpx2survex.py which is used by make_svx2.sh This is part of the make_essentials generation process. +

We used to use the OCAML program gpx2survex but we now also have a python equivalent gpx2survex.py which is used by make_svx2.sh This is part of the make_essentials generation process.

gpx2survex simplifies a track so that it is less voluminous.

For the reverse process we don't need a script. For svx-to-gps we can use survexport: Olly says [2022]: "you shouldn't need to mess around with undocumented scripts - since 2018, you can just do: survexport --entrances all.3d essentials.gpx" @@ -117,6 +117,7 @@ Get the OCAML file from GitHub convert_shx.ml

Not quite obsolete, but nearly. +

Unusually, this is in the :loser: repository, in :loser:/fixedpoints/scripts/convert_shx/

We think this turns a shapefile which holds the coordinates of the 1623, 1624 boundaries into GPX. But we have mislaid the shapefile containing this vital data.

It runs ogr2ogr -f csv -lco GEOMETRY=AS_WKT outputfile inputfile and then extensively post-processes the shapefile output. @@ -125,6 +126,7 @@ It is written in OCAML. Therefore it must be Mark Shinwell's responsibility. It seems to be being run to convert CSV files into something else. The "shx" part of the name implies a shapefile index format.

We suspect this was part of the production process for originally making essentials.gpx, but we don't need it as we now have the boundary data in other formats. +

svx2qm.py, tablize-qms.pl, find-dead-qms.py,qmreader.pl

See the entire page devoted to the various