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:supported_formats:image:owxs [2018/06/04 13:06]
andrei.efimov@orbitgt.com
dev:technology:supported_formats:image:owxs [2023/10/06 16:56] (current)
mihaela [Create]
Line 2: Line 2:
  
 An Orbit Web service resource connection file is a file reference to one specific layer of a well defined web service. \\ An Orbit Web service resource connection file is a file reference to one specific layer of a well defined web service. \\
-It is advised to read first the documentation about [[technology:core_concepts:web_resources|]].+It is advised to read first the documentation about [[dev:technology:core:web_resources|]].
  
 Connection file by web service type :  Connection file by web service type : 
Line 8: Line 8:
   * *.owmts : Orbit Web Map Tile Service   * *.owmts : Orbit Web Map Tile Service
   * *.owfs : Orbit Web Feature Service   * *.owfs : Orbit Web Feature Service
-  * *.otm : Orbit Tiled Map Service 
  
-=== Structure ===+===== Structure =====
  
 An Orbit Web service resource connection file has the following structure: An Orbit Web service resource connection file has the following structure:
Line 18: Line 17:
   * ''ServerName'' : Free of choice, but do not use "." character. Web service name as labeled in Orbit.   * ''ServerName'' : Free of choice, but do not use "." character. Web service name as labeled in Orbit.
   * ''ServerURL'' : service url   * ''ServerURL'' : service url
-  * ''MapURL'' :  map url, including "?". Do not append "REQUEST=GetCapabilities" (only for .otm). 
   * ''DataSetName'' : <layer name> or <layer order reference>   * ''DataSetName'' : <layer name> or <layer order reference>
     * <layer name> : Value of service FeatureType Name tag in the FeatureTypeList.     * <layer name> : Value of service FeatureType Name tag in the FeatureTypeList.
     * <layer order reference> : "[i]", "i" is the order of the layer it the web service FeatureTypeList. (only for OWFS).     * <layer order reference> : "[i]", "i" is the order of the layer it the web service FeatureTypeList. (only for OWFS).
-  * ''Layer'' : <layer name> (only for .otm) 
-    * <layer name> Value of service FeatureType Name tag in the FeatureTypeList 
-  * ''PixelSize'' : the maximum-detail size of the pixels to render. If this is 0.0 the 'resx' or 'resy' attribute of the layer bounding box will be checked, but these are optional attributes so do not depend on them to be present on each server. In a metric CRS a value of 0.25 will result in 25 centimeter pixels.The OTM driver will use the pixel size and layer bounding box to create a pyramid of 256x256 pixel tiles. These tiles are cached in memory to speed up rendering. (only for .otm) 
  
 Optional configurations Optional configurations
Line 31: Line 26:
   * ''swap_axis'' : Comma separated list of EPSG codes. Set list of CRS for map requests coordinates need to be inverted.    * ''swap_axis'' : Comma separated list of EPSG codes. Set list of CRS for map requests coordinates need to be inverted. 
   * ''PreferredCRS'' : EPSG Code. Set fix CRS for all web service communication and map requests. (Only for OWMTS)   * ''PreferredCRS'' : EPSG Code. Set fix CRS for all web service communication and map requests. (Only for OWMTS)
-  * ''StaticContent'' :  ''true'' or ''false'', default false. (Only for OWFS) \\ If true, then all features are loaded at once  and saved in memory. The initial feature request will take more time, but once loaded there are no more web requests needed. This setting perfect for smaller and static wfs layers to avoid continious time consuming web requests. \\ If false, then features are loaded on-the-fly as needed corresponding the map view. Setting for larger and/or dynamic wfs layers. +  * ''StaticContent'' :  ''true'' or ''false'', default false. (Only for OWFS) \\ If true, then all features are loaded at once and saved in memory. The initial feature request will take more time, but once loaded there are no more web requests needed. This setting is perfect for smaller and static WFS layers to avoid continuous time-consuming web requests. \\ If false, then features are loaded on-the-fly as needed corresponding to the map view. Setting for larger and/or dynamic WFS layers. 
   * ''FallbackGeometryPropertyType'' : ''PointPropertyType'', ''LineStringPropertyType'' or ''PolygonPropertyType'' (Only for OWFS) \\ Specification of the feature's spatial type (geometry) is mandatory only if the service is not specifying the geometry or identifying the spatial type as generic geometry.   * ''FallbackGeometryPropertyType'' : ''PointPropertyType'', ''LineStringPropertyType'' or ''PolygonPropertyType'' (Only for OWFS) \\ Specification of the feature's spatial type (geometry) is mandatory only if the service is not specifying the geometry or identifying the spatial type as generic geometry.
-  * ''ImageFormat'': specification of the tiles image format is mandatory if the tiles format is not .png as Orbit expects by default .png format; <image format> Value of service FeatureType Format tag in the FeatureTypeList (only for .otm)+  * ''Is3D''''true'' or ''false'', setting to request 2D or 3D vector features, default false (Only for OWFS). 
 +  * ''IgnoreDCP'':  ''true'' or ''false'', setting to ignore the post requests URLs as specified in the service's capabilities file. Orbit will use the capabilities URL for all requestsDefault false. 
 +  * ''UpdateMode'': ''READONLY'' or ''FULL_CONTROL'' for WFS-T, default is ''FULL_CONTROL''
  
-=== Reason to use ===+ 
 +===== Reason to use =====
  
 A Web Service reference file simplifies use of Web resources and enables additional configurations : A Web Service reference file simplifies use of Web resources and enables additional configurations :
   * Manage and share web resource in the same way as regular, file based resources.   * Manage and share web resource in the same way as regular, file based resources.
-  * Associate an [[technology:supported_formats:other:olg|Orbit Legend file]]. +  * Associate an [[dev:technology:supported_formats:other:olg|Orbit Legend file]]. 
   * Set additional service configurations, see Structure.    * Set additional service configurations, see Structure. 
  
-=== Create ==+===== Create =====
- +
-Create and edit the .owfs, .owms .owmts and .otm files using a simple text editor (e.g. Notepad).  Take care of spelling and file syntax. +
- +
-=== Examples === +
- +
-** Belgium Informatie Vlaanderen Ortho ** \\ +
-https://overheid.vlaanderen.be/Webdiensten-Raadpleegdiensten \\ +
-https://geoservices.informatievlaanderen.be/raadpleegdiensten/omwrgbmrvl/wms?service=wms&request=getcapabilities \\ +
-{{:technology:supported_formats:image:informatievlaanderen_ortho_.zip|}} +
- +
- +
-Example .owms file: +
-<code> +
-ServerType WMS +
-ServerName informatievlaanderen_omwrgbmrvl +
-ServerURL https://geoservices.informatievlaanderen.be/raadpleegdiensten/omwrgbmrvl/wms? +
-DataSetName Ortho +
-</code> +
- +
-Example .owfs file: +
-<code> +
-ServerType WFS +
-ServerName informatievlaanderen_vrbg +
-ServerURL Https://geoservices.informatievlaanderen.be/overdrachtdiensten/Vrbg/wfs?+
-DataSetName VRBG:Refarr +
-StaticContent true +
-</code> +
- +
-Example .otm file: +
-<code> +
-Format=WMS +
-MapUrl=https://geoservices.informatievlaanderen.be/raadpleegdiensten/omwrgbmrvl/wms? +
-Layer=Ortho +
-CRS=31370 +
-PixelSize=0.5 +
-</code> +
- +
-https://tile.informatievlaanderen.be/ws/raadpleegdiensten/wmts?request=getcapabilities&service=wmts&version=1.0.0 \\ +
-{{:technology:supported_formats:image:informatievlaanderen_ortho_wmts.zip|}} +
- +
-Example .owmts file: +
-<code> +
-ServerType WMTS +
-ServerName informatievlaanderen_raadpleegdiensten_wmts +
-ServerURL http://tile.informatievlaanderen.be/ws/raadpleegdiensten/wmts? +
-DataSetName omwrgbmrvl +
-UserName  +
-Password  +
-PreferredCRS 31370 +
-</code> +
- +
-http://geoservices.informatievlaanderen.be/overdrachtdiensten/GRB/wfs?service=wms&request=getcapabilities \\ +
-{{:technology:supported_formats:image:informatievlaanderen_grb_gbg.zip|}} +
- +
-Example .owfs file: +
-<code> +
-ServerType WFS +
-ServerName informatievlaanderen_grb +
-ServerURL http://geoservices.informatievlaanderen.be/overdrachtdiensten/GRB/wfs? +
-DataSetName [3] +
-</code> +
- +
-** Poland Geoportal Orto ** \\ +
-http://www.geoportal.gov.pl/uslugi/usluga-przegladania-wms \\ +
-http://mapy.geoportal.gov.pl/wss/service/img/guest/ORTO/MapServer/WMSServer?service=wms&request=getcapabilities \\ +
-{{:technology:supported_formats:image:poland_geoportal_orto.zip|}}+
  
-Example .owms file: +Create and edit the .owfs, .owms and .owmts files using a simple text editor (e.g. Notepad).  Take care of spelling and file syntax.
-<code> +
-ServerType WMS +
-ServerName mapy_geoportal_gov_pl_orto +
-ServerURL http://mapy.geoportal.gov.pl/wss/service/img/guest/ORTO/MapServer/WMSServer +
-DataSetName Raster +
-swap_axis 4326,2180,2176,2177,2178,2179 +
-</code>+
  
-** US Geological Survey ** \\ +Exemples of owfs configurations > to be saved in a .owfs file \\ 
-https://www.usgs.gov/ \\ +''ServerType:WFS \\ 
-https://isse.cr.usgs.gov/arcgis/services/Orthoimagery/USGS_EROS_Ortho_1Foot/ImageServer/WMSServer?service=wms&request=getcapabilities \\ +ServerURL:https://msdi.data.gov.mt/geoserver/MITA_WFS_SR_GeoSubArea/wfs \\ 
-{{:technology:supported_formats:image:usgs_eros_ortho_1foot.zip|}}+ServerName:geoserver \\ 
 +DataSetName:MITA_WFS_SR_GeoSubArea:SR.SeaArea.GSA15.WFS \\ 
 +PreferredCRS:3045'' \\
  
-Example .owms file+Exemples of owms configurations > to be saved in a .owms file \\ 
-<code> +''ServerType=WMS \\ 
-ServerType WMS +ServerName=wms.geo.gr.ch \\ 
-ServerName USGS_EROS_Ortho +ServerURL=https://wms.geo.gr.ch/kstn_strassenentwaesserung?Service=WMS&Request=GetCapabilities&Version=1.0.0 \\ 
-ServerURL https://isse.cr.usgs.gov/arcgis/services/Orthoimagery/USGS_EROS_Ortho_1Foot/ImageServer/WMSServer +DataSetName=Eigentuemer_Belagsschale''\\
-DataSetName USGS_EROS_Ortho_1Foot +
-</code>+
  
-** US Nasa Earth Observation ** \\ 
-https://neo.sci.gsfc.nasa.gov/ \\ 
-https://neo.sci.gsfc.nasa.gov/wms/wms?service=wms&request=getcapabilities \\ 
  
-Example .owms file: 
-<code> 
-ServerType WMS 
-ServerName NEO 
-ServerURL https://neo.sci.gsfc.nasa.gov/wms/wms 
-DataSetName SRTM_RAMP2_TOPO 
-</code> 
 
Last modified:: 2018/06/21 08:13