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

extra link and doctype additions

Browse Source
This commit is contained in:
Philip Sargent 2020-03-02 17:23:44 +00:00
parent 0dc210d665
commit db1050315d
4 changed files with 42 additions and 34 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
handbook/survey/nerd.html
View File

@ -1,6 +1,7 @@
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Handbook placeholder page</title>
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>

6
handbook/survey/newcavefile.html
View File

@ -1,5 +1,7 @@
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>Handbook placeholder page</title>
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
@ -59,6 +61,10 @@ at the bottom as this shows that this file is <code>::expoweb::/cave_data/augstb
<p>As you can see, this is an XML tag format similar to HTML but with tags defined to hold cave survey data. These files are processed by troggle in real-time to produce an HTML file on the fly which is sent to your browser so that it
looks <a href="http://expo.survex.com/augstb/4.htm">like this</a>
<p>An explanation of what the field names mean and how they are used is on
the <a href="caveentryfields.html">cave entry fields</a> page. There is not an exact correspondance between
the form and the file format however.
<p>When you fill in the online form you creating a file just like the one above: troggle takes the input data from the form and creates the file. Troggle also stores the cave information in it's live memory when you use the form method.
<p>If instead of using the form you create the file by hand and upload it to the server you will also need find a nerd to run the cave import procedure before troggle "knows" that the cave exists.
<h3>Cave entrances</h3>

2
handbook/survey/newrig.html
View File

@ -1,5 +1,7 @@
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>CUCC Expo Surveying Handbook: Drawing Up</title>
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>

5
noinfo/create_dplong_table.py
View File

@ -43,13 +43,12 @@ def print_caveline(number, l, d, w, cave):
def parse_csvfile():
caveslist = []
print "Calculating SMK-system extent... ",
print ("Calculating SMK-system extent... "),
os.popen("cavern -v7 ../loser/smk-system.svx -o noinfo/smk-system.3d")
l,d,w = map(float, chomp(os.popen(CS_BINARY + " noinfo/smk-system -c ").read()).split("\t"))
caveslist.append(["", l,d,w, {"Name" : "<i>Schwarzmooskogelh&ouml;hlensystem</i>", "Autogen file" : ""}])
print "done\nParsing Cave list"
print ("done\nParsing Cave list")
for cavefile in os.listdir("noinfo/cave_data"):
cavetabfiles = dir("noinfo/cave_data/")
fieldnames=chomp(cavetabfile.next()).replace('"','').split(",")
cavetab = csv.DictReader(cavetabfile, fieldnames)