Latest Contributions by BojanŠavrič

Hi @MelanieWawryk, I have some exciting news to share! In ArcGIS Pro 3.6, we've implemented new transformations that support conversions between NAD83 (CSRS) versions 2 through 8 using the NTv2 velocity grid file—specifically, the latest version: NAD83v80VG.gsb (see Canadian Geodetic Survey's website for details). Although the NTv2 velocity grid supports conversions at different data epochs, Esri only supports conversions at the anchor epochs of the realizations only. NAD83 (CSRS) realizations and their anchor epoch date: Datum Name WKID    Anchor Epoch Date NAD83 (CSRS) version 2 1193 1997.0 NAD83 (CSRS) version 3 1194 1997.0 NAD83 (CSRS) version 4 1195 2002.0 NAD83 (CSRS) version 6 1197 2010.0 NAD83 (CSRS) version 7 1198 2010.0 NAD83 (CSRS) version 8 1365 2010.0   New geographic transformations in ArcGIS Pro 3.6: Geographic (datum) Transformation Name  WKID NAD83(CSRS)v2_to_NAD83(CSRS)v4_5 10708 NAD83(CSRS)v2_to_NAD83(CSRS)v6_4 10709 NAD83(CSRS)v2_to_NAD83(CSRS)v7_3 10710 NAD83(CSRS)v2_to_NAD83(CSRS)v8_3 10711 NAD83(CSRS)v3_to_NAD83(CSRS)v4_4 10712 NAD83(CSRS)v3_to_NAD83(CSRS)v6_4 10713 NAD83(CSRS)v3_to_NAD83(CSRS)v7_3 10714 NAD83(CSRS)v3_to_NAD83(CSRS)v8_3 10715 NAD83(CSRS)v4_to_NAD83(CSRS)v6_4 10716 NAD83(CSRS)v4_to_NAD83(CSRS)v7_3 10717 NAD83(CSRS)v4_to_NAD83(CSRS)v8_3 10718   ArcGIS Pro 3.6 is currently in Beta and available for testing through the Early Adopter Community. You can sign up using this EAC sign-up form. Since these transformations rely on on-disk grid files, you'll need to install the ArcGIS Pro Coordinate System Data, which is also available on the EAC website. Thank you, Bojan ... View more

Hi @SisselS, Thank you for your suggestion. ArcGIS Pro’s on-the-fly transformation capability is designed to provide users with quick and appropriate datum transformations without requiring deep knowledge of the underlying methods or which transformations apply to specific geographic areas. ArcGIS Pro assumes that the transformation path listed at the top is the most likely appropriate choice. Allowing users to override defined extents would expose them to an overwhelming number of transformation options—potentially several hundred in some cases—and make it easy to apply an incorrect transformation path to the dataset. Since many users are not familiar with the details of datum transformations, this poses a significant risk and increases the likelihood of incorrect choices that could corrupt or invalidate their data. That said, we recognize that there are specific scenarios where bypassing extent checks may be necessary—for example, when repairing corrupted datasets, working with outdated coordinate reference systems (CRS), or correcting previously misapplied CRS and transformations. For these cases, we offer a more controlled and permanent solution that GIS administrators and data managers can use to bypass extent restrictions and fix their data appropriately. The Project tool in ArcGIS Pro allows users to manually define custom transformation paths. The tool only verifies that the transformation sequence correctly passes through all required geographic coordinate systems but does not enforce area-of-use constraints. For instance, in the example provided bellow—transforming Austrian data from ED50 to WGS84 (via a Norwegian transformation), and then to Belge 72 (via a Belgian transformation)—the Project tool successfully applies the specified transformations. Please note that this approach only works with mathematical transformation methods, such as position vector or coordinate frame (7-parameter) transformations. Transformations that rely on grid-based methods, like NTv2, will not transform coordinates outside the used transformation grids. If you believe the validity of the mentioned transformations or geographic coordinate systems should extend beyond what EPSG currently specifies, please reach out to EPSG (https://epsg.org/dataset-change-requests.html) and request a correction. Thank you, Bojan ... View more

Hi @COSPNWGuy  Thank you for reaching out and for your question. For now, I am keeping this blog up-to-date with current information.  In the past month, NGS moved some of their products to Beta release. You can check them out on this link: https://beta.ngs.noaa.gov/. To get the latest news on NSRS modernization and track NGS's progress, I would highly recommend you subscribe to NGS News or visit their "New Datums" web pages. My team also had a professional development session with NGS at FedGIS conference past February. You might be able to download our slide from this link: https://registration.esri.com/flow/esri/25fedgis/eventportal/page/detailed-agenda/session/1730232984656001zUCp Regards, Bojan ... View more

Hi @Craig_Eissler_Iceman, According to the NOAA's National Geodetic Survey website regarding the current GEOID18 model, it appears that geoid heights are all negative for CONUS. This would indicate that the current geoid model for NAVD88 is consistently below the GRS80 ellipsoid for NAD83 (2011). I hope this helps, Bojan   ... View more

@RyanDillingham @BenPearse  Great news! You can now create your own custom vertical transformations using local geoid models in ArcGIS Pro. The Create Custom Vertical Transformation tool, introduced in ArcGIS Pro 3.2, is available in the Data Management toolbox. At that time, my colleague published a blog post titled How to Create and Use a Custom Vertical Transformation in ArcGIS Pro, which also explains the required file format for custom geoid models and where to place them to enable these transformations. Since 2021, we have also expanded support for geoid models to include additional countries for which we were able to obtain the necessary data and definitions. Below is a map of the countries currently supported in ArcGIS Pro 3.4. Please note that to use these geoid models, you must install the ArcGIS Coordinate Systems Data component along with ArcGIS Pro. I hope this helps, Bojan     ... View more

Hi @MelanieWawryk! Here are updated links. NAD83(CSRS)v3 to NAD83(CSRS)v6 (3) NAD83(CSRS)v3 to NAD83(CSRS)v7 (2) ... View more

Hi @Wojciech87, Thank you for reaching out and for your question. Yes, Esri will support the dynamic datums to be released with NSRS 2022. Implementation of these functionalities will be complex and may lag a little behind the NSRS 2022 rollout. We are closely following this development. Regards, Bojan ... View more

@COSPNWGuy  Unfortunately, there is nothing planned for this year's UC (2024). We hope to have something specific planned for next Esri UC 2025. We will mention upcoming changes during our technical workshop about coordinate systems and transformations. Look for What You Need to Know About Coordinate Systems and Transformations session on Tuesday, Jul 16, at 1PM in Room 10 (SDCC). Meanwhile, if you want to talk about NSRS 2022 in detail, you are very much welcome to stop by the Coordinate Systems kiosk at ArcGIS Pro area in Esri Showcase. There may also be someone from the National Geodetic Survey at the NOAA kiosk at the Federal Agency area in Esri Showcase. ... View more

I set my map to Web Mercator (3857) PCS and then I used Go To XY tool and I input your projected coordinates above, by changing units to meters: By setting units to decimal degrees, I get the same point with geographic coordinates above: ... View more

@SatyaraySingh  Convergence angle is a difference between between True North and Grid North, and its value depends on a map projection used in a grid. If you use WGS 1984, technically this is not a projected coordinate system, but a geographic coordinate system, so your "grid" north with always be True North, and convergence angle is always 0. The same results would be in WGS 1984 Web Mercator, because the Mercator projection displays straight meridians and Grid North will always be aligned with True North. This would be the case with any cylindrical projection in normal aspect.  With other projected coordinate systems, like UTM or State Plane CRS, True and Grid North might be different, so convergence angle will not always be 0 (depending on the location). I hope this explains it. ... View more

@MichaelDavis3  GetConvergenceAngle method does not calculate magnetic declination but provides a difference between True North (calculated in GCS) and Grid North (calculated in PCS). The math relies purely on projection’s mathematics, and it does not require a dataset. ... View more

Hi @nexusiceland, Using custom projected coordinate system and aligning it with existing definition depends on the custom definition. Does you definition also have a custom geographic coordinate system? If it does, you have to first use the Create Custom Geographic Transformation tool to define a transformation that will align your custom geographic coordinate system with existing definition. After that, you can use Project tool to convert your data to your custom definition, by selecting it as an output coordinate system. Make sure you also select an appropriate transformation path in the tool, using previously defined custom geographic transformation.  ... View more