From d34c2c50d74ee7b4daacef8c8cffed4bc1a15fe3 Mon Sep 17 00:00:00 2001 From: Philip Sargent Date: Wed, 11 Oct 2023 01:38:41 +0300 Subject: [PATCH] comments in pages --- templates/cave.html | 4 ++-- templates/eastings.html | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/templates/cave.html b/templates/cave.html index 00b2a5f..f3b36db 100644 --- a/templates/cave.html +++ b/templates/cave.html @@ -118,7 +118,7 @@ {% endif %}

Scanned survey notes

- {{ cave_id|safe }} + {{ cave_id|safe }} (if any) {% endif %} {% if cave.notes %} @@ -205,7 +205,7 @@ New Entrance

Survex File(s)

- All survexfiles for this cave
+ All survexfiles for this cave (if any)
{% if cave.survex_file %} Primary survex file for this cave
diff --git a/templates/eastings.html b/templates/eastings.html index 2bb57ed..399cb97 100644 --- a/templates/eastings.html +++ b/templates/eastings.html @@ -37,7 +37,7 @@ th, td {

OK now for the nasty bit. Many of the older caves did not have easting & northing in UTM 33T at all, but (probably) in BMN and converting between BMN into UTM requires ellipsoids and bessel functions.. or we can just take a linear approximation, which is what I have done here:
e.northingUTM = e.northingBMN + 5198919.918
e.eastingUTM = e.easting + 374854.63
-Such converted eastings and northings are in italics in the table below. As you can see, some were wildly out. +Such converted eastings and northings are in italics in the table below. As you can see, some were wildly out. Well they were until I swapped teh easting/northings around and dealt with obvious typos.

These magic numbers simply come from assuming that both BMN and UTM are in metres, and linear over our area, and then taking the avergage of the offsets for 5 locations, the 5 cave entrances at the bottom of this page: Olaf's Coordinates.

This horrible approximation is accruate to ~8m in the northing and ~30m in the easting.