Latest Contributions by MelitaKennedy

Chuck wrote: Is the flat imagery, treated with any particular projection?  No. Some tools/functions now know to handle distances and areas differently if the coordinate system is a geographic one. If the data's using a projected coordinate system, the tools/functions normally do 2D/planar calculations. Web Mercator is projected, but online apps / web maps will usually not do planar distance calculations because there's so much distortion in a Mercator map projection. ... View more

Chuck, If it's in WGS84, and not Web Mercator (EPSG:3857), it's being treated as if it's flat. Depending on the application you're using to interact with it, you will usually get distances and areas calculated based on the curved surface, not the flat image. Is that what you were asking? Melita ... View more

Chuck,  There are two types of vertical data. The first is ellipsoidal heights (or depths) which are relative to the geographic coordinate system / datum's surface. So, latitude-longitude-h. If you project the data you now have easting-northing-h where the h (z) values are still relative to the ellipsoid surface. They're not relative to the projection planar surface.  The second type are heights/depths relative to a gravity-related surface. US examples are NGVD29 and NAVD88. These are only loosely tied to the horizontal datum (NAD27/NAD83/etc.). For instance, z values relative to NAVD88 could use NAD27 or NAD83 as the geodetic datum/coordinate system. NGVD29 is a leveling datum. Someone set a zero location on a coast somewhere based on local mean sea level and then calculated the relative heights everywhere else in the country. Newer vertical datums use gravity measurements, GPS, other surveying techniques. Melita ... View more

Christa Vinnemann‌ Projection-on-the-fly for vector data uses the same functions and settings as the Project tool. For rasters, they use zoom-level / map scale to adjust the on-the-fly projection. If you change the map scale or zoom level, the algorithm will adjust.  S. R.‌ What coordinate system if the map using? You can try other DHDN / ETRS89 transformations. Try #3 which is used in your area of use. Melita ... View more

In ArcMap, "clear" the coordinate system. Data frame properties, Coordinate System tab. Click the globe icon (next to the star icon) and select Clear. That sets the map to "unknown coordinate system." This is not possible in ArcGIS Pro. If you instead want to turn off any geographic/datum transformations, you can set a transformation to "None" in ArcMap. Not working in ArcGIS Pro 2.2, but should work in ArcGIS Pro 2.3. Melita ... View more

Definitely, once there's data within a feature class or feature dataset, you can't (or shouldn't) change the coordinate system. The xy/z/m extents (domain), tolerances, and resolution (how the data is stored internally) are all affected by the coordinate system. Because of that, if you want to change the coordinate system with existing data, the data should be reprojected or reloaded to get converted properly.  Melita ... View more

Hi Mark,  Yes, servers would need the NTv2 files. Because ArcSDE/Server doesn't use the same "coordinate systems folders" structure, you would likely have to use a more complicated workflow to add new coordinate systems and transformations. The Esri projection engine has a way to define new objects via text files. You define an environment variable that points at the folder of text files. Please send me an email and I'll send you some documentation about it. Melita ... View more

NGS is planning to release transformations to the new frames. If I understand correctly, there will be a beta (alpha?) this year with limited availability so people, particularly industry, can prepare. Melita ... View more

I am a bit suspicious because when I convert the "other converter's" values to decimal degrees I get: 21.0949 55.9678 I suspect there is a difference in precision in the two conversions. Can you post a link to the other converter? Melita ... View more

Yes, you should install either the per-machine/all users (has a generic name) or the specifically named ArcGIS Coordinate Systems Data Per-User setup.  The core setup contains these files: (there's a gdal folder but those files are used with rasters and aren't part of the "projection engine") ./geoid: -rw-r--r-- 1 melita 1049089 2082065 Jul 30 17:13 WGS84.img ./harn: -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 alhpgn.las -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 alhpgn.los -rw-r--r-- 1 melita 1049089 2376 Jul 30 17:13 arhpgn.las -rw-r--r-- 1 melita 1049089 2376 Jul 30 17:13 arhpgn.los -rw-r--r-- 1 melita 1049089 4624 Jul 30 17:13 azhpgn.las -rw-r--r-- 1 melita 1049089 4624 Jul 30 17:13 azhpgn.los -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 c1hpgn.las -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 c1hpgn.los -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 c2hpgn.las -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 c2hpgn.los -rw-r--r-- 1 melita 1049089 5520 Jul 30 17:13 cnhpgn.las -rw-r--r-- 1 melita 1049089 5520 Jul 30 17:13 cnhpgn.los -rw-r--r-- 1 melita 1049089 3952 Jul 30 17:13 cohpgn.las -rw-r--r-- 1 melita 1049089 3952 Jul 30 17:13 cohpgn.los -rw-r--r-- 1 melita 1049089 3344 Jul 30 17:13 cshpgn.las -rw-r--r-- 1 melita 1049089 3344 Jul 30 17:13 cshpgn.los -rw-r--r-- 1 melita 1049089 6384 Jul 30 17:13 emhpgn.las -rw-r--r-- 1 melita 1049089 6384 Jul 30 17:13 emhpgn.los -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 eshpgn.las -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 eshpgn.los -rw-r--r-- 1 melita 1049089 8568 Jul 30 17:13 ethpgn.las -rw-r--r-- 1 melita 1049089 8568 Jul 30 17:13 ethpgn.los -rw-r--r-- 1 melita 1049089 4624 Jul 30 17:13 flhpgn.las -rw-r--r-- 1 melita 1049089 4624 Jul 30 17:13 flhpgn.los -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 gahpgn.las -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 gahpgn.los -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 guhpgn.las -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 guhpgn.los -rw-r--r-- 1 melita 1049089 3536 Jul 30 17:13 hihpgn.las -rw-r--r-- 1 melita 1049089 3536 Jul 30 17:13 hihpgn.los -rw-r--r-- 1 melita 1049089 2736 Jul 30 17:13 iahpgn.las -rw-r--r-- 1 melita 1049089 2736 Jul 30 17:13 iahpgn.los -rw-r--r-- 1 melita 1049089 3600 Jul 30 17:13 ilhpgn.las -rw-r--r-- 1 melita 1049089 3600 Jul 30 17:13 ilhpgn.los -rw-r--r-- 1 melita 1049089 9424 Jul 30 17:13 imhpgn.las -rw-r--r-- 1 melita 1049089 9424 Jul 30 17:13 imhpgn.los -rw-r--r-- 1 melita 1049089 5184 Jul 30 17:13 inhpgn.las -rw-r--r-- 1 melita 1049089 5184 Jul 30 17:13 inhpgn.los -rw-r--r-- 1 melita 1049089 3344 Jul 30 17:13 kshpgn.las -rw-r--r-- 1 melita 1049089 3344 Jul 30 17:13 kshpgn.los -rw-r--r-- 1 melita 1049089 2736 Jul 30 17:13 kyhpgn.las -rw-r--r-- 1 melita 1049089 2736 Jul 30 17:13 kyhpgn.los -rw-r--r-- 1 melita 1049089 3600 Jul 30 17:13 lahpgn.las -rw-r--r-- 1 melita 1049089 3600 Jul 30 17:13 lahpgn.los -rw-r--r-- 1 melita 1049089 1872 Jul 30 17:13 mdhpgn.las -rw-r--r-- 1 melita 1049089 1872 Jul 30 17:13 mdhpgn.los -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 mehpgn.las -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 mehpgn.los -rw-r--r-- 1 melita 1049089 4560 Jul 30 17:13 mihpgn.las -rw-r--r-- 1 melita 1049089 4560 Jul 30 17:13 mihpgn.los -rw-r--r-- 1 melita 1049089 5040 Jul 30 17:13 mnhpgn.las -rw-r--r-- 1 melita 1049089 5040 Jul 30 17:13 mnhpgn.los -rw-r--r-- 1 melita 1049089 4560 Jul 30 17:13 mohpgn.las -rw-r--r-- 1 melita 1049089 4560 Jul 30 17:13 mohpgn.los -rw-r--r-- 1 melita 1049089 3120 Jul 30 17:13 mshpgn.las -rw-r--r-- 1 melita 1049089 3120 Jul 30 17:13 mshpgn.los -rw-r--r-- 1 melita 1049089 3024 Jul 30 17:13 nbhpgn.las -rw-r--r-- 1 melita 1049089 3024 Jul 30 17:13 nbhpgn.los -rw-r--r-- 1 melita 1049089 3696 Jul 30 17:13 nchpgn.las -rw-r--r-- 1 melita 1049089 3696 Jul 30 17:13 nchpgn.los -rw-r--r-- 1 melita 1049089 3696 Jul 30 17:13 ndhpgn.las -rw-r--r-- 1 melita 1049089 3696 Jul 30 17:13 ndhpgn.los -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 nehpgn.las -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 nehpgn.los -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 njhpgn.las -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 njhpgn.los -rw-r--r-- 1 melita 1049089 4560 Jul 30 17:13 nmhpgn.las -rw-r--r-- 1 melita 1049089 4560 Jul 30 17:13 nmhpgn.los -rw-r--r-- 1 melita 1049089 4080 Jul 30 17:13 nvhpgn.las -rw-r--r-- 1 melita 1049089 4080 Jul 30 17:13 nvhpgn.los -rw-r--r-- 1 melita 1049089 4784 Jul 30 17:13 nyhpgn.las -rw-r--r-- 1 melita 1049089 4784 Jul 30 17:13 nyhpgn.los -rw-r--r-- 1 melita 1049089 311696 Jul 30 17:13 ohdhihpgn.las -rw-r--r-- 1 melita 1049089 311696 Jul 30 17:13 ohdhihpgn.los -rw-r--r-- 1 melita 1049089 2288 Jul 30 17:13 ohhpgn.las -rw-r--r-- 1 melita 1049089 2288 Jul 30 17:13 ohhpgn.los -rw-r--r-- 1 melita 1049089 3696 Jul 30 17:13 okhpgn.las -rw-r--r-- 1 melita 1049089 3696 Jul 30 17:13 okhpgn.los -rw-r--r-- 1 melita 1049089 2992 Jul 30 17:13 pahpgn.las -rw-r--r-- 1 melita 1049089 2992 Jul 30 17:13 pahpgn.los -rw-r--r-- 1 melita 1049089 1664 Jul 30 17:13 pvhpgn.las -rw-r--r-- 1 melita 1049089 1664 Jul 30 17:13 pvhpgn.los -rw-r--r-- 1 melita 1049089 2288 Jul 30 17:13 schpgn.las -rw-r--r-- 1 melita 1049089 2288 Jul 30 17:13 schpgn.los -rw-r--r-- 1 melita 1049089 4368 Jul 30 17:13 sdhpgn.las -rw-r--r-- 1 melita 1049089 4368 Jul 30 17:13 sdhpgn.los -rw-r--r-- 1 melita 1049089 2352 Jul 30 17:13 tnhpgn.las -rw-r--r-- 1 melita 1049089 2352 Jul 30 17:13 tnhpgn.los -rw-r--r-- 1 melita 1049089 4080 Jul 30 17:13 uthpgn.las -rw-r--r-- 1 melita 1049089 4080 Jul 30 17:13 uthpgn.los -rw-r--r-- 1 melita 1049089 2736 Jul 30 17:13 vahpgn.las -rw-r--r-- 1 melita 1049089 2736 Jul 30 17:13 vahpgn.los -rw-r--r-- 1 melita 1049089 3536 Jul 30 17:13 wihpgn.las -rw-r--r-- 1 melita 1049089 3536 Jul 30 17:13 wihpgn.los -rw-r--r-- 1 melita 1049089 6384 Jul 30 17:13 wmhpgn.las -rw-r--r-- 1 melita 1049089 6384 Jul 30 17:13 wmhpgn.los -rw-r--r-- 1 melita 1049089 5776 Jul 30 17:13 wohpgn.las -rw-r--r-- 1 melita 1049089 5776 Jul 30 17:13 wohpgn.los -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 wshpgn.las -rw-r--r-- 1 melita 1049089 2704 Jul 30 17:13 wshpgn.los -rw-r--r-- 1 melita 1049089 6800 Jul 30 17:13 wthpgn.las -rw-r--r-- 1 melita 1049089 6800 Jul 30 17:13 wthpgn.los -rw-r--r-- 1 melita 1049089 2728 Jul 30 17:13 wvhpgn.las -rw-r--r-- 1 melita 1049089 2728 Jul 30 17:13 wvhpgn.los -rw-r--r-- 1 melita 1049089 2992 Jul 30 17:13 wyhpgn.las -rw-r--r-- 1 melita 1049089 2992 Jul 30 17:13 wyhpgn.los ./nadcon: -rw-r--r-- 1 melita 1049089 88320 Jul 30 17:13 ICEGRID93.LAS -rw-r--r-- 1 melita 1049089 88320 Jul 30 17:13 ICEGRID93.LOS -rw-r--r-- 1 melita 1049089 530000 Jul 30 17:13 alaska.las -rw-r--r-- 1 melita 1049089 530000 Jul 30 17:13 alaska.los -rw-r--r-- 1 melita 1049089 133712 Jul 30 17:13 conus.las -rw-r--r-- 1 melita 1049089 133712 Jul 30 17:13 conus.los -rw-r--r-- 1 melita 1049089 227856 Jul 30 17:13 hawaii.las -rw-r--r-- 1 melita 1049089 227856 Jul 30 17:13 hawaii.los -rw-r--r-- 1 melita 1049089 88320 Jul 30 17:13 icegrid2004.las -rw-r--r-- 1 melita 1049089 88320 Jul 30 17:13 icegrid2004.los -rw-r--r-- 1 melita 1049089 13776 Jul 30 17:13 prvi.las -rw-r--r-- 1 melita 1049089 13776 Jul 30 17:13 prvi.los -rw-r--r-- 1 melita 1049089 30256 Jul 30 17:13 stgeorge.las -rw-r--r-- 1 melita 1049089 30256 Jul 30 17:13 stgeorge.los -rw-r--r-- 1 melita 1049089 13776 Jul 30 17:13 stlrnc.las -rw-r--r-- 1 melita 1049089 13776 Jul 30 17:13 stlrnc.los -rw-r--r-- 1 melita 1049089 3696 Jul 30 17:13 stpaul.las -rw-r--r-- 1 melita 1049089 3696 Jul 30 17:13 stpaul.los ./ntv2/australia: -rw-r--r-- 1 melita 1049089 4647312 Jul 30 17:13 A66_National_13_09_01.gsb -rw-r--r-- 1 melita 1049089 12627328 Jul 30 17:13 National_84_02_07_01.gsb ./ntv2/austria: -rw-r--r-- 1 melita 1049089 3193168 Jul 30 17:13 AT_GIS_GRID.gsb ./ntv2/brazil: -rw-r--r-- 1 melita 1049089 200368 Jul 30 17:13 CA61_003.gsb -rw-r--r-- 1 melita 1049089 473168 Jul 30 17:13 CA7072_003.gsb -rw-r--r-- 1 melita 1049089 675136 Jul 30 17:13 SAD69_003.gsb -rw-r--r-- 1 melita 1049089 688688 Jul 30 17:13 SAD96_003.gsb ./ntv2/france: -rw-r--r-- 1 melita 1049089 225584 Jul 30 17:13 RGNC1991_IGN72GrandeTerre.gsb -rw-r--r-- 1 melita 1049089 17568 Jul 30 17:13 RGNC1991_NEA74Noumea.gsb -rw-r--r-- 1 melita 1049089 277424 Jul 30 17:13 rgf93_ntf.gsb ./ntv2/germany: -rw-r--r-- 1 melita 1049089 83696 Jul 30 17:13 BETA2007.gsb -rw-r--r-- 1 melita 1049089 35043648 Jul 30 17:13 NTv2_SN.gsb ./ntv2/ireland: -rw-r--r-- 1 melita 1049089 570608 Jul 30 17:13 tm75_etrs89.gsb ./ntv2/japan: -rw-r--r-- 1 melita 1049089 136952064 Jul 30 17:13 tky2jgd.gsb -rw-r--r-- 1 melita 1049089 9856384 Jul 30 17:13 touhokutaiheiyouoki2011.gsb ./ntv2/netherlands: -rw-r--r-- 1 melita 1049089 3844960 Jul 30 17:13 rdtrans2008.gsb ./ntv2/newzealand: -rw-r--r-- 1 melita 1049089 318464 Jul 30 17:13 nzgd2kgrid0005.gsb ./ntv2/portugal: -rw-r--r-- 1 melita 1049089 944528 Jul 30 17:13 D73_ETRS89_geo.gsb -rw-r--r-- 1 melita 1049089 944528 Jul 30 17:13 DLX_ETRS89_geo.gsb ./ntv2/spain: -rw-r--r-- 1 melita 1049089 25824 Jul 30 17:13 100800401.gsb -rw-r--r-- 1 melita 1049089 661040 Jul 30 17:13 SPED2ETV2.gsb -rw-r--r-- 1 melita 1049089 101552 Jul 30 17:13 baleares.gsb -rw-r--r-- 1 melita 1049089 667552 Jul 30 17:13 peninsula.gsb ./ntv2/switzerland: -rw-r--r-- 1 melita 1049089 3310656 Jul 30 17:13 CHENYX06.gsb ./ntv2/uk: total 14884 -rw-r--r-- 1 melita 1049089 15240384 Jul 30 17:13 OSTN02_NTv2.gsb The files that are in the Coordinate Systems Data (CSD) setup as of ArcGIS Pro 2.2 / Desktop 10.6.1 are: ./ntv2/australia: -rw-r--r-- 1 melita 1049089 83028032 Feb 26 11:57 GDA94_GDA2020_conformal.gsb -rw-r--r-- 1 melita 1049089 83028032 Feb 26 11:57 GDA94_GDA2020_conformal_and_distortion.gsb ./ntv2/canada: -rw-r--r-- 1 melita 1049089 13817072 Jun 16 2006 Ntv2_0.gsb ./ntv2/spain: -rw-r--r-- 1 melita 1049089 101552 Aug 22 2017 BALR2009.gsb -rw-r--r-- 1 melita 1049089 667552 Aug 22 2017 PENR2009.gsb ./ntv2/switzerland: -rw-r--r-- 1 melita 1049089 3310656 Sep 17 2016 CHENYX06_etrs.gsb ./ntv2/uk: -rw-r--r-- 1 melita 1049089 15240384 Sep 23 2016 OSTN15_NTv2.gsb -rw-r--r-- 1 melita 1049089 174080 Feb 3 2016 osgb36_xrail84.gsb plus GEOCON (USA) files, and vertical transformation files except for EGM96.  Melita ... View more

NAD 1983 CSRS is the "readjustment" of the original NAD 1983 in Canada. A lot of people use "NAD 1983" when they have data that really in CSRS (or a later realization in the USA).  If you really had original NAD 1983 data, offsets between it and CSRS should still be sub-meter in southern Ontario. Unfortunately, Esri software doesn't have any data for NAD 1983 - CSRS transformations in Canada. They were released by the individual provinces and sometimes we need to arrange permissions to redistribute the files.  I poked around on NRCan websites but didn't find a converter or a way to check historical coordinates on a control network point. When you defined the data with NAD 1983 CSRS (2010) UTM 17N, did you make a custom coordinate system definition? If you did, you might try to use the just NAD 1983 CSRS-based definition, 2958 (you can type that into the search box). I'm trying to determine if there's an issue with using a custom GCS, something more general! Melita ... View more

Check your inbox! If you don't get something from me, send me an email at mkennedy at esri dot com. ... View more

Hi Sheila,  Login to MyEsri, choose My Organizations, Downloads, Data and Content.  Melita ... View more

Do you have the NTv2 file installed? If you installed per-machine / for everyone, it can go in:  C:\Program Files\ArcGIS\Pro\Resources\pedata\ntv2\canada However, you should instead install the ArcGIS Coordinate Systems Data setup for Pro 2.1 which should include the Canadian NTv2 file. Note: The NTv2_0 file converts from NAD27 to NAD83 (original), not to NAD83 CSRS which is maybe why you're defining the custom transformation. Note: You should only use GCS in the Create Custom Geographic Transformation tool. Melita ... View more

Hi Shane,  It's currently on our list of tasks for ArcGIS 10.7 / Pro 2.3.  Melita ... View more