Files
expoweb/cave_data
..
2024-11-08 02:37:45 +00:00
2024-11-08 02:37:45 +00:00
2024-11-08 02:37:45 +00:00
2024-11-08 02:37:45 +00:00
2025-10-31 22:29:45 +00:00
2024-11-08 02:37:45 +00:00
2024-11-08 02:37:45 +00:00
2024-11-08 02:37:45 +00:00
2024-11-08 02:37:45 +00:00
2024-11-08 02:37:45 +00:00
2025-03-11 17:48:07 +00:00
2025-02-11 00:25:42 +00:00
2025-08-28 21:40:33 +01:00
2025-03-11 14:35:44 +00:00
2024-11-08 02:37:45 +00:00
2025-11-02 22:46:19 +00:00
2025-07-25 10:25:35 +01:00
2025-03-04 17:46:18 +00:00
2024-11-08 02:37:45 +00:00
2024-11-08 02:37:45 +00:00
2024-11-08 02:37:45 +00:00
2024-11-08 02:37:45 +00:00
2024-11-08 02:37:45 +00:00
2025-03-03 00:29:23 +00:00
2024-11-08 02:37:45 +00:00
2025-07-28 21:35:36 +02:00
2025-07-28 21:35:36 +02:00
2025-07-28 21:35:36 +02:00
2025-07-28 21:35:36 +02:00
2025-07-28 21:35:36 +02:00
2024-11-08 02:35:38 +00:00
2024-11-08 02:37:45 +00:00
2025-11-01 11:01:37 +02:00
2024-11-08 02:37:45 +00:00
2024-11-08 02:37:45 +00:00
2024-11-08 02:37:45 +00:00

The pendingcaves.txt file lists caves for which we haven't yet got around to creating 
a cave_data/162n-xxx.html description file.

e.g. 
https://expo.survex.com/1626/E02
or 
https://expo.survex.com/1623/2014-bl888

the dummy data is created by
def do_pending_cave(k, url, area) in troggle/parsers/caves.py

No actual cave description file is created, just the entry in the database.

If the first part of the name is not 1623- or 1626- then the cave is assumed to be in the 1623 area.