2023-10-16 11:38:54 +01:00
<!DOCTYPE html>
<!-- Only put one entrance in this file -->
2023-10-20 18:47:19 +01:00
<!-- This file is generated by troggle on Oct. 20, 2023, 5:30 p.m. UTC using the form documented at handbook/survey/ententry.html -->
2023-10-16 11:38:54 +01:00
<!-- If you edit this file by hand, and manually upload it to the server using git,
make sure you update the database by doing a full data import. If you edit it using the online form
though, you do not need to do a data import as it happens automatically -->
<!-- See http://expo.survex.com/handbook/survey/caveentryfields.html for current details on filling in this form -->
<!-- there is 1 required field: slug. The entrance will not appear without that. -->
<!-- ALWAYS use ü for u+Umlaut and ö for o+umlaut eg Höhle for Hohle and Glück for Gluck -->
< html lang = "en" >
< head >
< meta http-equiv = "Content-Type" content = "text/html; charset=UTF-8" / >
< / head >
< body >
2023-10-20 18:47:19 +01:00
< b > This file is generated by troggle< / b > on Oct. 20, 2023, 5:30 p.m. UTC using the form documented at
2023-10-16 11:38:54 +01:00
< a href = "/handbook/survey/ententry.html" > handbook/survey/ententry.html< / a >
< br >
< entrance >
< non_public > False< / non_public >
< slug > 1626-2019-HT-01< / slug > <!-- one entrance and one slug per entrance_data file -->
< name > < / name >
< entrance_description > < / entrance_description >
< explorers > < / explorers >
2023-10-20 15:32:45 +01:00
< map_description > Daniel Ginger Heins:
2023-10-20 18:47:19 +01:00
[pit] should be >10' if I recall right, so I would've thought that would've been well identifiable but point taken that in practice it doesn't seem to be as clear as I was thinking it'd be (assuming the "west of homecoming" is accurate)
< pre >
2023-10-20 15:32:45 +01:00
47.696565, 13.803737
https://www.bing.com/maps?osid=1f7cf2d0-63be-488c-bed6-7f521a459f8f& cp=47.69654%7E13.803728& lvl=20.4& style=h& v=2& sV=2& form=S00027
2023-10-20 18:47:19 +01:00
< / pre >
2023-10-20 15:32:45 +01:00
That might be it but I can't say for sure if that's actually a hole or just a cliff shadow. But nonetheless, it'd be that sort of feature - a shadow of a hole on a decent size slab of pavement.
I do think I remember clambering up the boulder on the north end of that slab, which is a decently positive sign but can't 100% say that those were the same slabs
if I had to guess this might be the other complex [Boop-da-etc] , it matches my rough recollections and notes but obviously isn't as distinct as the other
2023-10-20 18:47:19 +01:00
< pre >
2023-10-20 15:32:45 +01:00
https://www.bing.com/maps?osid=6c43eb16-8ec7-46a4-9557-083976268780& cp=47.697241~13.801916& lvl=19.845789& style=h& pi=0& v=2& sV=2& form=S00027
2023-10-20 18:47:19 +01:00
< / pre >
(that's low confidence, but it at least is a near-ish patch of exposed limestone with a cliff around half of it. the entrances wold not be as clear since they'd be obscured by cliff shadows)< / map_description >
2023-10-16 11:38:54 +01:00
< location_description > < / location_description >
< lastvisit > < / lastvisit >
< approach > < / approach >
< underground_description > < / underground_description >
< photo > < / photo >
<!-- marking options: P = Paint,
P? = Paint (?),
T = Tag,
T? = Tag (?),
R = Retagged,
S = Spit,
S? = Spit (?),
U = Unmarked,
? = Unknown" -->
< marking > U< / marking >
< marking_comment > < / marking_comment >
<!-- findability options: ? = To be confirmed ...,
S = Surveyed,
L = Lost,
R = Refindable" -->
< findability > L< / findability >
< findability_description > On Jon's GPS tracklog, which we don't have< / findability_description >
< alt > < / alt >
2023-10-20 15:36:33 +01:00
< lat_wgs84 > 47.696565< / lat_wgs84 >
< long_wgs84 > 13.803737< / long_wgs84 >
2023-10-16 11:38:54 +01:00
< tag_station > < / tag_station >
< other_station > < / other_station >
< other_description > < / other_description >
< bearings > < / bearings >
< url > < / url >
< / entrance >
< / body >
< / html >
