{% extends "base.html" %}
{% load wiki_markup %}
{% load link %}

{% block title %}Expo statistics{% endblock %}

{% block content %}
<h1>Expo Statistics</h1>

<p>{{ expoCount }} expeditions: {{ personCount }} people,  {{ caveCount }} caves and {{ logbookEntryCount }} logbook entries. 

<p>Number of survey legs: {{nsurvexlegs}}<br />
Total length: {{totalsurvexlength|stringformat:".1f"}} km added-up on importing survex files.<br />
Total length: {{addupsurvexlength|stringformat:".1f"}} km adding up the total for each year.</p>

<p>These are raw tape lengths which include pitches, splays and surface-surveys. There is also some doubt that the parsing is 
correct so maybe some long lengths are misinterpeted: compass readings as tape-lengths for example: LoadSurvexDataCmd
in parsers/survex.py would be a good place to start.
<p>
This is work in progress (July 2020).

<p>However the number of survey legs should be correct, and the by-year total <em>should</em> be 
the same as the by-file-import total.<br>Obviously there is still work to do.

<table>
<tr><th>Year</th><th>Survex<br>Survey<br>Blocks</th><th>Survex<br>Survey Legs</th><th>Total length<br>(m)</th></tr>
{% for legs in legsbyexpo %}
<tr>
  <td>{{legs.0.year}}</td>
  <td style="text-align:center">{{legs.0.survexblock_set.all|length}}</td>
  <td style="text-align:center">{{legs.1.nsurvexlegs|rjust:"10"}}</td>
  <td style="text-align:right">{{legs.1.survexleglength}}</td>
</tr>
{% endfor %}
</table>
<p>One Survex Survey Block is one *begin/*end block of data in a survex file. 
Some files from other caving clubs may have a convention of using many more blocks per file than we do, e.g. if the 
file is exported from other software into survex format.
{% endblock %}