Latest Contributions by MelitaKennedy

There are known bugs with copy/paste and drag/drop and the transformation warning dialog. Is the transformation dialog showing the different GCS? Is your new PAL_ITM projected coordinate system on a different GCS? The screen shots don't show that information. Melita ... View more

Have you done any searching via Google or Bing for something like "township range shapefile"? You're more likely to find local maybe up to statewide data. The PLSS doesn't lend itself to easy/regular creation because of the corrections, oddities, etc. ... View more

Hi, I want to make sure that everything is working correctly.  Did the vector layers (are they shapefiles or ?) already have a defined coordinate system? It sounds like they do, and its WGS84 / decimal degrees. We can probably assume that the tab-separated values (.tsv) are also in WGS84 but try to verify that by checking for their metadata on the website where you downloaded them.  So, 1. Add the vector data to ArcMap 2. Use Add XY Data to add the tsv data. Make sure the coordinate system is set to WGS84, or whatever coordinate system the values are in. 3. Open the data frame properties and change the coordinate system to 28992 (Amersfoort RD New).  4. Also set a transformation between WGS84 and Amersfoort (Transformations button on the coordinate system tab).  If you want to make copies of the data that are using RD New, you can use the Project Tool for the vector data (right click the tool to open in batch mode). For the tsv data, you could convert them to shapefiles or geodatabase feature classes by right-clicking its layer name and selecting data, export data. In that dialog, make sure that "use data frame coordinate system" is selected. Melita ... View more

Try also setting:  PCSName GCS (perhaps by the GCSCode instead, 4326 for WGS84, 4269 for NAD83) There also might be a problem with the parameters. Orthographic uses Lon/Lat of Center and parameters exposed here might not be converting to the correct ones internally. So if you do get a valid SR, make sure the results make sense. Melita ... View more

Clip was written well before we had any geodesic line support. It would have to be upgraded WITH the ability for someone to decide whether to clip in projected space or treating lines as geodesics (or other types). I can think of cases where you wouldn't want the geodesic used (western north border of conus, projected data that represents plss or other surveyed lines, etc.). ... View more

I think it's always been a separately licensed extension. It's still there on my ArcGIS for Desktop 10.5 version. Did you recently upgrade but not install or enable the extension? ... View more

I'm not 100% sure that I understand your question, but I'll describe how a few things work.  When you open the Transformations dialog, and select a particular input GCS, the transformation pull-down should list the current transformation or say "None" if nothing is set. I know at an early release, if you set a transformation, then tried to set it back to "None" that didn't work, but I don't remember for sure in which version that got fixed.  Transformations, once chosen, are put into a list of "active" transformations and that list is saved in an mxd. However, if you start over with a new mxd, you should be back to an empty list. ... View more

Dan, I just tried it on a device external to Esri's network (sort-of) and it worked. Copy/paste the base link, then add in the article number. It should work. Example (broken link on purpose): http://support.esri.com/en/knowledgebase/techarticles/detail/29035 Melita ... View more

No idea, but he's still listed in the UW directory! Maybe he's emeritus now. ... View more

Did you find that the "Harvey" listed on one page is Harvey Greenberg at UW? The UW directory lists a slightly different email, [email protected]. Have you tried calling Andrew North if he's not answering his email? Of course, everyone may be on vacation for the holidays right now. ... View more

I didn't get my act together to get a longer topic into the help for ArcGIS Desktop/Server 10.5 or ArcGIS Pro 1.4. I was specifically tasked with writing a white paper/blog posts/etc. about it. Maybe this week, while it's quiet!  Particularly for ArcGIS Pro, we're trying to keep the core setup as small as possible. Adding even the 2.5'x2.5' EGM2008 and the GEOCON files is close to 0.5 GB. Management said NO. We had discussed making a separate data install years ago, when the ArcGIS Desktop install was creeping towards requiring either another CD or maybe a DVD, but managed to scrape through. So with geoid models coming from several countries, and more grid-file-based transformations all the time, it was decided that we've start a separate setup for that data. It also allows customers to decide to not install everything if they want. At some point, we'll likely move the existing NADCON/HARN/NTv2 files from the core setups into this separate setup, but there's no timeline for that yet. There are two versions of the data setups. One is 32-bit and used for Desktop, Server, Engine, etc. The other is 64-bit and currently used only for ArcGIS Pro. The separation has mostly to do with being able to access the 32-bit and 64-bit registries, but ArcGIS Pro is also the one most likely to get out-of-sync with the others when dealing with release schedules. The GEOCON files are for the US and convert between the latest NAD 1983 HARN, NAD83 (NSRS2007), and NAD83 (2011). These files are from the GEOCON and GEOCON11 1.0 versions. There's a new version in beta from the NGS, that includes multiple HARN realizations (the last one is now called an FBN). While it's in beta, we haven't added support for them yet. The transformations that use these files are: NAD_1983_HARN_To_NSRS2007_GEOCON_CONUS NAD_1983_HARN_To_NSRS2007_GEOCON_Alaska NAD_1983_HARN_To_NSRS2007_GEOCON_Puerto_Rico_Virgin_Islands NAD_1983_NSRS2007_To_2011_GEOCON11_CONUS NAD_1983_NSRS2007_To_2011_GEOCON11_Alaska NAD_1983_NSRS2007_To_2011_GEOCON11_Puerto_Rico_Virgin_Islands The Vertical folder contains the EGM84 and EGM2008 2.5'x2.5' files. The EGM96 file is already in the core software. The EGM2008 1'x1' has a separate entry in the setup because it's so large. We aren't using it by default because of that. WGS_1984_To_WGS_1984_EGM2008_1x1_Height WGS_1984_To_WGS_1984_EGM2008_2.5x2.5_Height WGS_1984_To_EGM_1996_Geoid_1 WGS_1984_To_EGM_1996_Geoid_2 (interpolation is natural spline) WGS_1984_To_EGM_1984_Geoid_1 WGS_1984_To_EGM_1984_Geoid_2 (interpolation is natural spline) The Vertical folder also contains the US Geoid12b files (Alaska, Guam and Northern Marianas, Hawaii, Puerto Rico and US Virgin Islands, American Samoa, and CONUS) and the VERTCON files. We have the east, central, and west files, plus a combined one that we built in-house. NAD_1983_2011_To_NAVD88_CONUS_GEOID12B_Height NAD_1983_2011_To_NAVD88_Alaska_GEOID12B_Height NAD_1983_PA11_To_NAVD88_Hawaii_GEOID12B_Height NAD_1983_2011_To_PRVD02_GEOID12B_Height (Puerto Rico) NAD_1983_PA11_To_ASVD02_GEOID12B_Height (American Samoa) NAD_1983_MA11_To_GUVD04_GEOID12B_Height (Guam) NAD_1983_2011_To_VIVD09_GEOID12B_Height (US Virgin Islands) NAD_1983_MA11_To_NMVD03_GEOID12B_Height (Northern Marianas) NAD_1983_To_NAVD88_CONUS_GEOID12B_Height NAD_1983_To_NAVD88_Alaska_GEOID12B_Height NAD_1983_To_NAVD88_Hawaii_GEOID12B_Height NAD_1983_To_PRVD02_GEOID12B_Height (Puerto Rico) NAD_1983_To_VIVD09_GEOID12B_Height (US Virgin Islands) NGVD29_To_NAVD88_NAD27_3_East NGVD29_To_NAVD88_NAD27_2_Central NGVD29_To_NAVD88_NAD27_1_West NGVD29_To_NAVD88_NAD27_ECW (conus grid) NGVD29_To_NAVD88_NAD83_East NGVD29_To_NAVD88_NAD83_Central NGVD29_To_NAVD88_NAD83_West NGVD29_To_NAVD88_NAD83_ECW (conus grid) NGVD29_To_NAVD88_HARN_East NGVD29_To_NAVD88_HARN_Central NGVD29_To_NAVD88_HARN_West NGVD29_To_NAVD88_HARN_ECW (conus grid) Note: The NAD27/NAD83/HARN in the transformation name indicates the GeoCRS used to interpolate the offset values from the grid files. The VERTCON files are imprecise enough that it doesn't matter which NAD83 adjustment you use for the interpolation. However, we still need to them listed separately. We may end up adding NSRS2007 and 2011 variants in a future release. We had a few new NTv2 grids that ended up in the new setup as well. I suggested putting them in the core software with the existing ones, but no go. For Switzerland, we added a replacement for an existing grid, CHENYX06_etrs.gsb. For the UK, we added OSTN15_NTv2.gsb and osgb36_xrail84.gsb. The latter is for the CrossRail project in the greater London area. The transformations that use these files are below: CH1903_To_CHTRF95_1_NTv2 CH1903_To_ETRS_1989_2_NTv2 CH1903_To_WGS_1984_3_NTv2 ETRS_1989_To_OSGB_1936_OSTN15 WGS_1984_To_OSGB_1936_OSTN15 OSGB_1936_To_Xrail84_NTv2 I'm working on other countries' geoid files but redistribution rights are often an issue. Melita ***Edited to list the transformations that use these files. ... View more

I've got an almost-final-Release-Candidate (they ain't changing the python version now). It has the same versions as Robert. ... View more

Based on the original image, they might have originally had data in 3 UTM or MTM zones which were then unprojected. Thus the truncated NS lines around 90W and 85W (approximately). Or, if Ontario used a township-range-section system, that could also cause those types of artifacts. ... View more

Check ArcMap and see what transformation (if any) is set there: Data frame properties, coordinate system tab, Transformations button. If it's not the same, change Pro to use the same transformation. ... View more

Just wondering, UTM using feet for the units, correct? Thanks! Melita ... View more