Groundhawk Guide for Documenter
You will find all the relevant information that will make using Groundhawk efficient in your daily work.
How should the documenter work with Groundhawk? Let’s assume here that the role of the documenter is to ensure that site is properly documented in the network owners GIS system.
There are two fundamentally different ways the data can flow from Groundhawk to the GIS system – either through downloaded files from Groundhawk portal or directly using APIs. We will primarily instruct here the download case.
Before the Build
Before a project is started the documenter should together with the project manager take care of 3 things:
- The project is created in the Groundhawk portal (+Add site),
- The project route plan is uploaded to Groundhawk (DXF file to support),
- The project export format, specific site extra attributes etc are defined with Groundhawk
The following configurations can be made to a site:
- Basic site information
- Site export format
- Access rights (which field user can see and record to the sites)
- Custom cables and protections. A site can have specific or added cables/protections
- Extra attributes for trenches like Cover material, type of network etc are typical extra attributes.
During the Build
During build it makes sense for documenter to regularly review the incoming documentation and give feedback to project manager if there seems to be missing information, bad photos, etc.
Documentation can be started during the build. Keep in mind that by default the site map data is contains the full site, meaning that if you document in increments you need to ensure you can only import part of the information to avoid duplication of imports.
Groundhawk support is ready to help you at any point. Reach out if you have a question!
After the Build
Before end of the build, ensure the team really has mapped everything
Archive when documentation is finished the site can be archived.
Archive when documentation is finished the site can be archived.