diff --git a/handbook/troggle/gpx_publish_process-small.jpg b/handbook/troggle/gpx_publish_process-small.jpg new file mode 100644 index 000000000..bce400bd3 Binary files /dev/null and b/handbook/troggle/gpx_publish_process-small.jpg differ diff --git a/handbook/troggle/make-essentialsREADME.txt b/handbook/troggle/make-essentialsREADME.txt index 4f7a93272..dd3004d80 100644 --- a/handbook/troggle/make-essentialsREADME.txt +++ b/handbook/troggle/make-essentialsREADME.txt @@ -1,3 +1,33 @@ +New in 2025: +============ +We now have the boundaries for all the kataster areas in a shapefile (again), we have re-generated GPX files for both 1623 and 1626 as GPX files. Copies are in +expoweb/documents/boundaries/ +1623.gpx +1626.gpx + +The original shapefile data is in the files +expofiles/qgis_resources/boundaries +4_Teilgruppen_M31_2021_01 .shp. ..shx, .dbf etc etc + +Download ogr2ogr and run this to convert the whole lot to a single 26 MB GPX files. + +$ ogr2ogr -f GPX -nlt MULTILINESTRING -t_srs EPSG:4326 -s_srs EPSG:32633 boundaries.gpx 4_Teilgruppen_UTM_33_N_2021_01.shp -dsco GPX_USE_EXTENSIONS=YES + +The problem is that the shapefile uses polygons, and is in UTM33N, whereas GPX files are just polylines and are in WGS84: hence all the command line parameters. + +The 1623.gpx file was extracted simply by editing it out of the 26 MB gpx file.. It was then run through GPSprune to add the SRTM altitude data. + +Now we can re-engineer the process for making essentials2025.gpx from scratch, without having to bounce back and forth between survex and other formats. + + + +Status in 2024 +============== +In 2024 we manually created essentials2024.gpx +and then updated it to include the deviation around the seilbahn works +at the end of the car park to make essentials2024divert.gpx + + The folders for each year are for general gpx files from recorded tracks, which will be included as surface legs in all.svx. gpx_publish is for creating exportable files to personal @@ -31,12 +61,19 @@ the year directory following the 2018 example. This is the place to rename stations to follow normal conventions and to mark waypoints as entrances, etc. The file does not need to be present. -4. Open a terminal in this directory loser/ and run +4. If you have no gpx files for the current year, copy the 'dummy.gpx' file +from the 2024 year folder. + +5. Open a terminal in this directory loser/ and run the make_svx.sh script like this: bash gpx/make_svx.sh -5. Run "cavern all.svx" in loser/gpx/ then "aven all.3d". Check that the +6. Run "cavern all_gpx.svx" in loser/gpx/ then "aven all_gpx.3d". Check that the tracks appear as expected when fixed points / surface surveys are enabled. -6. Commit everything to git and push. +7. cd /loser then run gpx/make_essentials.sh + +8. Commit everything to git and push. + +--HOWEVER the essentials.gpx created by this inserts TRKSEG around every pair +of points, so this is UNUSABLE on OSMand. -7. run gpx/make_essentials.sh diff --git a/handbook/troggle/scriptscurrent.html b/handbook/troggle/scriptscurrent.html index a69444dd8..eadcfc879 100644 --- a/handbook/troggle/scriptscurrent.html +++ b/handbook/troggle/scriptscurrent.html @@ -95,14 +95,28 @@ and run

make_essentials.sh

-

In :loser:/gpx/ + +

+
+ + +

Click for enlarged view +
+
+
+

This needs re-writing because the process is highly confusing: see the "documentation" in the diagram on the right. ALSO the 2024 process created a GPX track which was unusable in OSMand (our preferred GPS app) because it put every point into a separate trkseg. +

In :loser:/gpx/ [2024 text]

Makes essentials.gpx - see GPS on expo. This used to require the gpx2survex program (written in OCAML) but now doesn't (since 2023). Get the OCAML file from GitHub https://github.com/mshinwell/gps2survex;

Read the README file in :loser:/gpx/y.

Someone needs to document this and and make_svx.sh properly. - +

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

See the entire page devoted to the various QM scripts.