<?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>idea Incorporate Ground Control Points (GCP) during creation of Mosaic Datasets in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/incorporate-ground-control-points-gcp-during/idi-p/928386</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;In ArcGIS 10, we can do rectifcation with RPC or ortho-rectifcation with RPC &amp;amp; DEM from Raw Bundle of imagery (IKONOS, GeoEye, QuickBird, OrbView, etc). But it would be very useful to also include GCP from references or surveying data when creating a Mosaic Dataset to improve accuaracy. Or, enhance the&amp;nbsp;'Georeferencing' tool in Desktop to work with Mosaic&amp;nbsp;Datasets, in particular the "Update Georeferencing" option.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;For background on the reasons for this workflow, please see below:&lt;BR /&gt;++++++++++++++&lt;BR /&gt;&lt;BR /&gt;For engineering-grade accuracy of processed images, 2-3 pixels are allowable in shift (horizontal), corresponding to historical GIS &amp;amp; imagery references or surveying data [those references can be used to collect ground control points (GCP)].&lt;BR /&gt;&lt;BR /&gt;As we know, for example, with RPC and very-high-resolution DEM, GeoEye-1 can offer up to five-meter (10-pixel) geo-location accuracy, which means that customers can map natural and man-made features to within five meters (about sixteen feet) of their actual location on the surface of the Earth. So far, no other commercial imaging system can do this. [Of course, only using RPC without DEM, GeoEye-1 geolocation accuracy becomes poorer, even up to 10-meter (20-pixel) in shift...]&lt;BR /&gt;&lt;BR /&gt;Link to the following research for more at&amp;nbsp; &lt;A href="http://mcgsc.usgs.gov/publications/Kaintuck_vaughn_.pdf" target="_blank"&gt;http://mcgsc.usgs.gov/publications/Kaintuck_vaughn_.pdf &lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;So, without GCP's integration during rectification or ortho-rectification, the spatial accuracies of finally-processed Mosaic Datasets are usually not enough to meet the basic requirements for some GIS applications requring accurate imagery.

&lt;!-- content transformation source ID: 08730000000boIp --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 21 Jun 2011 10:30:19 GMT</pubDate>
    <dc:creator>larryzhang</dc:creator>
    <dc:date>2011-06-21T10:30:19Z</dc:date>
    <item>
      <title>Incorporate Ground Control Points (GCP) during creation of Mosaic Datasets</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/incorporate-ground-control-points-gcp-during/idi-p/928386</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;In ArcGIS 10, we can do rectifcation with RPC or ortho-rectifcation with RPC &amp;amp; DEM from Raw Bundle of imagery (IKONOS, GeoEye, QuickBird, OrbView, etc). But it would be very useful to also include GCP from references or surveying data when creating a Mosaic Dataset to improve accuaracy. Or, enhance the&amp;nbsp;'Georeferencing' tool in Desktop to work with Mosaic&amp;nbsp;Datasets, in particular the "Update Georeferencing" option.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;For background on the reasons for this workflow, please see below:&lt;BR /&gt;++++++++++++++&lt;BR /&gt;&lt;BR /&gt;For engineering-grade accuracy of processed images, 2-3 pixels are allowable in shift (horizontal), corresponding to historical GIS &amp;amp; imagery references or surveying data [those references can be used to collect ground control points (GCP)].&lt;BR /&gt;&lt;BR /&gt;As we know, for example, with RPC and very-high-resolution DEM, GeoEye-1 can offer up to five-meter (10-pixel) geo-location accuracy, which means that customers can map natural and man-made features to within five meters (about sixteen feet) of their actual location on the surface of the Earth. So far, no other commercial imaging system can do this. [Of course, only using RPC without DEM, GeoEye-1 geolocation accuracy becomes poorer, even up to 10-meter (20-pixel) in shift...]&lt;BR /&gt;&lt;BR /&gt;Link to the following research for more at&amp;nbsp; &lt;A href="http://mcgsc.usgs.gov/publications/Kaintuck_vaughn_.pdf" target="_blank"&gt;http://mcgsc.usgs.gov/publications/Kaintuck_vaughn_.pdf &lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;So, without GCP's integration during rectification or ortho-rectification, the spatial accuracies of finally-processed Mosaic Datasets are usually not enough to meet the basic requirements for some GIS applications requring accurate imagery.

&lt;!-- content transformation source ID: 08730000000boIp --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jun 2011 10:30:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/incorporate-ground-control-points-gcp-during/idi-p/928386</guid>
      <dc:creator>larryzhang</dc:creator>
      <dc:date>2011-06-21T10:30:19Z</dc:date>
    </item>
    <item>
      <title>Re: Incorporate Ground Control Points (GCP) during creation of Mosaic Datasets</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/incorporate-ground-control-points-gcp-during/idc-p/928387#M2137</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN style="color: rgb(31, 73, 125); font-size: 11pt;"&gt;This idea is of interest to the PUG (&lt;A href="http://www.pugonline.org/" target="_blank"&gt;&lt;FONT color="#0000ff"&gt;http://www.pugonline.org/&lt;/FONT&gt;&lt;/A&gt; ) and applies to raster format data.&lt;/SPAN&gt;

&lt;!-- content transformation source ID: 00aE00000029Ts2 --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Mar 2013 23:42:38 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/incorporate-ground-control-points-gcp-during/idc-p/928387#M2137</guid>
      <dc:creator>DeanSitzman</dc:creator>
      <dc:date>2013-03-29T23:42:38Z</dc:date>
    </item>
    <item>
      <title>Re: Incorporate Ground Control Points (GCP) during creation of Mosaic Datasets</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/incorporate-ground-control-points-gcp-during/idc-p/928388#M2138</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;From Esri: This will be partially resolved in the 10.2 release. You can use georeferencing tool with Mosaic dataset and utilize X,Y control. This can be used to improve the accuracy. The georeferencing tools provide ability to determine RMS of different transform to be applied.&lt;BR /&gt;&lt;BR /&gt;ArcGIS Ideas Moderator

&lt;!-- content transformation source ID: 00aE0000002zXT1 --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Jun 2013 22:05:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/incorporate-ground-control-points-gcp-during/idc-p/928388#M2138</guid>
      <dc:creator>MichaelHogan</dc:creator>
      <dc:date>2013-06-14T22:05:45Z</dc:date>
    </item>
    <item>
      <title>Re: Incorporate Ground Control Points (GCP) during creation of Mosaic Datasets</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/incorporate-ground-control-points-gcp-during/idc-p/928389#M2139</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;This would be incredibly useful as a Function Chain.&amp;nbsp; You can capture the GCP points or already have&amp;nbsp;a GCP file.&amp;nbsp; The result can be that you decide which transformation function you would apply (first/second/third order, etc.)&amp;nbsp; You can apply those changes at any time.&amp;nbsp; This give flexibility to the end-user.&lt;BR /&gt;&lt;BR /&gt;Has anyone used this in&amp;nbsp;10.2 and determined whether this is available and can be applied to the image when you add it to&amp;nbsp;a Mosaic Dataset without permanently rectifying the image?

&lt;!-- content transformation source ID: 00aE0000004LtVS --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Nov 2013 09:21:24 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/incorporate-ground-control-points-gcp-during/idc-p/928389#M2139</guid>
      <dc:creator>JonettaNg</dc:creator>
      <dc:date>2013-11-18T09:21:24Z</dc:date>
    </item>
    <item>
      <title>Re: Incorporate Ground Control Points (GCP) during creation of Mosaic Datasets</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/incorporate-ground-control-points-gcp-during/idc-p/928390#M2140</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV id="cke_pastebin" style="width: 1px; height: 1px;"&gt;
	&amp;nbsp;&lt;/DIV&gt;
&lt;SPAN style=""&gt;&amp;nbsp;&lt;/SPAN&gt;Pug Idea List 2014:&amp;nbsp; Kteve Kopp, ESRI Lead
&lt;TABLE border="0" cellpadding="0" cellspacing="0" style="width: 308pt;" width="411"&gt;&lt;COLGROUP&gt;&lt;COL style="width: 308pt;" width="411" /&gt;&lt;/COLGROUP&gt;&lt;TBODY&gt;&lt;TR height="68" style="height: 51pt;"&gt;&lt;TD colspan="1" rowspan="1" class="xl67" height="68" style="width: 308pt; height: 51pt; background-color: transparent;" width="411"&gt;
				&lt;FONT face="Calibri"&gt;Need to clarify expectations. We think this is for block adjustment to approve accuracy in ground control, not sure if this is going to be possible.&lt;SPAN style=""&gt;&amp;nbsp; &lt;/SPAN&gt;&lt;FONT color="#000000" size="3"&gt;GCP might be added soon to mosaics.&lt;SPAN style=""&gt;&amp;nbsp; &lt;/SPAN&gt;Need additional information from the Raster team.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;

&lt;!-- content transformation source ID: 00aE0000006EsKu --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Apr 2014 14:32:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/incorporate-ground-control-points-gcp-during/idc-p/928390#M2140</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2014-04-11T14:32:56Z</dc:date>
    </item>
  </channel>
</rss>

