expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-12-22 16:32:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

restoring html files, not the same as xml files..

Browse Source
This commit is contained in:
Philip Sargent 2024-06-30 19:45:33 +03:00
parent facc530e1d
commit c0e8a77de5
2 changed files with 133 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

60
templates/cave_data.html Normal file
View File

@ -0,0 +1,60 @@
!DOCTYPE html>
-<!-- Only put one cave in this file -->
-<!-- If you edit this file, make sure you update the websites database -->
-<!-- ALTERNATIVELY you can use the online troggle form. The template for this is
- in troggle/templates/dataformat/cave.xml and the code in troggle/core/forms.py and
- troggle/views/caves.py . Default values are in the troggle/templates/dataformat/*.xml file -->
-<html lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-</head>
-<body>
- <cave>
- <!-- See http://expo.survex.com/handbook/survey/caveentryfields.html for current details on filling in this form -->
- <!-- there are 4 required fields: caveslug, area, kataster_number or unofficial_number, and url. The cave will not appear without all those. -->
- <!-- ALWAYS use &uuml; for u+Umlaut and &ouml; for o+umlaut eg H&ouml;hle for Hohle and Gl&uuml;ck for Gluck-->
-
-<non_public></non_public> <!-- 'False' or 'True'. True if the cave should only be visible to logged-in users. Caves are normally public, so enter 'False' unless you know otherwise. -->
-<caveslug></caveslug> <!--(Required). Internal I.D. used to refer to this cave in entrance data files. Typically the same as the filebase, e.g. '1623-195' -->
-<official_name></official_name> <!-- Name of the cave (normally in German) -->
-<area></area> <!-- (Required).The Kataster area (always 1623 or 1626). It's important to get this right, especially if near the border between the two areas. 1623 is our main area, but the border is not too far beyond the Stone Bridge so since 2014 some of our caves are in 1626. -->
-<area></area> <!-- Yes - there really are two different fields, both called 'area'. Bonkers. This second one is the CUCC-defined areas shown in http://expo.survex.com/areas.htm -->
-<kataster_code></kataster_code> <!-- 'length-or-depth/type exploration'
-code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast.htm
-
- T Trockenh&ouml;hlen (Dry caves)
- W Wasserh&ouml;hlen (Caves with water)
- (W) Zeitweilig aktiv Wasserh&ouml;hlen (Caves with seasonal water)
- E Eishohlen (Caves with ice formations)
- S Schachth&ouml;hlen (Caves with pitches)
- H Halbh&ouml;hlen (Rock shelters ?)
-
- - unerforscht (unexplored)
- = befahren (visited)
- × teilweise vermessen (partly surveyed)
- + erforscht (exploration considered complete)
- -->
-<kataster_number></kataster_number> <!-- (Either this or unofficial_number is required). Official number in Austrian kataster if one has been allocated -->
-<unofficial_number></unofficial_number> <!-- (Either this or kataster_number is required). Initial temporary cave ID used until kataster number is allocated e.g. '2012-DD-01'-->
-
-<!-- Add one entrance stanza for each entrance-->
-<entrance>
- <entranceslug></entranceslug> <!-- Internal ID to refer to each entrance instance in the entrance files (typically the same as that filename (e.g. 1623-161c). Matches the 'slug' field in the entrance file -->
- <letter></letter> <!--Leave blank for single-entrance cave. If there is more than one entrace then the letter needs to be given. Generally matches the entranceslug ID. -->
-</entrance>
-
-<explorers><p></p></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></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><p></p></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. -->
-<survey><p><div class="centre"></div><p></survey> <!-- Drawn-up surveys. Scans of paper surveys or images/PDFs of electronic surveys. Should include HTML to display current plan and elevation, with links to larger versions (See section on URLs and files). Could list links to multiple years of survey, or even a separate survey page if it's complicated enough. -->
-<kataster_status></kataster_status>
-<underground_centre_line></underground_centre_line> <!-- 'In dataset' if it is in the survex dataset. Blank if not, or notes about status such as 'surveyed, but no entrance fix so not yet in dataset'. -->
-<notes></notes> <!-- Normally empty, but place for anything else that should be noted, such as info on cave maybe being a duplicate, or lost -->
-<length></length> <!-- Cave length. Can be left blank and system should fill it in automatically from survey data (it doesn't yet) -->
-<depth></depth> <!--Cave depth. Can be left blank and system should fill it in automatically from survey data (it doesn't yet) -->
-<survex_file></survex_file> <!-- Name of top-level survey file for this cave. Relative to the 'loser' survex repository. So for most caves that's "caves/cavenum/cavnum.svx". (e.g. caves/204/204.svx -->
-<description_file></description_file><!-- Path of top-level description file for this cave, when a separate file is used. Otherwise blank. -->
-</cave>
-</body>
-</html>

73
templates/entrance_data.html Normal file
View File

@ -0,0 +1,73 @@
-<!DOCTYPE html>
-<!-- Only put one entrance in this file -->
-<!-- If you edit this file, make sure you update the websites database -->
-<!-- ALTERNATIVELY you can use the online troggle form. The template for this is
- in troggle/templates/dataformat/entrance.xml and the code in troggle/core/forms.py and
- troggle/views/caves.py . Default values are in the troggle/templates/dataformat/*.xml file -->
-<html lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-</head>
-<body>
- <!-- See http://expo.survex.com/handbook/survey/caveentryfields.html for current details on filling in this form -->
- <!-- there is 1 required field: slug. The entrance will not appear without that. -->
- <!-- ALWAYS use &uuml; for u+Umlaut and &ouml; for o+umlaut eg H&ouml;hle for Hohle and Gl&uuml;ck for Gluck-->
-
-<entrance>
-<non_public></non_public> <!-- 'False' or 'True'. True if the cave
-should only be visible to logged-in users. Caves are normally public,
-so enter 'False' unless you know otherwise. -->
-<slug></slug> <!-- Internal I.D. referring to this entrance. Must match
-entranceslug in cave_data file. -->
-<name></name> <!-- Entrance name if it has a specific one. Normally empty.
--->
-<entrance_description></entrance_description> <!-- What does entrance
-look like -->
-<explorers></explorers> <!-- 'CUCC Expo' and year(s) of exploration.
-To distinguish from caves explored by foreign groups. Names can be
-given too if it was a small cave, or of original discoverer. -->
-<map_description></map_description> <!-- Location on specific map
-sheet - hardly ever used. -->
-<location_description></location_description> <!-- Immediate area. How
-to find entrance -->
-<approach></approach> <!-- Best approach to cave e.g. from path/other
-cave/landmark -->
-<underground_description></underground_description> <!-- -->
-<photo><p><div class="centre"></div></p></photo> <!-- -->
-<!-- marking options: P = Paint,
- P? = Paint (?),
- T = Tag,
- T? = Tag (?),
- R = Re-tagged,
- S = Spit,
- S? = Spit (?),
- U = Unmarked,
- ? = Unknown" -->
-<marking></marking>
-<marking_comment></marking_comment> <!-- Clarifying comments about
-marking, if needed -->
-<!-- findability options: ? = To be confirmed ...,
- S = Surveyed,
- L = Lost,
- R = Refindable" -->
-<findability></findability>
-<findability_description></findability_description> <!-- Notes about
-findability, if needed -->
-<alt></alt> <!-- Altitude of entrance -->
-<northing></northing> <!-- Northing of entrance (WGS84 or UTM33).
-Leave for computer to calculate -->
-<easting></easting> <!-- Easting of entrance (WGS84 or UTM33). Leave
-for computer to calculate -->
-<tag_station></tag_station> <!-- Which loser dataset (survex) point is the tag (if
-surveyed) -->
-<exact_station></exact_station> <!-- Which loser dataset (survex)
-point is deemed as 'the entrance' (should be ground level at edge of
-'underground') -->
-<other_station></other_station> <!-- Other loser dataset (survex)
-points deemed important for this entrance-->
-<other_description></other_description> <!-- Notes on why
-other_station is relevant, if needed -->
-<bearings></bearings> <!-- Bearings from landmarks (from pre-GPS days) -->
-</entrance>
-</body>
-</html>