handbook geolocated photos script

This commit is contained in:
Philip Sargent 2023-11-04 14:32:14 +02:00
parent 624fa40c6e
commit e2925138d3

View File

@ -44,6 +44,15 @@ and reports on everything using "bigbro" which we don't have any other reference
<p><a href="">updatephotos</a> (in the :loser: repo) uses the BINS package to generate photo albums. BINS uses the EXIF data (date, location if available) in the uploaded image files to produce a page showing the information available about the picture. All image meta-data are stored in XML files.
<p>BINS is no longer maintained by its author so expo has taken on the responsibility for keeping it running. (Wookey is in the process of packaging it as a proper debian package).
<h4 id="geophotos">Geolocated Photos</a></h4>
<p>In Autumn 2023 we searched all the EXIF data on all our hoto archive looking for geo-located photos. This found a few entrances which had been lost.
<p>The script is <code><a href="">/troggle/photomap/pmap.py</a></code>
which currently generates a single file <var>photos_jpg.gpx</var> which can be imported into mapping software (such as GPSprune), but does not yet hot-link to the cave description pages or the photos themselves.
<p>Each line of the gpx file is of this form:
<code>&lt;wpt lat="47.616123" lon="13.812214"&gt;<br />&lt;name&gt;[img_20170801_143731431]&lt;/name&gt;<br />&lt;type&gt;photo&lt;/type&gt;<br />&lt;desc&gt;/2017/PhilipSargent/img_20170801_143731431.jpg&lt;/desc&gt;<br />&lt;/wpt&gt;
</code>
<p>We would want to add &lt;ele&gt; for elevation and we could use GPX extensions to insert the URL info we need to make this clickable and more useful, e.g. see <a href="https://hikingguy.com/how-to-hike/what-is-a-gpx-file/">What is a GPX file</a> and <a href="https://www.mapsmarker.com/kb/user-guide/how-to-use-gpx-extensions-to-customize-tracks">GPX extensions</a>.
<h4 id="latex">seshbook, bierbook & protractors</h4>
<p>How these are used once produced is <a href="../bierbook.html">documented in the the handbook</a>
<p>These are LaTeX files and the instructions for how to process them are in each .tex file. The protractors do not change but the others need a configuration file for all the cavers expected to attend expo.
@ -88,21 +97,21 @@ and run
<h4 id="gps">make_essentials.sh</h4>
<p>In :loser:/gpx/
<p>Makes essentials.gpx - see <a href="../essentials.html">GPS on expo</a>.
This requires the gpx2survex program.
This requires the gpx2survex program (written in OCAML).
Get this from GitHub <a href="https://github.com/mshinwell/gps2survex">https://github.com/mshinwell/gps2survex;</a>
<p>Read the <a href="troggle/make-essentialsREADME.txt">README</a> file in :loser:/gpx/y.
<p>Someone needs to document this and and make_svx.sh properly.
<h4 id="surface">make_svx.sh</h4>
<p>In :loser:/gpx/
<p>Regenerates the surface tracks as survex files from GPS .gpx files.
<p>Olly says [2022]: "you shouldn't need to mess around with undocumented scripts - since 2018, you can just do:
<p>Regenerates the surface tracks as survex files from GPS .gpx files. Also requires the gpx2survex program.
<p>For the reverse process we don't need a script. For svx-to-gps we can use <var>survexport</var>: Olly says [2022]: "you shouldn't need to mess around with undocumented scripts - since 2018, you can just do:
<var>survexport --entrances all.3d essentials.gpx</var>"
<p>But that does rather rely on <var>all.3d</var> being properly generated, which troggle does not currently do reliably and automatically.
<p>Documented, by <var>man survexport, survexport --help</var>,
and in the Survex manual on <a href="https://survex.com/docs/manual/survexport.htm">survexport</a>.
<p><span style="color:red">[to be documented]</span>
<h4 id="ocaml">convert_shx.ml</h4>
<p>Unusually, this is in the <var>:loser:</var> repository, in :loser:/fixedpoints/scripts/convert_shx/