#158
- Created on2012-03-22 15:38
- Reported by
- StatusTest
- PriorityNormal (3)
- Assigned to
- Milestone-
- Plan LevelStory
- Due Date-
Waypoints/tracks downloaded from DNRGPS are offset approximately 300-400 feet west of correct location
4 tips to improve your experience:
Waypoints downloaded with the DNRGPS software to ARCMAP 10 are not
correctly located. The points are offset 300-400 feet west of the
correct location. The project layers and downloaded waypoints are both
projected with "NAD 1927 UTM Zone 11." With previous versions of
DNRGarmin, the way to fix this issue was to change the correcting engine
files with "WO" in the file name to something different. This would
disable the correcting engine and allow the points to be located
correctly on the maps. What needs to be changed or disabled on the
DNRGPS version so that the downloaded waypoints will be located
correctly on the ARCGIS 10 maps? I have already changed the files with
"WO" without any success.
- The email subject will become the ticket summary.
- Attachments in your email will be included in the ticket.
- Reply to a ticket alert from Assembla and your email will be posted
- If you want to change other fields, read the extra documentation:
Waypoints downloaded with the DNRGPS software to ARCMAP 10 are not
correctly located. The points are offset 300-400 feet west of the
correct location. The project layers and downloaded waypoints are both
projected with "NAD 1927 UTM Zone 11." With previous versions of
DNRGarmin, the way to fix this issue was to change the correcting engine
files with "WO" in the file name to something different. This would
disable the correcting engine and allow the points to be located
correctly on the maps. What needs to be changed or disabled on the
DNRGPS version so that the downloaded waypoints will be located
correctly on the ARCGIS 10 maps? I have already changed the files with
"WO" without any success.
Leave a comment
One of the LinkedIn ESRI Network Group members reported an ArcMap issue that sounds something like #158... possibly it's an ArcMap issue. See:
http://www.linkedin.com/groupItem?view=&srchtype=discussedNews&gid=86844&item=101593297&type=member&trk=eml-anet_dig-b_pd-ttl-cn&ut=0dVOVmHmK9TR81
http://www.linkedin.com/groupItem?view=&srchtype=discussedNews&gid=86844&item=101593297&type=member&trk=eml-anet_dig-b_pd-ttl-cn&ut=0dVOVmHmK9TR81
The error could be in one of 3 places:
- The coordinates are being projected incorrectly in DNRGPS. To check this, type in a known location's Lat/Long values into the DNRGPS data table. Go to Edit-->Project Coordinates. Are the resulting XProj/YProj values correct?
- If saving to a shapefile, the PRJ file could be written incorrectly by DNRGPS. If this is the case, the data is getting projected correctly but Arcmap is reprojecting on the fly to a faulty prj definition. To check this open the PRJ file in Notepad from a shapefile saved out of DNRGPS and compare it to another PRJ file you have associated with another shapefile. Are the definitions consistent?
- ArcMap could be reprojecting on the fly incorrectly for that Datum/projection (I'm not in LinkedIn so don't have access to the link posted by Anonymous). If the first 2 suggestions above check out then the problem may be here.
This issue existed also in DNRGarmin and pertains to the area where two projection files are overlapping. In this case it was Northern California (using conus.dat) being overlapped by southern Oregon (using wo.dat). DNRGarmin falsely selects the wo.dat file thus the projection shift. Removing the wo.dat file fixed this issue as then the correct dat file was selected. How is this handled in DNRGPS?
