<?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 Extent and coordinate system in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/extent-and-coordinate-system/idi-p/921530</link>
    <description>&lt;P&gt;Geoprocessing is pretty nifty working across coordinate systems, but with raster processing there is a hassle with&amp;nbsp;extents and coordinate systems. If you define the extent from a dataset in one coordinate system and try to use it processing in another coordinate system, you reap nothing because the extent is defined in a different coordinate system than the data. The only solution is to project your extent data set before you use it.&lt;BR /&gt;&lt;BR /&gt;It would be nice to have the ability for the&amp;nbsp;gp&amp;nbsp;to smart-project extents when specifying&amp;nbsp;data sets (with a warning of course, as the results may be strange if the two coordinate systems are significantly different). (Could an inversability statistic by reported&amp;nbsp; in the error message - then you'd know whether this was a reasonable on the fly projection to use.)&lt;BR /&gt;&lt;BR /&gt;Here's an illustration of what I'm talking about:&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt; arcpy.OutputCoordinateSystem = "UTMBox"&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt;&amp;nbsp;arcpy.Extent = "e:\\work\\albersbox"&lt;BR /&gt;WARNING:&amp;nbsp;Extent was projected to match output coordinate system&lt;BR /&gt;&lt;BR /&gt;This wouldn't&amp;nbsp;be doable&amp;nbsp;for cell size or snap, as these depend on location, which you wouldn't know. But supporting on the fly extent projection would be a useful addition to this functionality.&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;!--  content transformation source ID: 08730000000872O  --&gt;</description>
    <pubDate>Thu, 16 May 2024 00:38:05 GMT</pubDate>
    <dc:creator>curtvprice</dc:creator>
    <dc:date>2024-05-16T00:38:05Z</dc:date>
    <item>
      <title>Extent and coordinate system</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/extent-and-coordinate-system/idi-p/921530</link>
      <description>&lt;P&gt;Geoprocessing is pretty nifty working across coordinate systems, but with raster processing there is a hassle with&amp;nbsp;extents and coordinate systems. If you define the extent from a dataset in one coordinate system and try to use it processing in another coordinate system, you reap nothing because the extent is defined in a different coordinate system than the data. The only solution is to project your extent data set before you use it.&lt;BR /&gt;&lt;BR /&gt;It would be nice to have the ability for the&amp;nbsp;gp&amp;nbsp;to smart-project extents when specifying&amp;nbsp;data sets (with a warning of course, as the results may be strange if the two coordinate systems are significantly different). (Could an inversability statistic by reported&amp;nbsp; in the error message - then you'd know whether this was a reasonable on the fly projection to use.)&lt;BR /&gt;&lt;BR /&gt;Here's an illustration of what I'm talking about:&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt; arcpy.OutputCoordinateSystem = "UTMBox"&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt;&amp;nbsp;arcpy.Extent = "e:\\work\\albersbox"&lt;BR /&gt;WARNING:&amp;nbsp;Extent was projected to match output coordinate system&lt;BR /&gt;&lt;BR /&gt;This wouldn't&amp;nbsp;be doable&amp;nbsp;for cell size or snap, as these depend on location, which you wouldn't know. But supporting on the fly extent projection would be a useful addition to this functionality.&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;!--  content transformation source ID: 08730000000872O  --&gt;</description>
      <pubDate>Thu, 16 May 2024 00:38:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/extent-and-coordinate-system/idi-p/921530</guid>
      <dc:creator>curtvprice</dc:creator>
      <dc:date>2024-05-16T00:38:05Z</dc:date>
    </item>
  </channel>
</rss>

