|
POST
|
RMS is in the units of the coordinate system which is, in this case, decimal degrees (your links are lat/lon). Melita
... View more
05-07-2014
11:47 AM
|
0
|
0
|
4758
|
|
POST
|
Hi Tufayel, The data was already in NAD83 UTM 13N, so all that needed to happen was adding this information to the shapefile. That's done with the Define Projection tool or the data's property page in ArcCatalog. Check out the data's extents above the coordinate system in the picture you posted. Do those look like latitude and longitude (decimal degree) values? They're much too big. When you defined the data as NAD 1983 (geographic coordinate system), the software tried to interpret the very large coordinates as if they're decimal degrees. Melita
... View more
05-02-2014
09:54 AM
|
0
|
0
|
606
|
|
POST
|
Hi, The csf can't be used by ArcGIS as far as I know (possibly Data Interoperability Extension can). You also should have a .prj file that contains the coordinate system information. Is there one? If there isn't, it's possible that the projection isn't supported by ArcGIS. Can you ask the data provider what the coordinate system is? Melita
... View more
05-02-2014
07:56 AM
|
0
|
0
|
3489
|
|
POST
|
Can you change the wkid to its replacement, 31466? It's the same coordinate system, just a slightly different name. Melita
... View more
04-28-2014
08:45 AM
|
0
|
0
|
1884
|
|
POST
|
Hi Wei, I don't use the Javascript API, but what about esri.geometry.geodesicUtils? Melita
... View more
04-25-2014
08:25 AM
|
0
|
0
|
2898
|
|
POST
|
Hello, Try unprojecting the data to its GCS (ArcInfo Sphere), then use the Define Projection tool to change the coordinate system to WGS 1984. At that point, try adding it, with your other data, to ArcMap. If it lines up, use the Project to convert to the final coordinate system that you want to use. Melita
... View more
04-24-2014
08:22 AM
|
0
|
0
|
1760
|
|
POST
|
While Esri does trail the EPSG Dataset because of release cycles, EPSG:32617 has been 32617 for a very long time and has never had any changes. If you dump the geotiff headers with listgeo.exe or something similar, are the projection parameters there? Do they match the EPSG code or the listed zone? Did Esri software create the geotiff? Melita
... View more
04-23-2014
01:35 PM
|
0
|
0
|
3116
|
|
POST
|
Okay, please do not consider this a binding/legal Esri answer, but going by the ArcGIS for Server Product life cycle document, 10.0 is in mature support while 10.1 is still in extended support. Further information on what that means is available here. Melita
... View more
04-23-2014
12:48 PM
|
0
|
0
|
1625
|
|
POST
|
Hi Andy, You can leave it. There's always a slight performance hit due to reprojecting the data that depends on the amount of data that you're looking at. You could convert the data to a feature class and make a copy in BNG by projecting it. Melita
... View more
04-23-2014
08:54 AM
|
0
|
0
|
1540
|
|
POST
|
As Jim says in his response, it's almost certainly an incorrectly defined coordinate system. You state that you added attribute fields with: decimal degrees longitude and latitude in British National Grid co ordinate system That's two different coordinate systems--a geographic one using longitude and latitude (OSGB 1936)--or British National Grid--a projected one. My guess is that the Excel data does have latitude-longitude values, but that you're assigning British National Grid as the coordinate system. That would cause the points to bunch up as they're all very small if their coordinates are being treated as BNG. Are they far southwest of where they should be? Melita
... View more
04-22-2014
09:49 AM
|
0
|
0
|
1540
|
|
POST
|
Hi, Both Vince and I are on the development-side, not the technical support side. It is possible for me to enter a bug into the development bug-tracking software and export it to the public/technical support software, but it's frowned upon. Partially, because I don't have access to the customer information, and don't know the right questions to ask (like DBMS/OS/release/etc) that's useful to have when putting together a bug report. Technical Support will also be able to identify if the issue has been reported before; I can't always do that reliably. It also gets the bug report into the correct queue; neither Vince nor I will be directly involved in triaging, fixing, or testing it and an analyst familiar with the area will have a better idea where to put it. Vince was able to repro it, I identified a similar bug but in a different API and stated that I couldn't identify the same issue in the C API code, so someone will still have to figure out what the real problem is. I pointed out the other bug because it might help an analyst/developer to compare working code (even in a different language). Melita
... View more
04-18-2014
02:45 PM
|
0
|
0
|
1625
|
|
POST
|
This may be a red herring, but when you contact tech support, you should also tell them that there was a very, very similar bug that was fixed in version 10.0 but for the SDE Java API. I looked at the fix and the same issue is not apparent to me in the C API code--which is why it might not be the same bug. Reference NIM040332: Running SeQuery.createTableStatistics with the 'SeTable.SeTableStats.SE_DISTINCT_STATS' option hangs when processing an nvarchar field from an ArcSDE 9.2 SQL Server 2005 database and gives an error when processing an nvarchar2 field from an ArcSDE 9.2 Oracle database. Melita
... View more
04-17-2014
03:01 PM
|
0
|
0
|
1625
|
|
POST
|
Hi, That would probably work fine! I didn't find exact matches in the EPSG registry for Serbia, but I think that both are using Gauss-Kruger zones, but one has added the zone number as the first digit of the easting values. This is pretty common in Europe. They do show an MGI or MGI 1901 Balkans zone 7 that has paraemeters that make sense--the false easting is 7500000. The scale factor is 0.9999. Many Gauss-Kruger zones I've seen use 1.0 instead. It's possible one is using UTM instead. UTM uses 500000 for the false easting. But the scale factor for UTM is 0.9996. If the two datasets are offset, but not very much, it could be because of different scale factors. What GCS/datum both datasets are using is unknown which could cause another problem. Melita
... View more
04-07-2014
01:26 PM
|
0
|
0
|
636
|
|
POST
|
Hi Pierre, ArcGIS doesn't support the southing-westing axes of the Lo system. We added some "pseudo" definitions that work by using a negative scale factor (changing the signs on all coordinates). Are you using one of those? Could this data already have changed/flipped values? If you are using one of the existing Lo coordinate systems, what happens if you redefine the coordinate system again by modifying the scale factor? Just change its sign. Melita
... View more
04-04-2014
09:57 AM
|
0
|
0
|
615
|
|
POST
|
Change it to a tiff or jpeg instead. I used the default file geodatabase, but I'm not sure what raster 'format' that is. Melita
... View more
04-03-2014
10:10 AM
|
0
|
0
|
1743
|
| Title | Kudos | Posted |
|---|---|---|
| 3 | Wednesday | |
| 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 |