<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Postprocessed differential correction in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/postprocessed-differential-correction/m-p/403408#M23160</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;Last summer during our fieldwork in Africa our team collected a lot of GNSS measurements &lt;SPAN style="text-align: justify; background-color: #f6f6f6;"&gt;(format: .axf or .shp files, each with associated .ssf file) &lt;/SPAN&gt;using ArcPad software installed on hand-held Trimbles (GeoExplorer 6000). Because we were working in a very remote area, we planned a postprocessed differential correction using data from a base station nearby. At the end of the campaign it turned out that the base station had unfortunately not been working properly, resulting in only a few days of base data being available. &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px; text-align: justify;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;Within the Trimble GPS Analyst extension for ArcGIS I successfully used the available base data to correct our GNSS measurements for these limited number of days. Particularly for the elevation these corrections make an important difference. &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px; text-align: justify;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;SPAN style="background: #f6f6f6;"&gt;This, however, this still leaves me with a lot of uncorrected GNSS measurements which I would also like to correct (or at least get an idea of the vertical error). I tried downloading data from a different base station (located further away) available on &lt;A class="jive-link-external-small" href="http://www.unavco.org/" rel="nofollow" target="_blank"&gt;http://www.unavco.org/&lt;/A&gt;, but the Trimble GPS Analyst extension is somehow not able to execute the corrections. After going through the whole differential correction procedure I get the end message: “&lt;/SPAN&gt;100% total coverage; Selected 4827 positions for post-processing; Corrected 0 positions; Failed to correct 4827 positions” (no specific error type is mentioned).&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px; margin-bottom: 0.0001pt; text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt;"&gt; &lt;/SPAN&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;A colleague suggested trying the differential corrections in Leica GeoOffice instead, but a conversion from .axf/.shp and .ssf files to a format compatible with the Leica software does not seem straightforward as I have not yet been able to find a conversion tool.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px; text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt; &lt;/SPAN&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;The only remaining option to somehow get a coarse estimate of the error of the currently uncorrected measurements would then probably be to develop some sort of algorithm.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px; text-align: justify;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;I was therefore wondering &lt;/SPAN&gt;&lt;/P&gt;&lt;UL style="list-style-type: disc; text-align: justify;"&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;how I could find out why the differential correction with the unavco data is not working.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;how I can convert .axf/.shp and .ssf files to a format compatible with the Leica software.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;if anyone hase experience with developing such algorithms and how I would best proceed with this. &lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;All suggestions are welcome! Thank you in advance!&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 23 Feb 2015 13:30:08 GMT</pubDate>
    <dc:creator>avan_baelen</dc:creator>
    <dc:date>2015-02-23T13:30:08Z</dc:date>
    <item>
      <title>Postprocessed differential correction</title>
      <link>https://community.esri.com/t5/data-management-questions/postprocessed-differential-correction/m-p/403408#M23160</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;Last summer during our fieldwork in Africa our team collected a lot of GNSS measurements &lt;SPAN style="text-align: justify; background-color: #f6f6f6;"&gt;(format: .axf or .shp files, each with associated .ssf file) &lt;/SPAN&gt;using ArcPad software installed on hand-held Trimbles (GeoExplorer 6000). Because we were working in a very remote area, we planned a postprocessed differential correction using data from a base station nearby. At the end of the campaign it turned out that the base station had unfortunately not been working properly, resulting in only a few days of base data being available. &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px; text-align: justify;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;Within the Trimble GPS Analyst extension for ArcGIS I successfully used the available base data to correct our GNSS measurements for these limited number of days. Particularly for the elevation these corrections make an important difference. &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px; text-align: justify;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;SPAN style="background: #f6f6f6;"&gt;This, however, this still leaves me with a lot of uncorrected GNSS measurements which I would also like to correct (or at least get an idea of the vertical error). I tried downloading data from a different base station (located further away) available on &lt;A class="jive-link-external-small" href="http://www.unavco.org/" rel="nofollow" target="_blank"&gt;http://www.unavco.org/&lt;/A&gt;, but the Trimble GPS Analyst extension is somehow not able to execute the corrections. After going through the whole differential correction procedure I get the end message: “&lt;/SPAN&gt;100% total coverage; Selected 4827 positions for post-processing; Corrected 0 positions; Failed to correct 4827 positions” (no specific error type is mentioned).&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px; margin-bottom: 0.0001pt; text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt;"&gt; &lt;/SPAN&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;A colleague suggested trying the differential corrections in Leica GeoOffice instead, but a conversion from .axf/.shp and .ssf files to a format compatible with the Leica software does not seem straightforward as I have not yet been able to find a conversion tool.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px; text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt; &lt;/SPAN&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;The only remaining option to somehow get a coarse estimate of the error of the currently uncorrected measurements would then probably be to develop some sort of algorithm.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px; text-align: justify;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;I was therefore wondering &lt;/SPAN&gt;&lt;/P&gt;&lt;UL style="list-style-type: disc; text-align: justify;"&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;how I could find out why the differential correction with the unavco data is not working.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;how I can convert .axf/.shp and .ssf files to a format compatible with the Leica software.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;if anyone hase experience with developing such algorithms and how I would best proceed with this. &lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="text-align: justify;"&gt;&lt;SPAN style="font-size: 10pt; background: #f6f6f6;"&gt;All suggestions are welcome! Thank you in advance!&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Feb 2015 13:30:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/postprocessed-differential-correction/m-p/403408#M23160</guid>
      <dc:creator>avan_baelen</dc:creator>
      <dc:date>2015-02-23T13:30:08Z</dc:date>
    </item>
  </channel>
</rss>

