WorksManager

Hi, when selecting MGA2020 with AusGeoid2020v2 the Geoid doesn't sync even if you add the v2 geoid manually. Is anyone else having this issue?

We had an issue with geoid18 (conus) with some of our older machines. From what I can tell, EW doesn't directly reference the geoid file, but goes through a database file (coordsystemdatabase.xml OR xintcoordsys.xml). The DB file was missing the reference to 18 and just had to be added by hand. The "name" line is what the .cal calls it, and the "gridfilename" is the name of the actual geoid file. Had to be done in person on each machine.

Same issue Tom. We ended up just using the AusGeoid2020. Doesn't appear to be a difference

This was resolved by updating the coordinatesystemdatabase.xml on the machines. 

In my case, the previous coordinatesystemdatabase.xml in WorksManager was from 2020 and didn't contain AusGeoid2020v2. I couldn't see how to update this using WorksManager but I could upload the file using TCC:

Once the machine did a file transfer the coordinatesystemdatabase.xml was updated and the job using AusGeoid2020v2 worked.

Tom, glad you were able to resolve it. Please refer this blog article to use WorksManager File Explorer (instead of TCC explorer) to achieve the same. You can add, delete, download, sort and search files in a simple explorer style; folder operations are work in progress, and should be available this quarter.