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 [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 Resources ======
  
-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 Servicesand Tile Map Services.
  
-===== Web 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 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, viewingor 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 information. 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/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]]+
  
-==== Web Services in HTML5 webclient ====+Orbit supports Web services as described by the OGC: 
 +  * https://ogc.org/standards/wms 
 +  * https://ogc.org/standards/wmts 
 +  * https://ogc.org/standards/wfs
  
-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 '.otm' file for WMS service: +=== Remarks ===
-<code> +
-Format=WMS +
-MapUrl=http://kartor.stockholm.se:80/bios/wms/app/baggis/web/WMS_STHLM_STOCKHOLMSKARTA_GRA_FORENKLAD_RASTER? +
-ImageFormat=image/jpg +
-Layer=p_1002800 +
-CRS=3011 +
-PixelSize=0.5 +
-</code>+
  
-The following configuration parameters need to be defined in the '.otmfile for WMTS service+  * 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.  
-<code> +  * 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 
-Format=WMTS +  * 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.
-MapUrl=http://tile.informatievlaanderen.be/ws/raadpleegdiensten/wmts? +
-Layer=grb_bsk +
-PreferredCRS=31370 +
-UserName= +
-Password= +
-</code>+
  
-Parameters present in *.otm file: +==== Orbit Connection to WebService ====
-  * (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 to use it to avoid extra transformations as this is the CRS in which tiles will be rendered in. +
-  * 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>Check the capabilities document of the WM(T)S server to find the right parameter values.\\ +There are 2 options to establish a connection to a WebService:
-For WMS server append "?REQUEST=GetCapabilities" to the URL to download this xml document.\\ +
-For WMTS append "?Service=WMTS&Request=GetCapabilities&Version=1.0.0" to the URL to download this xml document.\\ +
-\\ +
-example:\\ +
-http://maps.wien.gv.at/basemap/1.0.0/WMTSCapabilities.xml?Service=WMTS&Request=GetCapabilities&Version=1.0.0</note>+
  
 +=== 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's recommended solution. 
  
-Orbit provides 2 options to connect and load a web service layer. We highly recommend the first optionusing a file based connection :+More informationsee [[dev:technology:supported_formats:image:owxs|]].
  
-**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:supported_formats:image:owxs|]].+
  
-**Resource Browser service connection** \\ +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. \\ 
-Establish the Web service connection and add one ore more available web service resources. \\ +More information about Orbit Map and Dataset CRS, see [[dev:technology:core:crs|]].
-This user interface method is useful for initial testing of a service and its resources.+
  
-{{orbitgis:how_to_find.png?25&nolink |}} +==== WebService in Orbit 3DM Viewer ====
-  * Orbit desktop : [[180:desktop:workspace:resource_library|Library]] > Web +
-  * Orbit EOS server : [[180:server:console:resources:datasets_setup|]]+
  
 +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|]].
  
-=== Supported Versions ===+===== Tiled Map Service =====
  
-Orbit supports Web services as described by the OGC : +Tiled Map Services (TMS) are made popular by Google and OpenStreetMap. \\ 
-  * www.opengeospatial.org/standards/wms +More information, see [[https://en.wikipedia.org/wiki/Tiled_web_map|Tiled web map]].
-  * www.opengeospatial.org/standards/wmts +
-  * www.opengeospatial.org/standards/wfs+
  
-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 and custom pyramid-based tile services are supported by Orbit. 
-  * 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's engine supports only the vector based variant of the following WFS Ojbect 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 [[180: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 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, set the Orbit Map CRS to a WebService supported coordinate system. \\ +There is only 1 option to establish a connection to a Tiled Map Service
-More information about Orbit Map and Dataset CRS, see [[technology:coordinate_systems:crs_orbit|]].+
  
-===== Tiled Map Service =====+=== File-based Tiled Map Configuration === 
  
-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:technology:supported_formats:image:otm|]].
  
-More information, see [[https://en.wikipedia.org/wiki/Tiled_web_map|Tiled web map]].+===== IT Troubleshooting =====
  
-=== Setup Connection === +This paragraph documents common IT issues related to loading web resources. 
-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:supported_formats:image:otm|]] +
-===== SSL Security Certificates =====+
  
-When loading web resources via a secured https connection, the website's Security Certificate must be available to the Oracle'Java Runtime Engine used by Orbit. \\  +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. \\  
-More informationsee [[technology:platforms:java_keystore|]].+If the certificate is not known to the Java Runtime Enginethe 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
  
-===== Network connectivity =====+For more information and how to solve it, see [[dev:technology:platforms:java_keystore|]].
  
-To use a Web based resource a successful connection to the providing server/service is required.  +==== SSL Mixed Content ====
  
-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 local network to web service.+==== 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/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 : +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 : 
   * Orbit desktop standalone : [[inhouse:orbit:config|]].   * Orbit desktop standalone : [[inhouse:orbit:config|]].
-  * 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** \\ +  * Successful connection \\ {{:technologies:resources:otm_test_successful.png?nolink|}} 
- +  * Failed connection \\ {{:technologies:resources:otm_test_not_successful.png?nolink|}}
-{{:technologies:resources:otm_test_successful.png?nolink|}} +
- +
-**Failed connection** \\ +
-{{:technologies:resources:otm_test_not_successful.png?nolink|}}+
 
Last modified:: 2018/06/21 08:13