Hi Benjamin,
You are definately on track to what our problems have been. And you have pretty much explained the solutions we have found. If I could make a recommendation, including the EPSG in the description list of each coordinate system would be really helpful. Some of these system's names look so similar but when you look close enough you find they are slightly different in naming. They all do have an EPSG designation, but beyond being able to select by the EPSG in TBC, you don't really see that designation anywhere else, even though it is still relevant.
Another thing I was trying to find was all the previous realizations of NAD83. We still have agencies that have their control network based on very old realizations, for example 1991.35 EPOCH is really popular in California. But you can't select that in TBC anymore, only 2011 EPOCH 2010.00 is available. Or am I missing something. I think this is all related to the coordinate systems that exist in the Coordinate system manager, so maybe when we updated that we lost some of the older ones.
Thank you for replying.
------------------------------
Clayton Bradshaw
------------------------------
Original Message:
Sent: 11-29-2022 15:22
From: Benjamin Messer
Subject: Access Defaulting to Local Site
Hi Clayton,
I am investigating this issue but I believe the root of this is due to the planned improvement of the Trimble Geodetic Library. It might sound contradictory that your issue is due to an improvement but since the coordinate systems are constantly being added to TBC/TA the Trimble Geodetic Library needs to change as well, especially for users working in the North American Datum. Since the next Coordinate System Database (CSD 105) will have changes to support additional North American realizations like the HARN realization, for example NAD83(1986), we had to modify the NAD83(2011) Datum transformation from NAD 1983 (Conus) to NAD83(2011) when working in the 2010 global reference which I'm guessing is the situation you're in right now.
I will double check with our support group but I believe updating your TBC *.vct template file (found in C:\Users\bmesser\AppData\Roaming\Trimble\Trimble Business Center\38.0 folder) with the NAD83(2011) transformation you should not see an issue with future projects. If you would like to fix the issue in TA with existing projects changing the "Local Site" coordinate system to NAD83(2011) CA 4 0404 for example. Another method would be to change the coordinate system in TBC to NAD83(2011) CA 4 0404 and re-export the job file. I hope this information is helpful.
Ben
------------------------------
Benjamin Messer
Original Message:
Sent: 11-29-2022 09:13
From: Clayton Bradshaw
Subject: Access Defaulting to Local Site
Since updating to TBC 5.80 we have had real issues with what our previous standard coordinate systems were and what they are now called in both TBC and Access. We haven't found the bread crumb needed to understand the problem, but we think that there is a slightly different naming convention between the pre-TBC-5.8 coordinate system files and the current naming conventions.
We are in California, USA and work on in USFt California Coordinate System 1983, mainly in Zone 4 and 5. We had templates set up for our typical jobs and have been using these without issue for years. Then with 5.8, when we would export to Access, newest version, and then open that exported Access file on the data collector, instead of the Access job having that assigned coordinate system, it would be set to local site.
Is anyone else seeing this happen and do you know why it is? We are remaking all of our templates (only a couple), but this is problematic for all our previously started TBC files for years and years of project work. It isn't difficult to correct, and our party chiefs and office folks have been warned to take care, but it is just another thing that needs attention, in a pile of many.
CB
Clayton Bradshaw
------------------------------
Clayton Bradshaw
------------------------------