<?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 Projection Files for Microstation with Offset Global Origin in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/projection-files-for-microstation-with-offset/m-p/1333081#M73539</link>
    <description>&lt;P&gt;We have been using a standard Nad 83 Zone 17N projection file to attach Microstation files for the last few years, despite having an offset Global Origin in the .DGN file.&amp;nbsp; After our upgrade to ArcGIS Pro 3.1, that file no longer functions as it has for the last few years and is now moving our data to an incorrect location.&amp;nbsp; I've modified the file with a False Easting and Northing to accommodate our Global Origin and this works fine.&lt;/P&gt;&lt;P&gt;My question is, was this feature NOT working properly for the last few years and ArcPro 3.1 "corrected" the issue?&amp;nbsp; Or has the functionality been broken and will this new behaviour be corrected?&amp;nbsp; It doesn't matter either way, we have a methodology to make it work, but before I roll out a new standard Projection file I'd like to know if that's wasted effort and added confusion.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Wed, 27 Sep 2023 19:39:40 GMT</pubDate>
    <dc:creator>Scott_T_Anderson</dc:creator>
    <dc:date>2023-09-27T19:39:40Z</dc:date>
    <item>
      <title>Projection Files for Microstation with Offset Global Origin</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/projection-files-for-microstation-with-offset/m-p/1333081#M73539</link>
      <description>&lt;P&gt;We have been using a standard Nad 83 Zone 17N projection file to attach Microstation files for the last few years, despite having an offset Global Origin in the .DGN file.&amp;nbsp; After our upgrade to ArcGIS Pro 3.1, that file no longer functions as it has for the last few years and is now moving our data to an incorrect location.&amp;nbsp; I've modified the file with a False Easting and Northing to accommodate our Global Origin and this works fine.&lt;/P&gt;&lt;P&gt;My question is, was this feature NOT working properly for the last few years and ArcPro 3.1 "corrected" the issue?&amp;nbsp; Or has the functionality been broken and will this new behaviour be corrected?&amp;nbsp; It doesn't matter either way, we have a methodology to make it work, but before I roll out a new standard Projection file I'd like to know if that's wasted effort and added confusion.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 27 Sep 2023 19:39:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/projection-files-for-microstation-with-offset/m-p/1333081#M73539</guid>
      <dc:creator>Scott_T_Anderson</dc:creator>
      <dc:date>2023-09-27T19:39:40Z</dc:date>
    </item>
  </channel>
</rss>

