|
POST
|
Speculation: a local caching issue that rebooting cleared. When was the last time you opened the map prior to this? So what caused the problem? A bad update of the imagery that was fixed quickly maybe?
... View more
01-25-2018
04:33 PM
|
0
|
1
|
1311
|
|
POST
|
UTMutah is just NAD 1983 UTM zone 12 North. I recommend that you use 26912 instead (it's found in projected coordinate systems, utm, nad 1983) Melita
... View more
01-23-2018
12:46 PM
|
1
|
0
|
1048
|
|
POST
|
We do have NAD83 "UTM" on US feet. It's called a BLM rather than UTM zone. It was added in 9.3, so it was available at 10.2. The only thing I can think of is that the ArcSDE data has an interesting (AKA nonstandard) xy tolerance value. When you import the prj file to set the data frame, the software is likely calculating the default xy tolerance value which should be 0.00328083. If that's bigger than what the ArcSDE data has, that would explain why Select by Location finds more points. Melita
... View more
01-16-2018
09:43 AM
|
0
|
0
|
1724
|
|
BLOG
|
Thank you all!! You make my life and every other Esri employee and customer easier! Melita
... View more
01-16-2018
09:30 AM
|
4
|
0
|
550
|
|
POST
|
My guess is that there's something funky in the text files--control characters, spaces in column names (leading or trailing spaces), etc. Can you add them to ArcMap using Add XY Data? If so, I would just export and/or reproject from there. If you can, you might post one of the problematic files, and one that works for people to take a look at. Melita
... View more
01-15-2018
12:26 PM
|
1
|
0
|
2244
|
|
POST
|
Ask me the hard questions, why doncha? I'm looking for it. EDIT: Here's the bug: NIM004421 The low number means it was likely ported from the previous bug system, so it's existed for a long time...originally logged in 2005. Melita
... View more
01-09-2018
03:33 PM
|
2
|
0
|
2923
|
|
POST
|
They finally went in at ArcGIS 10.6 / ArcGIS Pro 2.1. These follow EPSG who worked with Mike Craymer on them (I believe). We have no transformations for them yet. # NAD83(CSRS96) [NAD83(CSRS96)] 8232,GEOGCS["NAD83(CSRS96)",DATUM["North_American_Datum_of_1983_(CSRS96)",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433],AUTHORITY["EPSG",8232]] # NAD83(CSRS)v2 [NAD83 (CSRS) v2] 8237,GEOGCS["NAD83(CSRS)v2",DATUM["North_American_Datum_of_1983_(CSRS)_version_2",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433],AUTHORITY["EPSG",8237]] # NAD83(CSRS)v3 [NAD83 (CSRS) v3] 8240,GEOGCS["NAD83(CSRS)v3",DATUM["North_American_Datum_of_1983_(CSRS)_version_3",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433],AUTHORITY["EPSG",8240]] # NAD83(CSRS)v4 [NAD83 (CSRS) v4] 8246,GEOGCS["NAD83(CSRS)v4",DATUM["North_American_Datum_of_1983_(CSRS)_version_4",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433],AUTHORITY["EPSG",8246]] # NAD83(CSRS)v5 [NAD83 (CSRS) v5] 8249,GEOGCS["NAD83(CSRS)v5",DATUM["North_American_Datum_of_1983_(CSRS)_version_5",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433],AUTHORITY["EPSG",8249]] # NAD83(CSRS)v6 [NAD83 (CSRS) v6] 8252,GEOGCS["NAD83(CSRS)v6",DATUM["North_American_Datum_of_1983_(CSRS)_version_6",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433],AUTHORITY["EPSG",8252]] # NAD83(CSRS)v7 [NAD83 (CSRS) v7] 8255,GEOGCS["NAD83(CSRS)v7",DATUM["North_American_Datum_of_1983_(CSRS)_version_7",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433],AUTHORITY["EPSG",8255]]
... View more
01-09-2018
03:32 PM
|
0
|
0
|
3690
|
|
POST
|
In ArcMap, yes, there's a bug/known limit that the grids and graticule wizard doesn't handle geographic/datum transformations. So a grid or a graticule in a 2nd GCS is not displayed properly. One thing to try is to use the tools instead (Makes Grids and Graticules layer tool in the cartography toolset). They create the grids and graticule differently.....although a Technical Support contact says that doesn't work either. She says you would have to create a second data frame in the other PCS/GCS create it there, then overlay it exactly in the layer frame. Another possibility is to create the grid with Fishnet tool but then you have to label it yourself.
... View more
01-09-2018
03:09 PM
|
1
|
2
|
2923
|
|
POST
|
I'm sorry that I didn't reply earlier. Yes, that's correct. We currently don't support any polynomial transformations in the Esri projection engine. It's possible that's there's a way do a custom transformation using raster functions/tools but I don't know offhand how it would be done. Another possibility would be to build a grid of offsets using the polynomial equations and then use the grid (raster) to convert the maps or convert the offsets to use a lat/lon grid file. For the latter make a NTv2 grid or NADCON-style files--then you could use the Create Custom Geographic Transformation tool. Melita
... View more
12-19-2017
12:33 PM
|
1
|
0
|
947
|
|
POST
|
I see "St. Croix" in the data's path. Is this the Caribbean island or some other St. Croix. What I'm really asking is--what location does this data represent? With that information, we may be able to narrow down the possible projected coordinate reference systems. Melita
... View more
12-12-2017
11:48 AM
|
0
|
1
|
2128
|
|
POST
|
I'm sorry for the delay in responding. When you see a scale factor listed among the projection parameters, it's a defining characteristic of the projected coordinate system. It is not the scale/distortion-at-a-point that can be calculated via a Tissot Indicatrix or other calculation. At some point, we do plan to add those types of calculations, but don't have them yet. So for instance, in a Cassini projection, the scale factor sets the scale along the central meridian. In a UTM zone, where the scale factor is 0.9996, that's the scale along the central meridian which means there are two lines (they are not quite longitude lines) approximately 180 km west and east of the central meridian that have scale = 1. Melita
... View more
11-21-2017
04:56 PM
|
2
|
1
|
3691
|
|
POST
|
The regular Mercator projection can't display a pole. The Hotine oblique Mercator and RSO projections can display the poles depending on the projection parameters. What do you want to do with the data? Is it for display, analysis (what type?), etc.? You can look at the ArcGIS help list of support projections. The individual projection pages usually have a picture showing what the projection looks like and information about it like which property if any is preserved (area, shape, etc.). Melita
... View more
11-13-2017
12:12 PM
|
1
|
0
|
873
|
|
POST
|
A colleague pointed out that it's an abstract specification, not an implementation specification or standard. So everyone's still free to interpret and implement it however they like!
... View more
10-30-2017
11:07 AM
|
1
|
1
|
2336
|
|
POST
|
Hmm, because of the rotation and jagged edges, it looks like it has been reprojected. Converting to polygon should lose the white area because it's probably no-data or 0 so not considered part of the polygon. It doesn't surprise me that the extents would be different. Otherwise, I have no suggestions...but it is Friday at the end of a long week at almost 5pm.
... View more
10-20-2017
04:52 PM
|
1
|
1
|
3886
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 01-31-2014 09:23 AM | |
| 4 | 01-18-2026 04:30 PM | |
| 1 | 01-16-2026 10:03 AM | |
| 2 | 12-02-2025 08:06 AM | |
| 1 | 12-02-2025 08:00 AM |