expoweb/cave_data
..
2023-09-06 21:58:30 +01:00
2023-09-16 18:54:47 +01:00
2023-09-06 21:56:51 +01:00
2023-09-22 20:17:55 +01:00
2023-09-07 13:16:19 +01:00
2023-09-11 18:06:39 +03:00
2023-09-16 19:15:39 +01:00
2023-07-26 18:34:17 +03:00
2023-07-13 16:07:34 +01:00
2023-07-27 17:13:40 +03:00
2023-09-11 18:06:39 +03:00
2023-08-03 16:11:05 +03:00
2023-07-10 07:14:10 +01:00
2023-07-24 17:33:06 +03:00
2023-07-27 14:55:26 +03:00
2023-09-11 17:11:34 +01:00
2023-09-26 00:55:02 +03:00
2023-07-26 19:48:20 +03:00
2023-09-15 18:21:59 +01:00
2023-09-26 12:46:52 +01:00
2023-08-01 23:05:13 +01:00
2023-07-27 14:55:26 +03:00
2023-09-25 23:12:35 +03:00
2023-09-26 00:55:02 +03:00
2023-07-27 14:55:26 +03:00
2023-07-27 15:08:38 +03:00
2023-07-27 15:08:38 +03:00
2023-07-27 15:08:38 +03:00
2023-09-26 00:55:02 +03:00
2023-07-27 13:47:48 +03:00
2023-07-27 13:47:48 +03:00
2023-07-27 13:47:48 +03:00
2023-07-27 13:47:48 +03:00
2023-07-27 01:03:46 +03:00
2023-07-27 01:03:46 +03:00
2023-07-27 01:03:46 +03:00
2023-07-27 01:03:46 +03: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.