Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dev:technology:core:web_resources [2021/01/12 16:36]
jeroen [Web-based Resources]
dev:technology:core:web_resources [2023/10/06 09:10] (current)
jeroen [IT Troubleshooting]
Line 6: Line 6:
 ===== Web Map and Web Feature Services ===== ===== Web Map and Web Feature Services =====
  
-Web Map Service (WMS), Web Map Tile Services (WMTS), and Web Feature Service (WFS) are the standard protocols of the [[http://www.opengeospatial.org/|Open Geospatial Consortium]] for serving, viewing, or editing georeferenced map images and geographical features over the internet or Intranet using platform-independent calls.+Web Map Service (WMS), Web Map Tile Services (WMTS), and Web Feature Service (WFS) are the standard protocols of the Open Geospatial Consortium for serving, viewing, or editing georeferenced map images and geographical features over the internet or Intranet using platform-independent calls.
  
-A WMS, WMTS serves georeference map data onlyA WFS returns both spatial features and attributesThis makes it possible to use a WFS dataset for spatial analyses, attribute viewing, and if allowed to edit and update the dataset.+More information:  
 +  * https://en.wikipedia.org/wiki/Web_Map_Service 
 +  * https://en.wikipedia.org/wiki/Web_Map_Tile_Service 
 +  * https://en.wikipedia.org/wiki/Web_Feature_Service
  
-More information :  +==== Supported Versions ====
-  * [[http://en.wikipedia.org/wiki/Web_Map_Service|Wikipedia Web Map Service]] +
-  * [[http://en.wikipedia.org/wiki/Web_Map_Tile_Service|Wikipedia Web Map Tile Service]] +
-  * [[http://en.wikipedia.org/wiki/Web_Feature_Service|Wikipedia Web Feature Service]]+
  
-=== Setup Connection ===+Orbit supports Web services as described by the OGC: 
 +  * https://ogc.org/standards/wms 
 +  * https://ogc.org/standards/wmts 
 +  * https://ogc.org/standards/wfs
  
-Orbit provides 2 options to connect and load a web service layer. We highly recommend the first option, using a file-based connection :+=== Supported versions ===
  
-**Web service resource connection file** \\ 
-Filed based connection to one specific layer of a well-defined web service. 
-  * [[dev:technology:supported_formats:image:owxs|]]. 
- 
-**Resource Browser service connection** \\ 
-Establish the Web service connection and add one or more available web service resources. \\ 
-This user interface method is useful for the initial testing of a service and its resources. 
- 
-{{orbitgis:how_to_find.png?25&nolink |}} 
-  * Orbit desktop : [[dev:desktop:workspace:resource_library|Library]] > Web 
-  * Orbit EOS server : [[dev:server:console:resources:datasets_setup|]] 
- 
-=== Supported Versions === 
- 
-Orbit supports Web services as described by the OGC : 
-  * www.opengeospatial.org/standards/wms 
-  * www.opengeospatial.org/standards/wmts 
-  * www.opengeospatial.org/standards/wfs 
- 
-Currently, Orbit supports : 
   * WMS versions 1.1.0, 1.1.1 and 1.3.0   * WMS versions 1.1.0, 1.1.1 and 1.3.0
   * WMTS version 1.0.0   * WMTS version 1.0.0
-  * WFS versions 1.1.0, the support of version 2.0 is on our wishlist. Let us know if you are interested+  * WFS versions 1.1.0, 2.0.
 + 
 +=== Remarks ===
  
-Remarks : 
   * View only (WFS) \\ WFS support is limited to view only for both spatial and attribute components. \\ Editing or updating WFS features and styling is not supported. \\ Via a file-based connection an Orbit legend can be defined.    * View only (WFS) \\ WFS support is limited to view only for both spatial and attribute components. \\ Editing or updating WFS features and styling is not supported. \\ Via a file-based connection an Orbit legend can be defined. 
   * Supported object types (WFS) \\ Orbit's engine supports only the vector-based variant of the following WFS Object types: \\ Point, MultiPoint, LineString, MultiLineString, Curve, MultiCurve, Surface, MultiSurface, Polygon, MultiPolygon   * Supported object types (WFS) \\ Orbit's engine supports only the vector-based variant of the following WFS Object types: \\ Point, MultiPoint, LineString, MultiLineString, Curve, MultiCurve, Surface, MultiSurface, Polygon, MultiPolygon
   * Internal resource name \\ No point "." characters allowed in web resource internal name. \\  Check the internal name via [[dev:desktop:dataset:general|Dataset Properties > General > Dataset]] : <Orbit web service name>.<internal web service resource name> . \\ If the internal name contains one or more points then the resource cannot be used.   * Internal resource name \\ No point "." characters allowed in web resource internal name. \\  Check the internal name via [[dev:desktop:dataset:general|Dataset Properties > General > Dataset]] : <Orbit web service name>.<internal web service resource name> . \\ If the internal name contains one or more points then the resource cannot be used.
  
-=== WebService CRS and Orbit Map CRS ===+===Orbit Connection to WebService ====
  
-The Orbit Map CRS will be used to define the Bounding Box of the GetMap WebService map request. To avoid issues like map misalignment due coordinate transformations, set the Orbit Map CRS to a WebService supported coordinate system. \\+There are 2 options to establish a connection to a WebService: 
 + 
 +=== File-based WebService Configuration === 
 + 
 +Establish the connection using an Orbit configuration file to a well-defined WebService Layer. \\  
 +This file-based configuration is supported by all products and today's recommended solution.  
 + 
 +More information, see [[dev:technology:supported_formats:image:owxs|]]. 
 + 
 +==== WebService CRS and Orbit Map CRS ==== 
 + 
 +The Orbit Map CRS will be used to define the Bounding Box of the GetMap WebService map request. To avoid issues related to coordinate transformations, it is advised to set the Orbit Map CRS to a WebService supported coordinate system. \\
 More information about Orbit Map and Dataset CRS, see [[dev:technology:core:crs|]]. More information about Orbit Map and Dataset CRS, see [[dev:technology:core:crs|]].
  
-=== WebServices in Html5 WebViewer ===+==== WebService in Orbit 3DM Viewer ====
  
-Special attention is required to use WMS and WMTS layers in the Orbit 3DM Viewer, see [[dev:technology:supported_formats:image:otm_for_wms|]].+Special attention is required to use WMS and WMTS layers in the Orbit 3DM Viewer. \\  
 +More information, see [[dev:technology:supported_formats:image:otm_for_wms|]].
  
 ===== Tiled Map Service ===== ===== Tiled Map Service =====
  
-Orbit supports pyramid-based tile services as made popular by OpenStreetMap. \\ +Tiled Map Services (TMS) are made popular by Google and OpenStreetMap. \\
 More information, see [[https://en.wikipedia.org/wiki/Tiled_web_map|Tiled web map]]. More information, see [[https://en.wikipedia.org/wiki/Tiled_web_map|Tiled web map]].
  
-=== Setup Connection ===+==== Supported Versions ====
  
-web service resource connection file +The common standards and custom pyramid-based tile services are supported by Orbit. 
  
-**Tiled map resource connection file** \\ +==== Orbit Connection to Tiled Map Service ====
-Configure the tiled map service connection and the web resource to load, cfr web services (see above). +
-  * [[dev:technology:supported_formats:image:otm|]]+
  
-===== SSL Security Certificates =====+There is only 1 option to establish a connection to a Tiled Map Service. 
  
-When loading web resources via a secured HTTPS connection, the website's Security Certificate must be available to the Oracle's Java Runtime Engine used by Orbit. \\  +=== File-based Tiled Map Configuration === 
-More information, see [[dev:technology:platforms:java_keystore|]].+
  
-===== Network connectivity =====+Establish the connection using an Orbit configuration file to a well-defined Tiled Map Layer, see [[dev:technology:supported_formats:image:otm|]].
  
-To use a Web-based resource a successful connection to the providing server/service is required.  +===== IT Troubleshooting =====
  
-If no network connection could be established, obviously Orbit will not be able to load the resource. Review the documentation below on how to check the connection from the local network to the web service.+This paragraph documents common IT issues related to loading web resources.  
 + 
 +==== SSL Trusted Authority ==== 
 + 
 +When loading web resources via a secured HTTPS connection, the website's Security Certificate must be available to the Java Runtime Engine used by Orbit. \\  
 +If the certificate is not known to the Java Runtime Engine, the following message is printed in the [[dev:technology:platforms:logfiles|Orbit logfile]]: 
 +  javax.net.ssl.SSLHandshakeException:  
 +  sun.security.validator.ValidatorException: PKIX path building failed 
 +  sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target 
 + 
 +For more information and how to solve it, see [[dev:technology:platforms:java_keystore|]]. 
 + 
 +==== SSL Mixed Content ==== 
 + 
 +==== Network connectivity ==== 
 + 
 +To use a Web-based resource a successful network connection to the providing server/service is required. \\ 
 +If no connection could be established, obviously Orbit will not be able to load the resource. Review the documentation below on how to check the connection from the local network to the web service.
  
 If a network connection is successful, but Orbit can't load resources, most probably the Orbit application is not allowed to get online/network access due to an internal internet security application (e.g. aXsGUARD Gatekeeper from Vasco). The network and/or local computer administrator need to adjust your security settings or configure a proxy to be used by Orbit :  If a network connection is successful, but Orbit can't load resources, most probably the Orbit application is not allowed to get online/network access due to an internal internet security application (e.g. aXsGUARD Gatekeeper from Vasco). The network and/or local computer administrator need to adjust your security settings or configure a proxy to be used by Orbit : 
   * Orbit desktop standalone : [[inhouse:orbit:config|]].   * Orbit desktop standalone : [[inhouse:orbit:config|]].
-  * Orbit Server and Orbit desktop Client : [[dev:server:eos:service|]].+  * Orbit Server and Orbit desktop Client : [[dev:publisher:orbit_eos_service|]].
  
 === Check Local network - Service connection === === Check Local network - Service connection ===
Line 92: Line 101:
 In the example below a connection to the OpenStreetMap service is tested : In the example below a connection to the OpenStreetMap service is tested :
  
-**Successful connection** \\ +  * Successful connection \\ {{:technologies:resources:otm_test_successful.png?nolink|}} 
-{{:technologies:resources:otm_test_successful.png?nolink|}} +  * Failed connection \\ {{:technologies:resources:otm_test_not_successful.png?nolink|}}
- +
-**Failed connection** \\ +
-{{:technologies:resources:otm_test_not_successful.png?nolink|}}+
 
Last modified:: 2021/01/12 16:36