<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Java·Applied·Geodesy·3D - Import Deflections of vertrical Value</title>
<link>https://software.applied-geodesy.org/forum/</link>
<description>Support forum for JAG3D software package</description>
<language>en</language>
<item>
<title>Import Deflections of vertrical Value (reply)</title>
<content:encoded><![CDATA[<p>Hi Amedeo,</p>
<p>thank you for your reply!</p>
<blockquote><p>I thank you for your infinite availability and courtesy.</p>
</blockquote><p>
No problem, you are welcome.</p>
<p>/Micha</p>
]]></content:encoded>
<link>https://software.applied-geodesy.org/forum/index.php?id=1678</link>
<guid>https://software.applied-geodesy.org/forum/index.php?id=1678</guid>
<pubDate>Wed, 15 Jan 2020 20:59:20 +0000</pubDate>
<dc:creator>Micha</dc:creator>
</item>
<item>
<title>Import Deflections of vertrical Value (reply)</title>
<content:encoded><![CDATA[<p>Hi Micha,<br />
I understand your reasoning and I share it.<br />
In my case, since the input values ​​to the program must still pass from a spreadsheet, I can convert them directly from that.<br />
I promise to post a complete project that has just been completed, since from an initial analysis of the values, the incidence of the vertical deflection is not so clear.. to me.<br />
I thank you for your infinite availability and courtesy.<br />
Amedeo</p>
]]></content:encoded>
<link>https://software.applied-geodesy.org/forum/index.php?id=1677</link>
<guid>https://software.applied-geodesy.org/forum/index.php?id=1677</guid>
<pubDate>Wed, 15 Jan 2020 20:47:58 +0000</pubDate>
<dc:creator>Amedeo_</dc:creator>
</item>
<item>
<title>Import Deflections of vertrical Value (reply)</title>
<content:encoded><![CDATA[<p>Hello Amedeo,</p>
<blockquote><p>I tested the &quot;v20200114&quot; version and it works</p>
</blockquote><p>Fine!</p>
<blockquote><p>The deviation input values ​​are expected in the program in mgon, but &quot;column-based import&quot; sees them as Gon. Can you modify it?</p>
</blockquote><p>Of course but then, we have some kind of inconsistencies. For angles and lengths, there are three methods to format the value. The first one is related to residuals, the second one to the uncertainties and the last one to the &quot;normal&quot; values (e.g. the observed values), cf. the <a href="https://github.com/loesler/applied-geodesy/blob/master/JAG3D/src/org/applied_geodesy/util/FormatterOptions.java#L216">sources</a>.</p>
<p>Now, let us take a look to the <a href="https://github.com/loesler/applied-geodesy/blob/master/JAG3D/src/org/applied_geodesy/jag3d/ui/io/CSVObservationFileReader.java#L223">CSV import of observations</a>. The &quot;value&quot; as well as the &quot;uncertainty&quot; uses the same converting method, i.e., <code>convertAngleToModel(value)</code> or <code>convertLengthToModel(value)</code> but not <code>convertAngleUncertaintyToModel(value)</code> or <code>convertLengthUncertaintyToModel(value)</code>. A similar situation is given in <a href="https://github.com/loesler/applied-geodesy/blob/master/JAG3D/src/org/applied_geodesy/jag3d/ui/io/CSVPointFileReader.java#L237">CSV import of points</a>. Always the &quot;normal value&quot;-option is used - to be backward compatible to former versions of JAG3D. <br />
 <br />
There is a small work-around: Before starting the import process, just change the unit of <em>angle measurement</em> to <code>mgon</code> (or your desired unit):</p>
<p><img src="https://i.ibb.co/Nt0qF1X/jag3d-formatter.png" alt="[image]"  /></p>
<p>Import your CSV file. Now, the imported values are interpreted as <code>mgon</code> (or the selected unit). Change it back after import...</p>
<p><br />
Kind regards<br />
Micha</p>
]]></content:encoded>
<link>https://software.applied-geodesy.org/forum/index.php?id=1674</link>
<guid>https://software.applied-geodesy.org/forum/index.php?id=1674</guid>
<pubDate>Wed, 15 Jan 2020 20:00:00 +0000</pubDate>
<dc:creator>Micha</dc:creator>
</item>
<item>
<title>Import Deflections of vertrical Value (reply)</title>
<content:encoded><![CDATA[<p>Hi Micha,<br />
I tested the &quot;v20200114&quot; version and it works, but I suggest some changes:<br />
The deviation input values ​​are expected in the program in mgon, but &quot;column-based import&quot; sees them as Gon.<br />
Can you modify it?<br />
Amedeo</p>
]]></content:encoded>
<link>https://software.applied-geodesy.org/forum/index.php?id=1670</link>
<guid>https://software.applied-geodesy.org/forum/index.php?id=1670</guid>
<pubDate>Wed, 15 Jan 2020 16:42:50 +0000</pubDate>
<dc:creator>Amedeo_</dc:creator>
</item>
<item>
<title>Import Deflections of vertrical Value (reply)</title>
<content:encoded><![CDATA[<p>Micha,<br />
....too fast!!!!<br />
I test.<br />
Thank you<br />
Amedeo</p>
]]></content:encoded>
<link>https://software.applied-geodesy.org/forum/index.php?id=1659</link>
<guid>https://software.applied-geodesy.org/forum/index.php?id=1659</guid>
<pubDate>Tue, 14 Jan 2020 16:36:31 +0000</pubDate>
<dc:creator>AMEDEO</dc:creator>
</item>
</channel>
</rss>
