Darren Clemons
Well-Known Member
Installed the pre release first thing this morning. At first, everything was fine. Installed, rebooted fine and coordinates of current job were in Ky Single as they were supposed to be.
It just so happened, the first thing on my list today was something back on an old job. I found and unpacked the archive of that job and when I went into coordinates of it, they were all screwed up again - back to just Lat/Long - no coordinate transformation.
I then went back into the job that had looked ok after update and now it was the same - no Ky Single zone coordinates.
This has got to be back on the genmapsdata.dbf file I've had so much trouble with - it happens with unpacked archived jobs and with the "duplicate" coordinate systems of KYsinglezone (12.11.17 where it applies a date to the end of the crd system).
I deleted the old unpacked job - rebooted and just started a "new" job and imported the raw coordinates from Autocad and everything is fine (I think )
Just sent Scott out to two jobs - will find out soon if all's OK.
It just so happened, the first thing on my list today was something back on an old job. I found and unpacked the archive of that job and when I went into coordinates of it, they were all screwed up again - back to just Lat/Long - no coordinate transformation.
I then went back into the job that had looked ok after update and now it was the same - no Ky Single zone coordinates.
This has got to be back on the genmapsdata.dbf file I've had so much trouble with - it happens with unpacked archived jobs and with the "duplicate" coordinate systems of KYsinglezone (12.11.17 where it applies a date to the end of the crd system).
I deleted the old unpacked job - rebooted and just started a "new" job and imported the raw coordinates from Autocad and everything is fine (I think )
Just sent Scott out to two jobs - will find out soon if all's OK.