Configuring a GIS feature service connection

SiteVision supports feature service data delivered in the following output formats:

• GeoJSON

• GML v2

• GML v3

• GML v3.2

The following data types are supported for each format:

SiteVision supports a range of Feature Service authentication options. While many publicly available Feature Services will have no authentication requirements, this area can be quite technical to set up and configure. The expectation is that you will need to contact your Feature Service provider so they can supply you with the correct URLs and credentials.

To specify the authentication approach, in the Account panel select the appropriate Login Type from the dropdown:

• None: Many Feature Services do not require any authentication.

• ArcGIS Token Server: Requires an Account Name and Password, and a Token Server URL. Leaving the field blank will prompt the input of this information when the WFS is loaded in SiteVision.

• Http Authentication: Requires an Account Name and Password. Leaving the field blank will prompt the input of this information when the WFS is loaded in SiteVision.

• OAuth: Requires quite extensive inputs, contact your OAuth service provider for these details.

• ArcGIS Online: Effectively a pre-populated OAuth connection, this may require some server side configuration to allow SiteVision to successfully connect.

After inputting the appropriate credentials the Test option can be used to confirm receipt of a valid login token. A valid response will display a icon.

There is a wide variety of server side configurations available when establishing an OGC web feature service. While the vast majority of these configurations are handled, there are advanced options available in SiteVision Manager that may be required based on the server settings.

To access the advanced settings, click More at the bottom of the Server Details panel.

• BBox Type: This setting controls the format and order of the coordinates used by the BBox (bounding box) function. It can be common for older OGC WFS (v1.1.0) to require BBox coordinates in a reversed Latitude, Longitude coordinate order.

• Send BBox EPSG: Determines if the BBox coordinate EPSG is appended to the BBox fetch request. It should be very uncommon that this setting would need to be adjusted.

• Invert Axis Order: Enabling this reverses the coordinate order of received feature data. This is a common requirement for OGC WFS that serve data in GML format.

SiteVision supports 2D Feature Service data. When 2D data is detected, SiteVision by default displays the data on a horizontal plane located 1.5 m below the APC of the SiteVision unit. For typical handheld use in flat areas this places the data close to the ground surface.

SiteVision also supports 3D Feature Service data. When 3D data is detected, SiteVision by default treats the Z values as absolute elevations and displays the features at the appropriate elevation.

You can alter this behavior by defining visualization rules using the SiteVision Manager, so it is possible to differentiate between e.g. ground surface, pipe invert, or depth below ground.

SiteVision will identify the coordinate system of the Feature Service automatically and display your data accordingly. The EPSG code of the coordinate system will be displayed in the Model Information window.

Important: SiteVision does not support Feature Services that deliver data in the Pseudo-Mercator (EPSG 3857) coordinate system.

As with any other SiteVision model it is also possible to apply a Trimble Site Calibration file (JXL, CAL, DC). Calibration files can be helpful in the following cases:

• Transform data in Lat/Long to a cartesian coordinate system

• Apply a different or custom Geoid model

• Incorporate a Site Calibration to adjust for a local height datum or control network