This article contains an example of a Python script with comments that allows to leverage the Cintoo Connect CLI functionality to import terrestrial scan data.
An example of a script is provided in the attachment.
This script is an example for how to automate a scan's import to a specific work zone. It doesn't need an URI, but some IDs need to be specified. It calls the import-static command in the function "import_file", open to any modifications if needed.
Below please find the script with comments on each part.
Import of libraries. Obtaining token and headers. For more details: Cintoo Connect CLI API guidance.
- Account ID for the account hosting the project targeted
- Project ID corresponding to the target project with the targeted work zone is
- Work zone ID corresponding to the target work zone
They could be retrieved with HTTPS requests or from WebApplication URL inside a work zone.
https://aec.cintoo.com/accounts/<ACCOUNT_ID>/projects/<PROJECT_ID>/workzones/
More detailed guidance: Cintoo Connect CLI API guidance.
Default URL could be either aec.cintoo.com or us.cintoo.com or <company>.cintoo.com if organization has a dedicated domain depending on configuration.
Finding and executing the Cintoo Connect CLI executable. Executable is located in the same place where CintooConnect is installed. By default it should be in:
- Users/"YourUserName"/AppData/Local /Programs/Cintoo
- ProgramFiles/Cintoo if installed with admin rights
Sending information to a server and getting a verification of the server response.
Login validation.
Getting the Cintoo URI out of account, project and workzone components defined earlier.
Execution of the import process with the Cintoo Connect CLI executable.
Importing all the files in the defined directory.
Execution of the main function.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article