Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
dev:technology:core:web_resources [2021/01/12 16:28] jeroen |
dev:technology:core:web_resources [2023/10/06 09:10] (current) jeroen [IT Troubleshooting] |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Web-based Resources ====== | ====== Web-based Resources ====== | ||
- | Web-based | + | This portal page provides access to all documentation related to support for web-based resources. \\ |
Orbit supports Web Map Services, Web Map Tile Services, Web Feature Services, and Tile Map Services. | Orbit supports Web Map Services, Web Map Tile Services, Web Feature Services, and Tile Map Services. | ||
===== 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:// | + | 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 only. A WFS returns both spatial features and attributes. This 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/ | ||
+ | * https://en.wikipedia.org/ | ||
+ | * https:// | ||
- | More information : | + | ==== Supported Versions ==== |
- | * [[http:// | + | |
- | * [[http:// | + | |
- | * [[http:// | + | |
- | === Setup Connection === | + | Orbit supports Web services as described by the OGC: |
+ | * https:// | ||
+ | * https:// | ||
+ | * https:// | ||
- | 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: | ||
- | |||
- | **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: | ||
- | * Orbit desktop : [[dev: | ||
- | * Orbit EOS server : [[dev: | ||
- | |||
- | === Supported Versions === | ||
- | |||
- | Orbit supports Web services as described by the OGC : | ||
- | * www.opengeospatial.org/ | ||
- | * www.opengeospatial.org/ | ||
- | * www.opengeospatial.org/ | ||
- | |||
- | 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, | + | * WFS versions 1.1.0, 2.0.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' | * Supported object types (WFS) \\ Orbit' | ||
* Internal resource name \\ No point " | * Internal resource name \\ No point " | ||
- | === 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 | + | 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' | ||
+ | |||
+ | More information, | ||
+ | |||
+ | ==== 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 | ||
More information about Orbit Map and Dataset CRS, see [[dev: | More information about Orbit Map and Dataset CRS, see [[dev: | ||
- | === WebServices | + | ==== WebService |
- | Special | + | Special |
+ | More information, see [[dev: | ||
===== 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, | More information, | ||
- | === 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 |
- | Configure the tiled map service connection and the web resource | + | |
- | * [[dev: | + | |
- | ===== 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' | + | === File-based Tiled Map Configuration === |
- | More information, | + | |
- | ===== Network connectivity ===== | + | Establish the connection using an Orbit configuration file to a well-defined Tiled Map Layer, see [[dev: |
- | To use a Web-based resource a successful connection to the providing server/ | + | ===== IT Troubleshooting ===== |
- | If no network connection could be established, | + | 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' | ||
+ | If the certificate is not known to the Java Runtime Engine, the following message is printed in the [[dev: | ||
+ | javax.net.ssl.SSLHandshakeException: | ||
+ | sun.security.validator.ValidatorException: | ||
+ | sun.security.provider.certpath.SunCertPathBuilderException: | ||
+ | |||
+ | For more information and how to solve it, see [[dev: | ||
+ | |||
+ | ==== SSL Mixed Content ==== | ||
+ | |||
+ | ==== Network connectivity ==== | ||
+ | |||
+ | To use a Web-based resource a successful | ||
+ | If no connection could be established, | ||
If a network connection is successful, but Orbit can't load resources, most probably the Orbit application is not allowed to get online/ | If a network connection is successful, but Orbit can't load resources, most probably the Orbit application is not allowed to get online/ | ||
* Orbit desktop standalone : [[inhouse: | * Orbit desktop standalone : [[inhouse: | ||
- | * 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** \\ | + | |
- | {{: | + | * Failed connection \\ {{: |
- | + | ||
- | **Failed connection** \\ | + | |
- | {{: | + |
Last modified:: 2021/01/12 16:28