2018-07-16 17:36:16 +01:00
< html >
< head >
2022-06-22 22:59:33 +01:00
< meta http-equiv = "Content-Type" content = "text/html; charset=utf8" / >
2018-08-04 12:39:43 +01:00
< title > Essential GPS information< / title >
2024-02-08 18:34:01 +00:00
< link rel = "stylesheet" type = "text/css" href = /css/main2.css / >
2018-07-16 17:36:16 +01:00
< / head >
< body >
< h2 id = "tophead" > CUCC Expedition Handbook< / h2 >
2018-07-17 18:58:28 +01:00
< h1 > Essential GPS information< / h1 >
2022-08-16 13:33:25 +01:00
< p > < b > SAFETY< / b > . Everyone < a href = "/guidebook/plateau.html" > gets lost on the plateau< / a > . Don't get lost for long as this causes rescue plans to be initiated.
2019-07-16 10:17:07 +01:00
So get this essential data onto your phone (or handheld GPS).
2023-06-30 15:20:30 +01:00
< style > t d , t h
{border: solid 1px #ccc; border-radius: 4px; text-align: center;}
< / style >
2024-07-08 08:28:38 +01:00
2023-06-30 15:20:30 +01:00
< table style = "width: 100%;" >
< tr > < th > GPX format< / th > < th > KML format< / th > < th > ZIP of both< / th > < / tr >
2024-07-08 08:28:38 +01:00
< tr >
2024-07-08 10:08:28 +01:00
< td > < a download href = "essentials2024.gpx" > essentials2024.gpx< / a > < / td >
2024-07-08 10:30:05 +01:00
< td > < a download href = "essentials2024.kml" > essentials2024.kml< / a > < / td >
< td > < a download href = "essentials2024.zip" > essentials2024.zip< / a > < / td >
2024-07-08 08:28:38 +01:00
< / tr >
2023-06-30 15:20:30 +01:00
< tr >
2024-07-08 11:39:19 +01:00
<!-- NOTE downloads from the handbook are from /expoweb/ repo and are managed by troggle and the correct "Content type" is set,
2024-07-08 12:02:05 +01:00
whereas files downloaded from /expofiles/ are just managed by apache and so Chrome on Android munges the filename -->
2024-07-08 11:39:19 +01:00
< td > < a download href = "/expofiles/gpslogs/essentials/essentials.gpx" > essentials.gpx< / a > < / td >
< td > < a download href = "/expofiles/gpslogs/essentials/essentials.kml" > essentials.kml< / a > < / td >
< td > < a download href = "/expofiles/gpslogs/essentials/essentials.zip" > essentials.zip< / a > < / td >
2023-06-30 15:20:30 +01:00
< / tr >
< / table >
2019-12-05 02:27:01 +00:00
< p > < b > SAFETY< / b > . Turn on < b > location tracking< / b > in Google Maps (or OsmAnd) before you leave the car park and share your location with someone you know at basecamp and also with someone you know at top camp. This will show your last known location if you walk into an area of bad signal.
2022-08-16 13:27:55 +01:00
< ul >
< li > If you are looking for how to upload one of your own GPS tracks, go to < a href = "/handbook/computing/gpxupload.html" > gpxupload< / a > .
< / ul >
2019-07-16 10:17:07 +01:00
< p >
2022-08-06 21:19:47 +01:00
We have a file of the wiggly tracks of the paths we regularly take: from Loser Alm car park to the col, top camp and caves currently being visited.
2018-07-16 17:36:16 +01:00
2019-07-16 10:17:07 +01:00
< p > [It also has the Austrian "kataster boundaries": these are < b > not paths< / b > but separate areas with
different mapping designations.
These are the smooth, curved lines.]
2018-07-16 17:36:16 +01:00
2022-08-06 21:19:47 +01:00
The file also includes all the cave entrances for the entire Schwartzmooskö gel system (SMK).< / p >
2024-07-08 10:30:05 +01:00
< a href = "http://expo.survex.com/expofiles/gpslogs/essentials/" > < img width = 60% src = "essentials2024.jpg" alt = "screenshot of the GPS file" > < / a >
2018-07-17 18:58:28 +01:00
2020-05-03 16:39:47 +01:00
< p > < b > Don't be misled by the apparent simplicity< / b > of the above tracks. The plateau is very broken and is
an unremitting extent of cliffs, holes and impassable dwarf-larch scrub ("bunde" as it is known on expo).
2022-08-16 13:33:25 +01:00
You can be 5m from the route and have lost it entirely. The < a href = "/guidebook/walkin.htm" > walk to and from< / a >
2020-05-03 16:39:47 +01:00
col leading to the plateau is comparatively easy is it is an obvious path, and marked and signposted in the earlier section.
2019-07-16 10:17:07 +01:00
< h2 > How to get this essential data onto your device< / h2 >
2022-08-06 21:19:47 +01:00
< p > Do one of< / p >
2019-07-16 10:17:07 +01:00
< ul >
2022-08-06 21:19:47 +01:00
< li > < a href = "#down" > Download the GPX file from the expo server direct to computer/phone/GPS< / a > - recommended
< li > < a href = "#up" > Upload the GPX file to phone/GPS from computer< / a >
2019-07-16 10:17:07 +01:00
< / ul >
2022-08-06 21:19:47 +01:00
< p > or, if you can't get those to work< / p >
2019-07-16 10:17:07 +01:00
< ol >
2022-08-06 21:19:47 +01:00
< li > < a href = "#sideways" > Download the data to your phone from an online GPS app< / a >
2019-07-16 10:17:07 +01:00
< / ol >
< h2 id = "sideways" > Get GPS essentials from an online service< / h2 >
< b > BEING UPDATED - OUT OF DATE FILE< / b >
< p > Try this link
2018-07-29 09:13:41 +01:00
< a href = "https://www.wikiloc.com/outdoor-trails/carpark-stonebridge-27029006&utm_source=social&utm_medium=twitter.com&utm_campaign=badge" >
Wikilocs< / a >
2019-07-16 10:17:07 +01:00
from where you can download a short version of the file (track and one waypoint at StoneBridge only)
or a Google Earth trail (you need to create a Wikiloc account first < em > and be logged-in< / em >
when you click on this). Or here is another < a href = "https://www.wikiloc.com/wikiloc/download.do?id=27029006" > direct download link< / a > .
2018-07-17 18:58:28 +01:00
2019-07-16 10:17:07 +01:00
< h2 id = "down" > Download the GPS essentials file from the expo server< / h2 >
2022-08-06 21:19:47 +01:00
< p > The most recent GPX file can be downloaded from here:
< a href = "https://expo.survex.com/expofiles/gpslogs/essentials/essentials.gpx" download > essentials.gpx< / a > (596K).
< p > The most recent entrances-only GPX file can be downloaded from here:
< a href = "https://expo.survex.com/expofiles/gpslogs/essentials/entrances.gpx" download > entrances.gpx< / a > (60K).
< p > (There are also individual tracks < a href = "https://expo.survex.com/expofiles/gpslogs/essentials/" > downloadable here< / a > )< / p >
2019-07-16 10:17:07 +01:00
< p >
2022-08-06 21:19:47 +01:00
This is easy on a laptop, but phone browsers make it difficult to download a simple link like that - just clicking will usually (unhelpfully) display it in the browser.< / p >
< p > You need to long-click and pick 'download file' or 'download link' (chrome). Then either:
< ol >
< li > Go to your 'Downloads' folder and tap on the GPX file, which should offer to load it in OSMand, or whatever other map software you use, or< / li >
< li > Go into OSMand, select 'My places' and 'IMPORT', then select the file.< / li >
< / ol >
< / p >
< p > OSMand defaults to not displaying labels on the caves. Go to 'configure map', and turn on 'Point Labels (POI, Favourites)'.< / p >
2018-07-17 18:58:28 +01:00
< h2 id = "up" > Upload the GPS essentials file to your device< / h2 >
< p >
2022-08-06 21:19:47 +01:00
This is where it gets tricky because every device and phone app does this differently.< / p >
2018-07-17 18:58:28 +01:00
2019-07-16 10:17:07 +01:00
2018-07-27 12:12:19 +01:00
< h3 > GPS phone apps< / h3 >
< p >
This should work the same way whether you have an iPhone or an Android phone.
2022-08-06 21:19:47 +01:00
< p > We recommended < a href = "https://osmand.net/" > OsmAnd< / a > as it is very capable, but you can use others.
2018-07-27 12:12:19 +01:00
< p >
2024-04-21 10:04:53 +01:00
< p > On android phones, this may be best achieved by installing from < a href = "https://f-droid.org/" > F-Droid< / a > rather than the plan store< / p >
2024-04-21 10:23:35 +01:00
2024-04-21 14:52:40 +01:00
< p > The map area to download is Austria - Upper Austria. < / p >
2022-08-06 21:19:47 +01:00
2018-07-27 12:12:19 +01:00
< p > The OsmAnd documentation says:
< ul >
< li > "The simplest way to view a track you've downloaded is to tap on it in your device's file manager and choose to open it in OsmAnd. After that, you'll see the track in My places - My tracks or in the Dashboard - My tracks."
< / ul >
< p >
More documentation on this to follow...
2024-04-21 14:52:40 +01:00
< p > On iPhones the prefered app is gaia GPS< / p >
2018-07-27 12:12:19 +01:00
< h3 > Modern Garmin handheld GPS devices< / h3 >
< p >
Connect the GPS device to your laptop (or the expo laptop) using the USB cable. A folder will open on the laptop showing the contents
of the device.
You will see a subfolder called "GARMIN". Open the folder "GARMIN" and copy the file essentials.gpx which you
downloaded into that folder.
2020-05-24 22:39:55 +01:00
< p > Even modern (2019) Garmin GPS devices use this old style mini-USB socket. So you will need the special cable that comes with the device. An ordinary phone USB cable won't work.
< p >
< figure >
< img src = "t/usb-minib-5pin-m-c.jpg" alt = "mini-USB socket" / >
< figcaption > < em > mini-USB b socket< / em > < / figcaption >
< / figure >
2018-07-27 12:12:19 +01:00
2020-05-24 22:39:55 +01:00
< h3 > Very Old Garmin handheld GPS devices< / h3 >
2018-07-17 18:58:28 +01:00
< p >
2019-07-16 10:17:07 +01:00
These need the Garmin communication protocol to import cave entrance locations (waypoints) and paths (tracks).
You can't do it by simply copying files.
This means that you need special software on your laptop in addition to a USB cable that
connects your laptop to the Garmin device.
2020-05-24 22:39:55 +01:00
2018-07-27 16:05:43 +01:00
< p > Once you have the right cable and connected your handheld to your laptop:
2018-07-17 18:58:28 +01:00
< ul >
< li > On a Windows machine, use "GPSbabel for Windows" which has an easy to use graphical user interface:
< a href = "https://www.gpsbabel.org/download.html" > download GPS Babel< / a >
< li > On a Linux machine the core gpsbabel command line utility is probably already installed;
but there is no simple, easy to use graphical interface.
Instead you must use other software such as QGIS or Viking (download using your usual Linux software installer)
which uses gpsbabel to talk to your device.
2018-07-27 16:05:43 +01:00
If this doesn't work then there are no useful error messages from Viking.
2018-07-17 18:58:28 +01:00
< / ul >
2019-07-16 10:17:07 +01:00
< h2 id = "down" > Nerds only: getting the < i > very latest< / i > GPS essentials file < / h2 >
< p >
We create a new version of this essential GPS data during expo and as expoers discover new entrances and
devise new routes to reach them.
< p >
To regenerate the < i > most recent version< / i > which contains the cave entrances discovered during expo
you will need to ask someone who is competent in logging into the server and running scripts.
2020-05-24 22:39:55 +01:00
< p > The data is in the version control system < a href = "computing/repos.html" > repository< / a > < var > :loser:< / var > in
2019-07-16 10:17:07 +01:00
< pre >
loser/gpx/
< / pre >
2020-05-24 22:39:55 +01:00
and is generated from the survex data by a script. It is best to do this on a laptop which has the entire < var > :loser:< / var >
2019-07-16 10:17:07 +01:00
repo downloaded onto it (e.g. the < i > expo laptop< / i > ) rather than on the server itself as the server can run out of memory doing this.
< p > The most recent track data will have been uploaded by an expoer into e.g.
< pre >
expofiles/gpslogs/2019/MichaelSargent/col-to-homecoming-msargent-2019-07-14_18-38_Sun.gpx
< / pre >
< p > and this will need to be hand-edited into script-generated essentials.gpx file.
2022-03-05 01:03:47 +00:00
< h3 > Regenerating the essentials.gpx file< / h3 >
< p > There are two scripts needed for this:
< a href = "troggle/scriptscurrent.html#gps" > make_essentials.sh< / a > and
< a href = "troggle/scriptscurrent.html#surface" > make_svx.sh< / a >
both of which are stored in the < var > :loser:< / var > repository in :loser:/gpx/ .
< p > Read the < a href = "troggle/make-essentialsREADME.txt" > README< / a > file in that directory.
< p > They are documented in the long list of < a href = "troggle/scriptsother.html" > Other scripts< / a > .
2018-07-16 17:36:16 +01:00
< hr / >
< li > < a href = "../index.htm" > Back to Expedition Intro page< / a > < / li >
< li > < a href = "../../index.htm" > Back to CUCC Home page< / a > < / li >
2023-06-30 15:20:30 +01:00
< / ul > < / body >
2018-07-16 17:36:16 +01:00
< / html >