2018-07-16 12:52:49 +01:00
< html >
< head >
< meta http-equiv = "Content-Type" content = "text/html; charset=utf-8" / >
< title > CUCC Expedition Handbook: Uploading files/photos< / title >
2024-02-09 00:01:17 +00:00
< link rel = "stylesheet" type = "text/css" href = "/css/main2.css" / >
2018-07-16 12:52:49 +01:00
< / head >
< body >
< h2 id = "tophead" > CUCC Expedition Handbook< / h2 >
2019-07-17 12:09:09 +01:00
< h1 > Saving GPS tracks and locations< / h1 >
2018-07-16 12:52:49 +01:00
< h2 > The end-result you are trying to achieve< / h2 >
What you are trying to do is to get your recorded locations (waypoints) and wanderings (tracks)
2019-07-17 12:09:09 +01:00
< ol >
< li > recorded somewhere,
< li > eventually appear properly in the cave survey database.
< / ol >
< p > To make this happen you have to transfer
2018-07-16 12:52:49 +01:00
the tracks and waypoints in a GPX file to the right place.
2019-07-17 12:09:09 +01:00
2018-07-16 12:52:49 +01:00
< p > If you are really lazy (or really a beginner) you can use the simple upload method, but there are some
unavoidable complexities in getting the GPX file out of your device.
< p > < em > (If you are looking for how to upload some photos instead, those instructions are
< a href = "uploading.html" > here< / a > )< / em > .
2022-03-20 00:31:49 +00:00
< h3 > TEMPORARY FIX 2022< / h3 >
< p > The form to make this easy is not yet written [March 2022]. So use the < a href = "/photoupload/" > Photo Upload Form< / a > which
temporarily will also work for GPX files.
2024-05-11 11:19:26 +01:00
< h3 > Editing your tracks< / h3 >
We would much rather have any track than nothing at all: any weirdness can be fixed later. But if you really want to edit out th eglitches yourself, the online GPX editor < a href = "https://gpx.studio/about.html" > GPX Studio< / a > is very good. Or you can download < a href = "https://activityworkshop.net/software/gpsprune/" > GPSprune< / a > to your laptop (it's a java app) and run it locally.
2018-07-16 12:52:49 +01:00
< h3 > Instructions: contents< / h3 >
< ol >
2018-08-25 11:08:35 +01:00
< li > < a href = "#getgpx" > Get the GPX file< / a > that holds your locations and wanderings from your phone.
2019-07-17 12:09:09 +01:00
< li > < a href = "#simplegpx" > Upload the GPX file< / a > to the proper place.
2018-07-16 12:52:49 +01:00
< / ol >
< h2 id = "getgpx" > Getting the GPX data out of your phone or device< / h2 >
< ol >
< li > Use the "Wikilocs" app (or another app with GPS tracking function) to record your track as you walk across the plateau.
< li > When you have finished your walk and are back on the internet, publish your track using the app.
2019-07-17 12:09:09 +01:00
< li > In the app, if there is an option to "share" your track by email:
2018-07-16 12:52:49 +01:00
< ul >
< li > Share it with yourself i.e. email it to your own email address.
< li > Share it with someone who knows how to do the GPX thing and upload it properly.
< / ul >
< li > On your laptop (or possibly on your phone) look at the email and visit the web page by clicking on the link.
< li > The web page has a "Download" button: click on it.
< li > It may give you options such as "Garmin", or "File". Choose "File".
< li > It will ask for a filename to use. Pick something like "northplat-asmith-2018-07-29" (if your name is Aaron Smith)
< li > A GPX file "northplat-asmith-2018-07-29.gpx" will be downloaded to the Downloads folder on your laptop.
2021-04-29 15:21:31 +01:00
< li > Write a note in < a href = "../logbooks.html" > the expo logbook< / a > to say what you have done with a short description of what you saw and found.
2018-07-16 12:52:49 +01:00
< / ol >
< p >
Congratulations. You now have your track recorded using GPS as a GPX file.
2019-07-17 12:09:09 +01:00
< h3 id = "simplegpx" > Simple upload instructions< / h3 >
2018-07-16 12:52:49 +01:00
< ol >
< li > Email the public link from the app to someone who knows how to do it. < br >
< li > Email the GPX file to someone who knows how to do it. < br >
2018-08-25 11:08:35 +01:00
GPX files are small enough for email systems, so don't be shy of adding them as attachments.
2021-04-29 15:21:31 +01:00
< li > Write a note in < a href = "../logbooks.html" > the expo logbook< / a > to say what you have done with a short description of what you saw and found.
2018-07-16 12:52:49 +01:00
< / ol >
2018-07-17 21:52:37 +01:00
< p > If you can't find someone who knows how to do it, find the most extreme nerd you can find and point them at the
< a href = "#expert" > Expert instructions< / a > below.
2018-07-16 12:52:49 +01:00
2018-07-17 21:52:37 +01:00
< h3 > Slightly less simple upload instructions< / h3 >
< p > Using your own laptop on expo, or after you return from expo,
use the "more complex" instructions for < a href = "uploading.html" > uploading photos< / a > to /uploads/,
2021-04-29 15:21:31 +01:00
but upload your GPX files instead. But < em > none of this will work< / em > on your own laptop until you have also done the < a href = "keyexchange.html" > key-pair setup< / a > procedure.
2018-07-16 12:52:49 +01:00
2019-07-17 12:09:09 +01:00
< h2 id = "uploadgpx" > More complex upload instructions< / h2 >
< p > OK you now have a file produced by your device, something like XTR20170714X2345.GPX .
< ol >
< li > First you rename it
to something recognisable such as 'top-camp-to-toilet-grike.gpx' (all lower case).
< li > On the < i > expo laptop< / i > copy it to a folder in/home/expo/Downloads/gpslogs/YourName/
< li > Tell someone you have done it.
2021-04-29 15:21:31 +01:00
< li > Write a note in < a href = "../logbooks.html" > the expo logbook< / a > to say what you have done with a short description of what you saw and found.
2019-07-17 12:09:09 +01:00
< / ol >
< br > < br > < br > < br >
2018-07-17 21:52:37 +01:00
< h2 id = "expert" > Experts only< / h2 >
< p >
2018-08-25 11:08:35 +01:00
GPX data is stored in two places.
< ul >
< li > initially in < em > expofiles/gpslogs/...< / em >
2021-04-29 15:21:31 +01:00
< li > some key selected tracks are later stored in the cave survey < a href = "repos.html" > repository< / a > < em > :loser:< / em >
2018-08-25 11:08:35 +01:00
< / ul >
< p >
GPS tracks are voluminous and we also get a lot of repetition
as people tend to follow the same routes for part of their walks. So the initial raw data is kept in
< pre >
expofiles/gpslogs/< year> /< MyName> /
< / pre >
e.g.
< pre >
expofiles/gpslogs/2018/PhilipSargent/
< / pre >
< p > and you can create sub-folders for raw data and edited data, or for different parts of the plateau. You should always
keep the raw, untouched data as well as any hand-edited data.
< p > The process for uploading the GPX files to a specific folder < em > expofiles/gpslogs/...< / em > is exactly the
same as for uploading photographs, so go to < a href = "uploading.html#morecomplex" > these "more complex" instructions< / a >
to learn how to do it.
< p > Note the naming convention for this folder created by Philip Sargent in 2018.
Human names in folders in expofiles are written in CamelCase; not lower-case letters.
This is for consistency with the naming for
< a href = "uploading.html#experienced" > uploading photos< / a > .
< p >
If you have edited GPS tracks and waypoints with no extraneous data
then, after agreeing this with other people as to its qualityand appropriateness,
2020-04-26 21:41:21 +01:00
it will go into the < a href = "/repositories/" > Loser git repository< / a >
2018-08-25 11:08:35 +01:00
in folder < em > /gpx/< year> /< / em > e.g. < br >
2020-04-11 17:46:18 +01:00
< em > :loser:/2018/stone-bridge-to-fischgesicht_aday-2018-07-12.gpx< / em > < br >
2018-08-25 11:08:35 +01:00
< p > Note the naming convention for this file created by Anthony Day on July 12th 2018.
Everything in any repository is always named using lower-case letters.
2024-05-11 11:19:26 +01:00
< hr / > < / body >
2018-07-16 12:52:49 +01:00
< / html >
