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 [2017/06/08 18:47] jve@orbitgt.com |
dev:technology:core:web_resources [2023/10/06 09:10] (current) jeroen [IT Troubleshooting] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Web Based Resources ====== | + | ====== Web-based |
- | Web based resources are commonly used for online serving of GIS data, both for vector and image resources. \\ | + | 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 Services===== | + | ===== Web Map and Web Feature |
- | 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 attribute | + | More information: |
+ | * https:// | ||
+ | * https:// | ||
+ | * https://en.wikipedia.org/ | ||
- | 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 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. \\ | + | * WMTS version 1.0.0 |
- | [[technology: | + | * WFS versions 1.1.0, 2.0.0 |
- | **Resource Browser service connection** \\ | + | === Remarks === |
- | Establish the Web service connection and add one ore more available web service resources. \\ | + | |
- | This user interface method is useful for initial testing of a service and its resources. | + | |
- | {{orbitgis: | + | * 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. |
- | * Orbit desktop | + | * Supported object types (WFS) \\ Orbit's engine supports only the vector-based variant of the following WFS Object types: \\ Point, MultiPoint, LineString, MultiLineString, |
- | * Orbit EOS server : [[171:server:console:resources: | + | * Internal resource name \\ No point " |
+ | ==== Orbit Connection to WebService ==== | ||
- | === Supported Versions === | + | There are 2 options to establish a connection to a WebService: |
- | Orbit supports Web services as described by the OGC : | + | === File-based WebService Configuration === |
- | * www.opengeospatial.org/ | + | |
- | * www.opengeospatial.org/ | + | |
- | * www.opengeospatial.org/ | + | |
- | Currently | + | Establish the connection using an Orbit configuration file to a well-defined WebService Layer. \\ |
- | * WMS versions 1.1.0, 1.1.1 and 1.3.0 | + | This file-based configuration |
- | * 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. | + | |
- | Remarks : | + | More information, see [[dev:technology:supported_formats:image:owxs|]]. |
- | * View only (WFS) \\ WFS support is limited to view only for both spatial and attribute component. \\ 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' | + | |
- | * Internal resource name \\ No point " | + | |
- | === WebService CRS and Orbit Map CRS === | + | ==== 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 | + | 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 [[technology: | + | More information about Orbit Map and Dataset CRS, see [[dev:technology:core:crs|]]. |
- | === Examples | + | ==== WebService in Orbit 3DM Viewer ==== |
- | No username and password | + | Special attention is required |
+ | More information, | ||
- | WMS | ||
- | * http:// | ||
- | * http:// | ||
- | * http:// | ||
- | * http:// | ||
- | |||
- | WFS | ||
- | * http:// | ||
- | * http:// | ||
===== 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 | + | |
- | **Tiled map resource connection file** \\ | + | The common standards |
- | Configure the tiled map service connection | + | |
- | * [[technology: | + | |
- | ===== Network connectivity ===== | + | |
- | To use a Web based resource a successful connection | + | ==== Orbit Connection |
- | If no network connection could be established, | + | There is only 1 option |
- | If a network connection is successful, but Orbit can't load resource, most probably the Orbit application is not allowed to get online/ | + | === File-based Tiled Map Configuration === |
+ | |||
+ | Establish the connection using an Orbit configuration file to a well-defined Tiled Map Layer, see [[dev: | ||
+ | |||
+ | ===== IT Troubleshooting ===== | ||
+ | |||
+ | 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 network connection to the providing server/ | ||
+ | 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/ | ||
* Orbit desktop standalone : [[inhouse: | * Orbit desktop standalone : [[inhouse: | ||
- | * Orbit Server and Orbit desktop Client : [[171: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:: 2018/06/21 08:13