I am working on a project in the Coordinate System NAD_1983_UTM_17N within ArcMap. I used a Yuma Trimble to collect data in Terrasync and made sure the projection was the same. I transferred the files to GPS Pathfinder in order to export the ssf file to a shp file in ArcMap.
I fist noticed that most of my points were being filtered out, so that the imported shp file did not match the actual area. So I exported the ssf file once more, but made sure to check off that uncorrected points were included, and the imagery matched finally.
However, even though the new shp file has the same projection, and I made sure using the Projection tools in ArcMap, the shp file appears in what must be the Arctic Circle. I am working in Florida. I traced the area myself in ArcMap using aerial imagery, but obviously the Trimble data would be more accurate.
I am at a loss of what to do, I have constantly checked the projection, made sure the same projection was listed in the layer in ArcMap, and even double checked the prj file that GPS Pathfinder references to export into ESRI.
Has anyone experience anything similar?
Best Answer
Confirming the PRJ in Arc is irrelevant as you can arbitrarily assign any projection to any file - even if it's wrong. You should check you export coordinate settings in PFO and be sure you're assigning the right .prj to match that setting.
In PFO you can set your "Display coordinates" and "Export Coordinates" separately and they do not talk to each other.
In the Export module, specify if you want to export in the "current display coordinates" or other specified "export Coordinates" which can be different
As noted in my comment on your answer:
Exporting it to KMZ probably worked because KMZ is always in WGS84. The fact that KMZ works makes me suspect that, instead of it being a bug, that your export coordinate system is not set to what you think it is.