<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0mm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0mm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoPlainText>Thanks Wookey,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>So these 3 files need editing to remove the mistaken location in 1626 ?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText style='margin-left:36.0pt'>:loser:/kataster/1626.svx:<o:p></o:p></p><p class=MsoPlainText style='margin-left:36.0pt'>*export p2018-ad-01<o:p></o:p></p><p class=MsoPlainText style='margin-left:36.0pt'> <o:p></o:p></p><p class=MsoPlainText style='margin-left:36.0pt'>:loser:/kataster/1626-no-schoenberg-hs.svx:<o:p></o:p></p><p class=MsoPlainText style='margin-left:36.0pt'>*export p2018-ad-01<o:p></o:p></p><p class=MsoPlainText style='margin-left:36.0pt'> <o:p></o:p></p><p class=MsoPlainText style='margin-left:36.0pt'>:loser:/gpx/2018/ additional_info.svx<o:p></o:p></p><p class=MsoPlainText style='margin-left:36.0pt'>*equate waypoints_aday-2018-07-11.2018_ad_01 1626.p2018-ad-01<o:p></o:p></p><p class=MsoPlainText style='margin-left:36.0pt'>*entrance 1626.p2018-ad-01<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><span lang=EN-US style='mso-fareast-language:EN-GB'>-----Original Message-----<br>From: Expo-tech [mailto:expo-tech-bounces@lists.wookware.org] On Behalf Of Wookey<br>Sent: 30 June 2020 13:46<br>To: expo-tech@lists.wookware.org<br>Subject: Re: [Expo-tech] glitch in p2018-ad-01 - is it 1623 or 1626 ?</span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>On 2020-06-30 13:16 +0100, Philip Sargent (Gmail) wrote:<o:p></o:p></p><p class=MsoPlainText>> cavern says:<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> …/loser/kataster/1623.svx:7: warning: Station “1623.p2018-ad-01” referred<o:p></o:p></p><p class=MsoPlainText>> to by *entrance or *export but never used<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> I according to /caves/ it is in 1623:<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> http://expo.survex.com/1623/2018-ad-01<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> and from the GPS in essentials.gpx it is probably in 1623, but overlooking<o:p></o:p></p><p class=MsoPlainText>> the Wildensee hutte so might be in 1626.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>It's 572m inside 1623 according to the dataset I just looked at. Not<o:p></o:p></p><p class=MsoPlainText>even close to being debateable. The border is in the dataset so it's<o:p></o:p></p><p class=MsoPlainText>very easy to tell which side of the line things are. Look in aven.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>> And how do we resolve this without breaking lots of things ?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Resolve the cavern warning?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Well there is no underground data for 2018-ad-01 so there is an no<o:p></o:p></p><p class=MsoPlainText>underground data connected to it. And there are two surface GPS tracks<o:p></o:p></p><p class=MsoPlainText>going there, but the entrance has been positioned in the middle of the<o:p></o:p></p><p class=MsoPlainText>'GPS wander' rather than at any specific point (which seems reasonably<o:p></o:p></p><p class=MsoPlainText>correct) so it's not connected to any actual dataset. Hence the<o:p></o:p></p><p class=MsoPlainText>warning. So nothing is 'wrong' here.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>It presumably doesn't also have a REFERENCE modifier which I think<o:p></o:p></p><p class=MsoPlainText>would supress the warning. This relates to the general treatment of<o:p></o:p></p><p class=MsoPlainText>entrance locations, which should correctly be derived from a number of<o:p></o:p></p><p class=MsoPlainText>inputs (surface surveys, bearings, multiple GPS readings, images, and<o:p></o:p></p><p class=MsoPlainText>DEMs and for altitude). Survex could do this (apart from the<o:p></o:p></p><p class=MsoPlainText>image-location - that needs to be extracted in another process), but<o:p></o:p></p><p class=MsoPlainText>currently has rather too simple a data model, resulting in warnings<o:p></o:p></p><p class=MsoPlainText>like this where someone has clearly done the averaging job<o:p></o:p></p><p class=MsoPlainText>manually/externally. We are working on a better process as part of the<o:p></o:p></p><p class=MsoPlainText>'how do we interface with GIS' discussions.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>> But so far as I can see, the GPS position is *only* in essentials.gpx and<o:p></o:p></p><p class=MsoPlainText>> not in any of the cave or entrance data. Presumably connected by a surface<o:p></o:p></p><p class=MsoPlainText>> survey to a fixed point but I haven’t deciphered that.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>It's clearly been derived from GPS tracks.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>A lot of this entrance info needs a good checking over as I'm pretty<o:p></o:p></p><p class=MsoPlainText>sure there is all sorts of nonsense in there. But more usefully we<o:p></o:p></p><p class=MsoPlainText>should work out how to enter the actual data we have such that a<o:p></o:p></p><p class=MsoPlainText>consistent location can be calculated from the available data, rather<o:p></o:p></p><p class=MsoPlainText>than arbitrarily annointing one GPS reading which is currently what<o:p></o:p></p><p class=MsoPlainText>happens a lot.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Wookey<o:p></o:p></p><p class=MsoPlainText>-- <o:p></o:p></p><p class=MsoPlainText>Principal hats: Linaro, Debian, Wookware, ARM<o:p></o:p></p><p class=MsoPlainText>http://wookware.org/<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>_______________________________________________<o:p></o:p></p><p class=MsoPlainText>Expo-tech mailing list<o:p></o:p></p><p class=MsoPlainText>Expo-tech@lists.wookware.org<o:p></o:p></p><p class=MsoPlainText>https://lists.wookware.org/cgi-bin/mailman/listinfo/expo-tech<o:p></o:p></p></div></body></html>