This is documentation of a bèta release.
For documentation on the current version, please check Knowledge Base.

Orbit Web service file

An Orbit Web service resource connection file is a file reference to one specific layer of a well defined web service.
It is advised to read first the documentation about Web-based Resources.

Connection file by web service type :

  • *.owms : Orbit Web Map Service
  • *.owmts : Orbit Web Map Tile Service
  • *.owfs : Orbit Web Feature Service

Structure

An Orbit Web service resource connection file has the following structure:

Required configurations

  • ServerType : WMS, WMTS or WFS.
  • ServerName : Free of choice, but do not use “.” character. Web service name as labeled in Orbit.
  • ServerURL : service url
  • DataSetName : <layer name> or <layer order reference>
    • <layer name> : Value of service FeatureType Name tag in the FeatureTypeList.
    • <layer order reference> : “[i]”, “i” is the order of the layer it the web service FeatureTypeList. (only for OWFS).

Optional configurations

  • UserName : Username credentials if applicable.
  • Password : Password credentials if applicable.
  • swap_axis : Comma separated list of EPSG codes. Set list of CRS for map requests coordinates need to be inverted.
  • PreferredCRS : EPSG Code. Set fix CRS for all web service communication and map requests. (Only for OWMTS)
  • StaticContent : true or false, default false. (Only for OWFS)
    If true, then all features are loaded at once and saved in memory. The initial feature request will take more time, but once loaded there are no more web requests needed. This setting is perfect for smaller and static WFS layers to avoid continuous time-consuming web requests.
    If false, then features are loaded on-the-fly as needed corresponding to the map view. Setting for larger and/or dynamic WFS layers.
  • FallbackGeometryPropertyType : PointPropertyType, LineStringPropertyType or PolygonPropertyType. (Only for OWFS)
    Specification of the feature's spatial type (geometry) is mandatory only if the service is not specifying the geometry or identifying the spatial type as generic geometry.
  • Is3D : true or false, setting to request 2D or 3D vector features, default false (Only for OWFS).
  • IgnoreDCP: true or false, setting to ignore the post requests URLs as specified in the service's capabilities file. Orbit will use the capabilities URL for all requests. Default false.
  • UpdateMode: READONLY or FULL_CONTROL for WFS-T, default is FULL_CONTROL

Reason to use

A Web Service reference file simplifies use of Web resources and enables additional configurations :

  • Manage and share web resource in the same way as regular, file based resources.
  • Associate an Orbit Legend file.
  • Set additional service configurations, see Structure.

Create

Create and edit the .owfs, .owms and .owmts files using a simple text editor (e.g. Notepad). Take care of spelling and file syntax.

Exemples of owfs configurations > to be saved in a .owfs file
ServerType:WFS
ServerURL:https://msdi.data.gov.mt/geoserver/MITA_WFS_SR_GeoSubArea/wfs
ServerName:geoserver
DataSetName:MITA_WFS_SR_GeoSubArea:SR.SeaArea.GSA15.WFS
PreferredCRS:3045

Exemples of owms configurations > to be saved in a .owms file
ServerType=WMS
ServerName=wms.geo.gr.ch
ServerURL=https://wms.geo.gr.ch/kstn_strassenentwaesserung?Service=WMS&Request=GetCapabilities&Version=1.0.0
DataSetName=Eigentuemer_Belagsschale

 
Last modified:: 2023/10/06 16:56