expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2026-04-02 03:21:03 +01:00
Code Issues Packages Projects Releases Wiki Activity

Fixup large collection of mixed-linefeed files in cave_data

Browse Source
This commit is contained in:
Wookey
2023-04-27 14:49:58 +01:00
parent af7cd5e477
commit faa5af7c3e
36 changed files with 988 additions and 988 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
cave_data/1623-2012-OK-03.html
View File

@@ -37,8 +37,8 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
</entrance>
<explorers>Olaf Kähler, Wookey</explorers><!-- 'CUCC Expo' and year(s) of exploration. To distinguish from caves explored by foreign groups. Individual names can be given too if it was a small cave. -->
<underground_description><p>Obvious hole of about 1.5m diameter in side of cliff opens up to a nice phreatic passage of considerable length. Another entrance to the left, to the right the cave becomes slightly smaller. Not explored any further, yet.</p>
<underground_description><p>Obvious hole of about 1.5m diameter in side of cliff opens up to a nice phreatic passage of considerable length. Another entrance to the left, to the right the cave becomes slightly smaller. Not explored any further, yet.</p>
<p>This cave might be identical to BS17 but no tags or signs of previous exploration could be found. Also there was almost no noticeable draught.</p></underground_description><!-- Underground description. (description of approach and entrance goes in entrance file). For a small cave this will be the entire description. For larger caves it will be the front page of the description, or a short intro, containing links to other pages with the cave description in, or even nothing but a link. -->
<equipment></equipment><!-- For a small cave, summary of gear needed to descend. For longer caves it could be blank, a table, or just refer to the description/topos. Leave blank if this info is in the description. -->
<references></references><!-- References to documentation. Could be Journal articles or Logbook entries. Can be links if the docs are online. -->