I am getting an error in Pathfinder that I can't seem to solve. It is with an older Trimble which is a Geoexplorer 6000.
The error is essentially saying that the coordinate systems don't match so it wont load any of my data. I've attached a file containing a screen shot of the error.
The thing is that the Trimble and Pathfinder are in the exact same coordinate system, i've double/triple checked. I've been using this trimble for years and never had this error appear. I haven't changed anything so I don't understand why this error would suddenly appear. I can no longer open ANY of my files...
Help!
Two things come to mind. First would be a longitude entered as east rather than west. The other would be one system referenced to the WGS84 ellipsoid and the other to GRS80. It's a shot in the dark but hope it helps...
Is the problem only with this particular data file or any new files you create?
Have you recently updated the software?
> Two things come to mind. First would be a longitude entered as east rather than west. The other would be one system referenced to the WGS84 ellipsoid and the other to GRS80. It's a shot in the dark but hope it helps...
I'm not using Lat/Long, using UTM coordinates set as North/East. Both reference the same zone (9 north), datum and altitude :bored:
> Is the problem only with this particular data file or any new files you create?
> Have you recently updated the software?
Unfortunately it is now occuring with ALL data files, new and old... I was able to open the files yesterday.
I updated the software (and transferred which computer it was on) a few weeks ago and updated the base list about a week ago.
We have experienced similar problems over the years in several different data collectors. The last time it was after an upgrade. The new software assumed our false nothings and eastings were metric as opposed to US feet. Before that an upgrade got confused after stripping the minus sign from in front of all central meridians. The common thread on tbe errors is it creates points well outside a realistic area for the projection.
good luck...
Did you come up with a solution for the problem?
I've contacted my supplier regarding the issue but I think they are all out of office for the weekend....
The last go around we had to reload our projections by hand. Not really fun but su h 8 life when you mix and match as much as we do...
I would start by looking at the projection definitions. Do the units look correct? Are they in the correct hemisphere? Do the ellipsoid for the projection and geoid model match? Hopefully it will be one of these.
The solution will be driven by what you find and how you typically get projections and coordinate systems into the data collector.
Figured out the issue.. On the program the altitude measurement was set to measure MSL instead of HAE.. Always one little button! |-)
That's the great thing about a site like this. We can all share the unique ways we break stuff...
Glad you got it going..