Field Systems Data Services comprises a set of cloud services and storage, to support the needs of Field Systems field applications, and their workflows. For instance, a Jobs Service is needed to help the field applications package and deliver their field data, from the field, to where it is required for delivery to the customer. A Settings Service is needed to capture configuration settings, and to convey them to the field.
Environments and Regions
Field Systems Data Services makes use of Azure as its cloud provider. Field Systems Data Services are developed in .NET and deployed as Azure Function Applications.
MongoDb Atlas is the cloud storage provider of choice for Field Systems data.
Field Systems have a dependency on Trimble Connect because Connect projects are typically used to store data files related to field systems jobs and settings.
Field Systems and data are stored in different regions around the world. Regions are chosen to match the Connect project regions.
Multi-Region Environments
The intent is to support a multi-region architecture, such that each environment has instances of the Jobs Service available in multiple regions, to be as close as possible to the customer and the origin and destination of their data. Jobs Service will have services near the Connect regions. Regions: East US 2, Australia East, North Europe, South East Asia
Bearer tokens
Jobs Service requests all require a Bearer token header parameter to identify the calling user/application.
These bearer tokens are generated by Trimble Identity login using oAuth.
An application API cloud application must have been registered to use the Geospatial Data Services product.
Swagger Console
The Cortex services all provide OpenAPI documentation, and a swagger console for testing the API routes. These routes are as follows:
/swagger/ui to browse the swagger console ui
/swagger.json to request the openapi document, in json format\
/swagger.yaml to request the openapi document, in yaml format\
/openapi/OpenApi3_0.yaml
/openapi/OpenApi2_0.yaml
/openapi/OpenApi3_0.json
/openapi/OpenApi2_0.json to request the openapi document in various versions and formats
/redoc/ui to view the API documentation as a Redoc UI\
For instance, use https://cloud.api.trimble.com/geospatial/jobs-service/1.0/swagger/ui to load the Swagger console for the Jobs Service.
Service root URLs are:
For the Jobs Service: //cloud.api.trimble.com/geospatial/jobs-service/1.0
and
For the Settings Service: //cloud.api.trimble.com/geospatial/settings-service/1.0