Trimble Business Center

 View Only
Expand all | Collapse all

Why aren't GGF files imported with Job files if they exist?

  • 1.  Why aren't GGF files imported with Job files if they exist?

    Posted 06-12-2019 23:28

    When importing a Job file into TBC that comes from a project copied out of Access, why is it we don't check and reference a GGF if it exists in the project folder automatically and let the user know we have done that?

     

    The current workflow makes the user manually locate the GGF file we have written out of access, which seems a bit of a convoluted approach considering it should be in a standard location and would be the GGF that was used for that project.



  • 2.  Re: Why aren't GGF files imported with Job files if they exist?

    Posted 06-13-2019 08:21

    Noted. Thanks for your suggestions!

     

    -Josh



  • 3.  Re: Why aren't GGF files imported with Job files if they exist?

    Posted 06-17-2019 07:03

    We have created our own .ggf files at my current employer. I don't have to select the .ggf each time I am importing the .job file. Did you place the .ggf file in the correct location where your TBC is installed? Have you imported the .ggf into the Coordinate System Manager(CSM)?

     

    Maybe I have misunderstood what you are saying, but if not, here is the generic location of .ggf files when you install TBC onto a normal C-Drive/PC:  C:\ProgramData\Trimble\GeoData

     

    Once you place the .ggf file there you can go into the CSM and create the required profile and from there you will locate the .ggf file you placed in the standard folder.



  • 4.  Re: Why aren't GGF files imported with Job files if they exist?

    Posted 06-17-2019 22:50

    Normally this is the case, and you are right about this. Our team here works on supporting Trimble field and office solutions for users and we don't always have the luxury of having a .GGF already accessible, as users create their own or naming conventions change over time. For everything that calls a default code we don't have an issue with, its when we hit custom ones that don't already exist it would be good to have the ability for TBC to reference the one that has been copied with the job.

     

    The .GGF is there and it has been copied from Access so TBC should give users the option to reference the relevant file in the import or simply use it, rather than tell the user it doesn't have it and then get them to go off and sort out its import and use. It doesn't help either that the .GGF can't be dragged and dropped into TBC to reference it either.

     

    Its not a deal breaker by any means, just something that seems a little clunky for anyone that would hit that menu.



  • 5.  Re: Why aren't GGF files imported with Job files if they exist?

    Posted 06-18-2019 05:44

    I thought that with a TSC3 connected to your laptop, that when you drag a JOB file from the Access explorer into the plan view that it will copy all associated files including the FXL and geoid file. That now is not possible if you are using a TSC7 since it cannot connect to your laptop in the same way the TSC3 can.