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 17:40] jeroen [Web Map and Web Feature Services] |
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:// | + | 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. |
More information: | More information: | ||
Line 20: | Line 20: | ||
* https:// | * https:// | ||
- | === Current supported | + | === Supported |
* 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 === | ||
Line 36: | Line 36: | ||
There are 2 options to establish a connection to a WebService: | There are 2 options to establish a connection to a WebService: | ||
- | === File-based WebService | + | === File-based WebService |
Establish the connection using an Orbit configuration file to a well-defined WebService Layer. \\ | Establish the connection using an Orbit configuration file to a well-defined WebService Layer. \\ | ||
- | This file-based configuration supported by all products and today' | + | This file-based configuration |
- | * [[dev: | + | More information, |
- | + | ||
- | === Legacy WebService Connection === | + | |
- | + | ||
- | Establish the connection using the Legacy Orbit Desktop Resource Library or Orbit EOS Console user interface, and add runtime one or more WebService Layers. \\ | + | |
- | This legacy approach is not supported in the 3DM Publisher Console and 3DM Viewer. | + | |
- | + | ||
- | * Orbit desktop : [[dev: | + | |
- | * Orbit EOS server : [[dev: | + | |
==== WebService CRS and Orbit Map CRS ==== | ==== WebService CRS and Orbit Map CRS ==== | ||
Line 58: | Line 50: | ||
==== WebService in Orbit 3DM Viewer ==== | ==== WebService in Orbit 3DM Viewer ==== | ||
- | Special attention is required to use WMS and WMTS layers in the Orbit 3DM Viewer, see [[dev: | + | Special attention is required to use WMS and WMTS layers in the Orbit 3DM Viewer. \\ |
+ | 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 95: | 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 17:40