Timeline for CRS Conversion problem
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 21, 2013 at 13:38 | comment | added | Ligia | thank you very much for all your replies. It definitely cleared out the problem. Now I'll start finding solutions to a new one:) | |
| Feb 21, 2013 at 13:36 | vote | accept | Ligia | ||
| Feb 21, 2013 at 7:49 | comment | added | Jens | to 1: I think your original problem is solved: A and B have a misalginment of 0 meters to 50 meteres because of bad digitization. to 2: I suspect that the datum transformation from A to Bing and from B to Bing is not correct. To solve this problem I would start a new question on gis.stackexchange. | |
| Feb 21, 2013 at 7:05 | comment | added | Ligia | 1. Hi again, we're talking about a 50 m to the east, but as I looked carefully now, it could be just a matter of bad digitization for databaset B, because on certain sections it overlaps perfectly. 2. I added Bing Aerial Basemap, the difference between the basemap and the two feature classes is 180 m to the east, and around 35 m to the south. | |
| Feb 20, 2013 at 14:48 | comment | added | Jens | Is the difference of 50 m always in the same direction? Then I suspect a problem with the datum transformation. Have you used the right transformation? | |
| Feb 20, 2013 at 13:38 | comment | added | Ligia | I assume B is WGS 1984. Meanwhile I deleted any.prj file I had for B, gave them from ArcCatalog the WGS 1984 geographic coordinate system-> and then in ArcMap-> Project (with the projection of A). There is still a difference of aprox. 50 m. | |
| Feb 20, 2013 at 13:03 | comment | added | Jens | Do you know the corret coordinate system for B? Then use the tool Define Projection (Data Management) to overwrite the coordinate system information of B. | |
| Feb 20, 2013 at 12:08 | comment | added | Ligia | This is exactly what I was writing now :) I think the coordinate system for B be is defined incorrectly. what do I do in this case? | |
| Feb 20, 2013 at 11:46 | comment | added | Jens | When adding data A to ArcMap, ArcMap reads the coordinate system information stored with data A. The data frame use coordinate system A. If you add data B to the same data frame ArcMap will project data B 'on-the-fly' to the coordinate system that is set for the data frame (A). If the proper datum transformation is not specified you will see a misalginment of about 50 to 500 meters. If the coordinate system definition of A or B is incorrect you will see a very large misalginment (up to thousands of kilometers). So I assume: the coordinate system definition of A and/or B is incorrect. | |
| Feb 20, 2013 at 11:18 | comment | added | Ligia | checked first possibility before; didn't work. tried second: Added feature class A to a new data frame. Then added feature class B. Set datum transformation in data frame properties. feature classes didn't align:( | |
| Feb 20, 2013 at 10:09 | history | answered | Jens | CC BY-SA 3.0 |