{% extends "base.html" %}
{% block title %}Cave Entrances and other locations in UTM{% endblock %}

{% block content %}

<h1>Entrance locations</h1>

<p>This next table is of all the survex stations in troggle: i.e. only those survey stations which have been identified with an Entrance by manually editing the Entrance data.
<table cellpadding="6" cellspacing="8">
<tr><th>Survex Station</th><th>x</th><th>y</th><th>lat.</th><th>long.</th><th>alt</th><th>SRTM<br> alt</th><th>SRTM<br> ref</th><th>Used on ent</th><th>Cave</th></tr>
{% for s in stations %}
<tr>
  <td style="text-align:left; "> {{s.name|safe}} </td>
  <td style="text-align:right; width:10"> {{s.x|floatformat:2}} </td>
  <td style="text-align:right; width:10"> {{s.y|floatformat:2}} </td>
  <td style="text-align:right; width:10"> <em>{{s.lat|floatformat:6}} </em></td>
  <td style="text-align:right; width:10"> <em>{{s.long|floatformat:6}} </em></td>
  <td style="text-align:right; "> {{s.z|floatformat:0}} </td>
  <td style="text-align:right; "> {{s.srtm_diff.0|safe}} </td>
  <td style="text-align:right; "> {{s.srtm_diff.1|floatformat:0}}m <small></small></td>
  <td style="text-align:right;" > <a href="/cave/{{s.entrance.firstcave|safe}}">{{s.entrance|safe}}</a> </td>
  <td style="text-align:right;" > <small>
    {% if s.entrance.firstcave.official_name %}
        {{s.entrance.firstcave.official_name|safe}}
    {% else %}
        <em>{{s.entrance.firstcave|safe}}</em>
    {% endif %}</small>
  </td>
</tr>
{% empty %}
  <td colspan="3"> NO STATION DATA - This is due to survex (cavern) failing on the entire dataset.
  <br>See <a href="/dataissues">DataIssues</a> 'survex' section . 
  <br>Resolve the survex errors and do a full databasereset import. 
  <br>You should look at the .log and .err files produced by survex in the :loser: repo folder first.
  <br>
  <br>Probably, the generaton of the .3d file has failed, so the .pos file is not generated.
  <br> Look for a message like this 'Failed to find /mnt/d/EXPO/loser/1623-and-1626-no-schoenberg-hs.3d so aborting generation of new .pos, using old one if present'
  </td>
{% endfor %}
</table>

<p>The SRTM altitude is that measured at a nearby reference point. The horizontal distance between the survey station and the SRTM reference point is shown in the "SRTM ref" column. It is always less than 35m for our dataset. Differences between the recorded altitude and the SRTM altitude are in <b>bold</b> if the discrepancy is more than 60m vertically.

<p>
Coordinate systems in Austria are explained in:<br>
<a href="/handbook/survey/lasers.htm">Geographical fixed points on Loser</a><br>
<a href="/handbook/survey/coord2.html">GPS and coordinate systems</a><br>
<a href="/handbook/survey/coord.htm">Basic Coordinate Systems</a>.

<p>The data in the table immediately below has been hand-entered and is sometimes very wrong.
<p>The Lat. Long. coordinates are manually entered using a phone or a hand-held GPS device at (or near) the entrance.
<p>For the Cave column, if there is an official cave name, then it is shown. 
Otherwise whatever other name we can find for it is shown <em>in italics</em>.

<style> 
th, td {
  padding-left: 5px;
  padding-right: 5px;
}
</style>

<table>
<tr><th>Cave</th><th>Ent slug</th>
<th>tag</th><th>tag x</th><th>tag y</th><th>tag other</th><th>other x</th><th>other y</th></tr>
{% for ent in ents %}
<tr>
  <td style="text-align:left">
  {% for c in ent.cavelist %}
    <a href="/{{c.url}}">
    {% if c.official_name %}
        {{c.official_name|safe}}
    {% else %}
        <em>{{c|safe}}</em>
    {% endif %}</a><br>
  {% endfor %}</td>
 
  <td style="text-align:right">{{ent.slug}}</td>
  <td style="text-align:right">{{ent.tag_station}}</td>
  <td style="text-align:right">{{ent.tag_ts.x|floatformat:0}}</td>
  <td style="text-align:right">{{ent.tag_ts.y|floatformat:0}}</td>

  <td style="text-align:right">{{ent.other_station}}</td>
  <td style="text-align:right">{{ent.tag_os.x|floatformat:0}}</td>
  <td style="text-align:right">{{ent.tag_os.y|floatformat:0}}</td>
 </tr>
{% endfor %}
</table>

<h3>and now the GPS equivalents</h3>
<table>
<tr><th>Cave</th>
<th>Alt</th>
<th>GPS Lat</th><th>GPS Long</th>
<th>best Lat</th><th>best Long</th>
</tr>
{% for ent in gpsents %}
<tr>
  <td style="text-align:left">
  {% for c in ent.cavelist %}
    <a href="/{{c.url}}">
    {% if c.official_name %}
        {{c.official_name|safe}}
    {% else %}
        <em>{{c|safe}}</em>
    {% endif %}</a><br>
  {% endfor %}</td>
 
  <td style="text-align:right">{{ent.alt|floatformat:1}}</td>  
  <td style="text-align:right">{{ent.lat_wgs84|floatformat:6}}</td>
  <td style="text-align:right">{{ent.long_wgs84|floatformat:6}}</td>
  <td style="text-align:right">{{ent.lat|floatformat:6}}</td>
  <td style="text-align:right">{{ent.long|floatformat:6}}</td>
 
 </tr>
{% endfor %}
</table>

<h3>All entrances in Trogggle</h3>
<p> See also <a href="/entrances">Entrances list</a>.
<p>But the Entrances - the objects in the troggle system - are not properly connected to the dataset which is the combined set of survex data. They are only linked - and only implicitly - by the tag name. The data in the table below is calculated directly from 
the assemblage of survex files, including fixed point files, and is probably 'correct'. 
<p>But which coordinate system are they in ? Read these three articles to find out:
<br>
<a href="/stations">Troggle UTM and lat./lomg. and altitude report</a><br>
<a href="/entrances">Troggle entrances</a><br>
<a href="/handbook/survey/lasers.htm">Geographical fixed points on Loser</a><br>
<a href="/handbook/survey/coord2.html">GPS and coordinate systems</a><br>
<a href="/handbook/survey/coord.htm">Basic Coordinate Systems</a>.


{% endblock %}