Fixup large collection of mixed-linefeed files in cave_data

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

View File

@@ -37,8 +37,8 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
</entrance>
<explorers></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>; notes in 2007#41
Andrew and I decided to get a bit of gentle exercise so did a walk from 204 towards 161d/g and found not v. many promising holes for quite a lot of stomping.
<underground_description>; notes in 2007#41
Andrew and I decided to get a bit of gentle exercise so did a walk from 204 towards 161d/g and found not v. many promising holes for quite a lot of stomping.
Elev 1758m 37070 82945 5m deep surface hole with two horizontal entrances at either end. The most likely-looking lead probably.</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. -->