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 [2018/06/01 12:56] natalia.zheltukhina@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:// | + | |
- | ==== Web Services in HTML5 webclient ==== | + | Orbit supports |
+ | * https:// | ||
+ | * https:// | ||
+ | * https:// | ||
- | Direct connection to WMS\WMTS is not possible for HTML5 webclient. The OTM (Orbit TileMap) is an abstract image format that supports reading and rendering online image data.\\ | + | === Supported versions === |
- | It has several advantages in comparison with direct connection to a remote resource: | + | * WMS versions 1.1.0, 1.1.1 and 1.3.0 |
- | * Unlike direct connection it requests not just an image of a current window in rendered on-the-fly resolution but tiles of 256*256 pixels on a certain level of pyramid which allows both: faster rendering and cashing of loaded data. | + | * WMTS version 1.0.0 |
- | * Possibility to transform loaded tiles and visualize them in any Map CRS. | + | * WFS versions 1.1.0, 2.0.0 |
- | The following configuration parameters need to be defined in the ' | + | === Remarks |
- | < | + | |
- | Format=WMS | + | |
- | MapUrl=http:// | + | |
- | ImageFormat=image/jpg | + | |
- | Layer=p_1002800 | + | |
- | CRS=3011 | + | |
- | PixelSize=0.5 | + | |
- | </ | + | |
- | The following configuration parameters need to be defined | + | * View only (WFS) \\ WFS support is limited |
- | <code> | + | * Supported object types (WFS) \\ Orbit's engine supports only the vector-based variant of the following WFS Object types: \\ Point, MultiPoint, LineString, MultiLineString, |
- | Format=WMTS | + | * Internal resource name \\ No point " |
- | MapUrl=http://tile.informatievlaanderen.be/ | + | |
- | Layer=grb_bsk | + | |
- | PreferredCRS=31370 | + | |
- | UserName= | + | |
- | Password= | + | |
- | </code> | + | |
- | Parameters present in *.otm file: | + | ==== Orbit Connection |
- | * (Preferred)CRS should be chosen from the list of the projections enabled for the corresponding web service. If it's expected that the Map CRS mostly used for this data will be one of the enabled CRSs of the webservice then it's recommended | + | |
- | * Pixel size is used by OTM\WMS driver to create a pyramid of 256x256 pixel tiles, it also is a maximum detail size of the pixel to render (resolution of this abstract image). | + | |
- | <note tip> | + | There are 2 options |
- | For WMS server append "? | + | |
- | For WMTS append "? | + | |
- | \\ | + | |
- | example: | + | |
- | http:// | + | |
+ | === File-based WebService Configuration === | ||
- | === Setup Connection === | + | 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' | ||
- | Orbit provides 2 options to connect and load a web service layer. We highly recommend the first option, using a file based connection | + | More information, see [[dev:technology: |
- | **Web service resource connection file** \\ | + | ==== WebService CRS and Orbit Map CRS ==== |
- | Filed based connection to one specific layer of a well defined web service. | + | |
- | * [[technology: | + | |
- | **Resource Browser service connection** \\ | + | The Orbit Map CRS will be used to define |
- | Establish | + | More information about Orbit Map and Dataset CRS, see [[dev: |
- | This user interface method is useful for initial testing of a service | + | |
- | {{orbitgis: | + | ==== WebService in Orbit 3DM Viewer ==== |
- | * Orbit desktop : [[180: | + | |
- | * Orbit EOS server : [[180: | + | |
+ | Special attention is required to use WMS and WMTS layers in the Orbit 3DM Viewer. \\ | ||
+ | More information, | ||
- | === Supported Versions | + | ===== Tiled Map Service ===== |
- | Orbit supports Web services as described | + | Tiled Map Services (TMS) are made popular |
- | * www.opengeospatial.org/standards/wms | + | More information, |
- | * www.opengeospatial.org/standards/wmts | + | |
- | * www.opengeospatial.org/ | + | |
- | Currently Orbit supports : | + | ==== Supported Versions ==== |
- | * WMS versions 1.1.0, 1.1.1 and 1.3.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. | + | |
- | Remarks : | + | The common standards |
- | * View only (WFS) \\ WFS support is limited to view only for both spatial | + | |
- | * Supported object types (WFS) \\ Orbit' | + | |
- | * Internal resource name \\ No point " | + | |
- | === WebService CRS and Orbit Map CRS === | + | ==== Orbit Connection to Tiled Map Service ==== |
- | 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, | + | There is only 1 option |
- | More information about Orbit Map and Dataset CRS, see [[technology: | + | |
- | ===== Tiled Map Service ===== | + | === File-based |
- | Orbit supports pyramid-based tile services as made popular by OpenStreetMap. \\ | + | Establish the connection using an Orbit configuration file to a well-defined Tiled Map Layer, see [[dev: |
- | More information, | + | ===== IT Troubleshooting ===== |
- | === Setup Connection === | + | This paragraph documents common IT issues related to loading |
- | web service resource connection file | + | |
- | **Tiled map resource connection file** \\ | + | ==== SSL Trusted Authority |
- | Configure the tiled map service connection and the web resource to load, cfr web services (see above). | + | |
- | * [[technology: | + | |
- | ===== SSL Security Certificates ===== | + | |
- | When loading web resources via a secured | + | When loading web resources via a secured |
- | More information, see [[technology: | + | If the certificate is not known to the Java Runtime Engine, the following message is printed in the [[dev:technology: |
+ | javax.net.ssl.SSLHandshakeException: | ||
+ | sun.security.validator.ValidatorException: | ||
+ | sun.security.provider.certpath.SunCertPathBuilderException: | ||
- | ===== Network connectivity ===== | + | For more information and how to solve it, see [[dev: |
- | To use a Web based resource a successful connection to the providing server/ | + | ==== SSL Mixed Content ==== |
- | If no network connection could be established, | + | ==== Network connectivity ==== |
- | If a network connection is successful, but Orbit can't load resource, most probably the Orbit application is not allowed to get online/ | + | 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 : [[180: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 127: | 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