<?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 Re: Raster converted from ASCII is offset in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/raster-converted-from-ascii-is-offset/m-p/722118#M40944</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;is it just a shift? or is it a scale too? a shift would imply that the difference between reference locations would be consistent as you head east-west and north-south. A scale will have an increasing difference in those directions since the cell size specified is not correct and the 'offset' becomes greater to the east and north if the raster location is defined based on its lower left coordinate (east and south if defined by the top left).&amp;nbsp; If there is no consist variation or it just gets progressively worse, then you have&amp;nbsp; translation, rotation and scale issues and a georeferenced of the image using a simple 1st order (affine) transformation should work.&amp;nbsp; Check georeferencing images in the help files.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 20 Mar 2017 22:51:20 GMT</pubDate>
    <dc:creator>DanPatterson_Retired</dc:creator>
    <dc:date>2017-03-20T22:51:20Z</dc:date>
    <item>
      <title>Raster converted from ASCII is offset</title>
      <link>https://community.esri.com/t5/data-management-questions/raster-converted-from-ascii-is-offset/m-p/722117#M40943</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;IMG alt="Showing offset of raster (red-green scale) in northwestern direction from basemap." class="image-1 jive-image j-img-original" src="https://community.esri.com/legacyfs/online/343317_Bathy_shift.jpg" style="width: 620px; height: 802px;" /&gt;&lt;/P&gt;&lt;P&gt;Background: I received an .asc file with elevation data in southern Oregon. The horizontal datum = feet, vertical datum = MLLW. &amp;nbsp;I edited the header, and successfully used the ASCII to Raster tool.&amp;nbsp;&amp;nbsp;I used&amp;nbsp;the Define Projection tool to set projection. I tried:&amp;nbsp;&lt;/P&gt;&lt;P&gt;NAD_1983_StatePlane_Oregon_South_FIPS_3602_Feet_Intl&lt;BR /&gt; NAD_1983_StatePlane_Oregon_South_FIPS_3202_Feet_US&lt;/P&gt;&lt;P&gt;I used the Project Raster to our working projection (WGS_1984_UTM_Zone_10N).&lt;/P&gt;&lt;P&gt;**All of these steps were conducted in ArcCatalog.**&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was told by .asc provider that:&amp;nbsp;&lt;/P&gt;&lt;P&gt;"Use&amp;nbsp;Oregon state plane South survey feet (id# 3602), because grid cells will have the same spacing in the latitudinal and longitudinal direction. You should be able to use this to load into arc and then convert to another datum (lat/lon)."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Problem:&amp;nbsp;When I put it in ArcMap with a basemap in the&amp;nbsp;&lt;SPAN&gt;WGS_1984_UTM_Zone_10N, it is offset. I tried estimating the offset and using the Shift tool, but it is difficult given the permanent features in a basemap with current bathymetry topography. It seemed to indicate the offset may not be quite the same everywhere. I'm not sure though.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Any suggestions?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Mar 2017 21:26:35 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/raster-converted-from-ascii-is-offset/m-p/722117#M40943</guid>
      <dc:creator>ElizabethPerotti</dc:creator>
      <dc:date>2017-03-20T21:26:35Z</dc:date>
    </item>
    <item>
      <title>Re: Raster converted from ASCII is offset</title>
      <link>https://community.esri.com/t5/data-management-questions/raster-converted-from-ascii-is-offset/m-p/722118#M40944</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;is it just a shift? or is it a scale too? a shift would imply that the difference between reference locations would be consistent as you head east-west and north-south. A scale will have an increasing difference in those directions since the cell size specified is not correct and the 'offset' becomes greater to the east and north if the raster location is defined based on its lower left coordinate (east and south if defined by the top left).&amp;nbsp; If there is no consist variation or it just gets progressively worse, then you have&amp;nbsp; translation, rotation and scale issues and a georeferenced of the image using a simple 1st order (affine) transformation should work.&amp;nbsp; Check georeferencing images in the help files.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Mar 2017 22:51:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/raster-converted-from-ascii-is-offset/m-p/722118#M40944</guid>
      <dc:creator>DanPatterson_Retired</dc:creator>
      <dc:date>2017-03-20T22:51:20Z</dc:date>
    </item>
    <item>
      <title>Re: Raster converted from ASCII is offset</title>
      <link>https://community.esri.com/t5/data-management-questions/raster-converted-from-ascii-is-offset/m-p/722119#M40945</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are you saying that the original text file didn't have a header?&lt;/P&gt;&lt;P&gt;Where did you get the information about cell size, LL corner coords etc?&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="http://desktop.arcgis.com/en/arcmap/latest/tools/conversion-toolbox/ascii-to-raster.htm" title="http://desktop.arcgis.com/en/arcmap/latest/tools/conversion-toolbox/ascii-to-raster.htm"&gt;ASCII to Raster—Help | ArcGIS Desktop&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Mar 2017 06:12:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/raster-converted-from-ascii-is-offset/m-p/722119#M40945</guid>
      <dc:creator>NeilAyres</dc:creator>
      <dc:date>2017-03-21T06:12:48Z</dc:date>
    </item>
    <item>
      <title>Re: Raster converted from ASCII is offset</title>
      <link>https://community.esri.com/t5/data-management-questions/raster-converted-from-ascii-is-offset/m-p/722120#M40946</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Neil, the lead in question &lt;A _jive_internal="true" href="https://community.esri.com/thread/191843-ascii-to-raster-error-in-grid-expression"&gt;https://community.esri.com/thread/191843-ascii-to-raster-error-in-grid-expression&lt;/A&gt;&amp;nbsp;which I think is related.&amp;nbsp; Initial assumption would have been specifying a cell size issue, which may not be the simple case if the header information doesn't fix it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Mar 2017 08:19:38 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/raster-converted-from-ascii-is-offset/m-p/722120#M40946</guid>
      <dc:creator>DanPatterson_Retired</dc:creator>
      <dc:date>2017-03-21T08:19:38Z</dc:date>
    </item>
    <item>
      <title>Re: Raster converted from ASCII is offset</title>
      <link>https://community.esri.com/t5/data-management-questions/raster-converted-from-ascii-is-offset/m-p/722121#M40947</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In the screen shot of the linked thread, CELLSIZE = 0.0, which obviously can't be correct.&lt;/P&gt;&lt;P&gt;As the data appears to be in GCS, getting the cellsize correct would be quite tricky.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Mar 2017 06:23:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/raster-converted-from-ascii-is-offset/m-p/722121#M40947</guid>
      <dc:creator>NeilAyres</dc:creator>
      <dc:date>2017-03-22T06:23:42Z</dc:date>
    </item>
  </channel>
</rss>

