Files
expoweb/cave_data
2025-11-02 18:59:28 +00:00
..
2025-09-27 12:16:50 +03:00
2025-09-27 12:16:50 +03: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
2025-03-11 17:48:07 +00:00
2025-03-06 17:33:41 +00:00
2025-03-11 15:12:01 +00:00
2024-11-08 02:37:45 +00:00
2025-03-11 18:55:56 +00:00
2024-11-08 02:37:45 +00:00
2024-11-08 02:37:45 +00:00
2025-07-18 15:56:03 +01:00
2025-03-10 20:41:43 +00:00
2024-11-08 02:37:45 +00:00
2025-03-07 18:51:26 +00:00
2024-11-08 02:37:45 +00:00
2024-11-08 02:37:00 +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
2024-11-08 02:37:45 +00:00
2025-07-28 21:35:36 +02:00
2025-07-28 21:35:36 +02:00
2024-11-08 02:37:45 +00:00
2024-11-08 02:37:45 +00:00
2025-11-02 18:59:28 +00:00
2025-11-01 11:01:37 +02: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.