Testare Si Evaluare Pagini Web Suport de Curs

Generation 1 Templates
Number Title
GeoMetOc - WMS 1.3 basic
GeoMetOc - WMS 1.3 basic with EPSG:4326

GeoMetOc - WMS 1.3 queryable
GeoMetOc - WMS 1.3 with TIME parameter (no span)

GeoMetOc - WMS 1.3 with TIME parameter (with spans)
GeoMetOc - WMS 1.3 layerstructure turn on/off layer

transparency
GeoMetOc - WMS updated layerlist
GeoMetOc - GeoTiff 8 bit - local data dissemination
GeoMetOc - GeoTiff 16 bit - local data dissemination
GeoMetOc - GRIB1 - local data dissemination - with I & j

GeoMetOc - GRIB1 - local data dissemination - without I & j
GeoMetOc - GRIB2 - local data dissemination
GeoMetOc - WMS-REP
GeoMetOc - WFS 2.0 basic
GeoMetOc - WFS 1.1 basic
GeoMetOc - WFS 2.0 cascading

GeoMetOc - WFS 2.0 Projections
GeoMetOc - WFS-T 2.0
GeoMetOc - WFS 2.0 with dynamic data

GeoMetOc - WFS 2.0 OGC filter
Objectives
The objective is to ensure that the provider is able to provide and the consumer is able to consume a WMS
according to the OGC basic WMS confirmance class
Provider provides a WMS supporting WMS basic, the service shall contain GeoMetOc information.
The WMS shall support a map projection according to the BBox of the data (other than EPSG:4326 - this is
managed by a separate test).
The EPSG codes shall be listed in the GetCapabilities response
The WMS shall be organised so that the service content is in a structure suitable for the end users.
The consumer finds the relevant WMS to use in this test by using the GeoMETOC portal. The GeoMETOC portal
shall provide all information needed to make sure the end users can identify the correct WMS.
The objective of this testcase is to ensure that the provider is able to provide and the consumer is able to consume
a WMS according to the OGC basic WMS, specifically for EPSG:4326.
Provider provides a WMS supporting WMS basic, the service shall contain GeoMetOc information.
The WMS service shall support EPSG:4326.

The WMS Service shall be organised so that the service content is in a structure suitable for the end users.
The objective is to ensure that the provider is able to provide and the consumer is able to consume a WMS
according to the OGC Queryable WMS conformance class.
Provider provides a WMS supporting WMS Queryable, the service shall contain GeoMetOc information.
The WMS shall support GetFeatureInfo requests to specific layers within the service.
The consumer finds the relevant WMS to use in this test by using the GeoMETOC portal. The GeoMETOC portal
shall provide all information needed to make sure the end users can identify the correct WMS.
a WMS containing information making use of the TIME parameter.
Provider provides a WMS containing temporal information to be used in this test.
The WMS shall support the WMS TIME dimension and advertise the available time slots in the capabilities
document (without using durations or validity periods) e.g.
<Dimension name="time" default="2018-02-19T19:00:00Z" units="ISO8601">2018-02-19T19:00:00.000Z,2018-02-
19T20:00:00.000Z,2018-02-19T21:00:00.000Z</Dimension>
The WMS shall be configured in such a way that clients can provide a TIME parameter in the GetMap request to
retrieve the temporal information.
The WMS shall support GetFeatureInfo requests to all layers within the service.
The WMS shall be organized so that the service content is in a structure suitable for the end users.
The WMS shall be configured so that "no data areas" in data sets can be returned as transparent areas in the WMS
GetMap Response.
*** Potential test case case to handle times with durations - To be confirmed ***
a WMS containing information making use of the TIME parameter e.g in as commonly used in with METOC layers.
Provider provides a WMS containing temporal information to be used in this test.
The WMS shall support the WMS TIME dimension and advertise the available time slots in the capabilities
document (with start/end/duration values) e.g.<Dimension name="time" default="2010-01-01T00:00:00Z"
units="ISO8601">
2010-01-01T00:00:00.000Z/2010-01-01T00:00:00.000Z/PT1S,2010-02-01T00:00:00.000Z/2010-02-
01T00:00:00.000Z/PT1S,2010-03-01T00:00:00.000Z/2010-03-01T00:00:00.000Z/PT1S</Dimension>
The WMS shall be configured in such a way that clients can provide a TIME parameter in the GetMap request to
retrieve the temporal information. The WMS shall support GetFeatureInfo requests to all layers within the service.
The WMS shall be organized so that the service content is in a structure suitable for the end users. The WMS shall
be configured so that "no data areas" in data sets can be returned as transparent areas in the WMS GetMap
Response.
The objective of this testcase is to ensure that the consumer's client is able to display layer structure and
transparency of a WMS correctly and to toggle on/off layers.
A single provider provides a WMS, the service shall contain GeoMetOc information.
The WMS Service shall contain a hierarchy of layers

The WMS Service shall be organised so that the service content is in a structure suitable for the end users.
The WMS Service shall be configured so that "no data areas" layers in data sets can be returned as transparent
areas in the WMS GetMap Response.
The objective of this testcase is to ensure that the consumers client adapts correctly to changes done by a WMS
provider.
Provider provides a WMS containing GeoMetOc information.
The objective of this testcase is to ensure that the provider is able to provide and the consumers can download
and use a provided raster file in GeoTiff 8 bit format.
Provider provides raster data (e.g. satellite images) in GeoTiff 8 bit format via HTTP download.
The objective of this testcase is to ensure that the provider is able to provide and the consumers can download
and use a provided raster file in GeoTiff 16 bit format.
Provider provides raster data (e.g. satellite images) in GeoTiff 16 bit format via HTTP download.
The objective of this testcase is to ensure that the provider is able to provide and the consumer can download and
use a provided file in GRIB1 format.
Provider provides MetOc data compliant with GRIB1 specification via HTTP download. The provided file will
specify the i and j direction increments, and flag accordingly in "octet 17".
use a provided file in GRIB format.
Provider provides MetOc data compliant with GRIB1 specification via HTTP download. The provided file will NOT
specify the i and j direction increments, and flag accordingly in "octet 17".
use a provided file in GRIB format.
Provider provides MetOc data compliant with GRIB2 specification via HTTP download.
a WMS containing the REP.
Provider provides a multilayered WMS containing environmental information to be used in this test.
The contained layers to be determined by REP Service Lead analysis of Joint Vignette/Scenario and made available
on the GeoMetOc Portal.
The WMS shall support GetFeatureInfo requests to specific layers within the service.
The WMS shall contain a hierarchy of layers
The WMS shall be organised so that the service content is in a structure suitable for the end users.
The WMS shall be configured so that "no data areas" in data sets can be returned as transparent areas in the WMS
GetMap Response.
a WFS 2.0 with basic functionality.
a WFS 1.1 with basic functionality.
The objective of this testcase is to ensure that the provider is able to cascade a WFS from a third party and the
consumer is able to consume it.
Provider republishes ("cascades") a WFS provided by a third party (e.g.NATO Core GIS). The Service should contain
at least point, line and polygon layers.
The objective of this testcase is to ensure that the provider is able to provide a WFS in different projections so that
the consumer does not have to do any reprojection on the received data.
Provider provides a WFS supporting at least these coordinate reference systems: EPSG:4326 (geographic projection
in WGS84)
EPSG:3395 (World Mercator)
EPSG:32627(UTM zone 27N) EPSG:32628 (UTM zone 28N) EPSG:32629 (UTM zone 29N) EPSG:32630 (UTM zone
30N) EPSG:32631 (UTM zone 31N) EPSG:32632 (UTM zone 32N) EPSG:32633 (UTM zone 33N) EPSG:32634 (UTM
zone 34N) EPSG:32635 (UTM zone 35N) EPSG:32636 (UTM zone 36N) EPSG:32637 (UTM zone 37N)
EPSG:32661 (WGS 84 / UPS North)
The objective of this testcase is to ensure that the provider is able to provide a WFS-T so that the consumer is able
to edit the data.
Provider provides a WFS that supports editing of the vector data according to the WFS-T (Transactional WFS)
specification.
WFS with dynamic data.
Provider provides a WFS serving dynamic data such as vehicle tracks.
Consumer consumes the service.

WFS using OGC filters.
Provider provides a WFS.

Keywords
*GeoMetoc Portal
*Geodata
*GeoMETOC
*single access point
*wms
*Service
*GeoMETOC
*epsg:4326
*Geodata
*Service
*GeoMetoc Portal
*wms
*wgs84
*GeoMetoc Portal
*Geodata
*GeoMETOC
*wms
*Service
*download
*GeoMetoc Portal
*Service
*GeoMETOC
*geotiff
*data dissimination
*Geodata
*download
*GeoMetoc Portal
*Service
*GeoMETOC
*geotiff
*data dissimination
*Geodata
*Service
*GeoMetoc Portal
*Geodata
*GeoMETOC
*wms
*Geodata
*wms
*GeoMetoc Portal
*GeoMETOC
*Service
*Geodata
*download
*GeoMETOC
*GeoMetoc Portal
*Service
*local data
*geotiff
*data dissimination
*Geodata
*download
*GeoMETOC
*GeoMetoc Portal
*Service
*local data
*geotiff
*data dissimination
*GeoMetOc
*Geodata
*GRIB 1/2
*Service
*GeoMetOc Portal
*GeoMetOc
*Geodata
*GRIB 1/2
*Service
*GeoMetOc Portal
*GeoMetOc
*Geodata
*GRIB 1/2
*Service
*GeoMetOc Portal
*Service
*rep
*GeoMetOc
*GeoMetOc Portal
*ogc
*wms
*Geodata
*Service
*Geodata
*GeoMetOc
*GeoMetOc Portal
*WFS
*feature
*WFS Access
*Service
*Geodata
*GeoMetOc
*GeoMetOc Portal
*WFS
*feature
*WFS Access
*NATO Core GIS

*Service
*GeoMetOc Portal
*WFS
*feature
*GeoMetOc
*Geodata
*cascading
*EPSG:32661 (WGS 84 / UPS
North)
*EPSG:32630 (UTM zone 30N)
*Service
*WFS
*feature
*EPSG:3395 (World Mercator)
*GeoMetOc Portal
*Geodata
*GeoMetOc
*projections
*EPSG:32627(UTM zone 27N)
*GeoMetOc Portal
*GeoMetOc
*editing
*update
*publish
*Service
*WFS-T
*Geodata
*transactional
*feature
*vector data
*GeoMetOc
*GeoMetOc Portal
*metoc
*feature
*WFS
*Service
*vehicle tracks
*dynamic data
*Geodata
*GeoMetOc
*WFS
*GeoMetOc Portal
*feature
*Service
*OGC filter
*Geodata
Pre-Conditions
The WMS shall support a map projection according to the BBox of the data.
The WMS shall be organised so that the service content is in a structure suitable for the end
users.
Steps
Step 1:The consumer finds the relevant WMS to use in this test by using the GeoMetOc portal. The
GeoMetOc portal shall provide all information needed to make sure the end users can identify the
correct WMS.
Step 2:The consumer connects to the WMS by copying either the URL endpoint or the
GetCapabilities URL response and displays the information.
Step 3:The consumer selects a layer from the WMS and loads it via a GetMap request.
Step 4: The consumer displays the retrieved layer.
correct WMS.
Step 3:The consumer selects a layer from the WMS and loads it via a GetMap request - specifically
using EPSG:4326.

correct WMS.
Step 3:The consumer selects a layer from the WMS and loads it via a GetMap request.
Step 5: The consumer querys the layer at a specific point, via a GetFeatureInfo request, and displays
the returned attributes.
correct WMS.
Result 1:see Validation Criteria
correct WMS.
Step 1: The consumer finds the relevant WMS to use in this test by using the GeoMetOc portal. The
correct WMS.
Step 2: The consumer connects to the WMS by copying either the URL endpoint or the
Step 3: The consumer toggles on/off of layers

correct WMS.
Step 3:After the client has successfully connected to and displayed the service, the provider will
add/remove/change layers in the service and the client will observe if the changes have taken place
Step 1:Consumer locates the link to download the file using the GeoMetOc portal.
Step 2:The consumer downloads the file.





correct WMS service.
Step 2:The consumer connects to the WMS through the web portal by copying either the URL
endpoint or the GetCapabilities response and displays the information.
Step 1:The consumer finds either the WFS endpoint or directly the WFS GetCapabilities URL for this
test by using the GeoMetOc portal. The GeoMetOc portal shall provide all information needed to
make sure the end users can identify the correct WFS.
Step 2: Consumer loads service onto client and is able to display and utilize vector data from the
WFS
Step 1:The consumer finds either the WFS endpoint or directly the WFS GetCapabilities URL for this
test by using the GeoMetOc portal. The GeoMetOc portal shall provide all information needed to
make sure the end users can identify the correct WFS.
Step 2: Consumer loads service onto client and is able to display and utilize vector data from the
WFS
Step 1:The Provider cascades a WFS from a third party and publishes the cascaded WFS on the
GeoMetOc portal with reference to the original WFS.
Step 2:The consumer finds the original WFS service and the cascaded version using the GeoMetOc
portal. The GeoMetOc portal shall provide all information needed to make sure the end users can
identify the correct WFS.
Step 3:Consumer consumes both WFS 2.0 services and compares them.
Consumer should compare and document differences in data and service performances and add as a
comment to the test results.
Step 1:The consumer finds the relevant WFS to use in this test by using the GeoMetOc portal. The
correct WFS.
Step 2:Consumer attempts to select and zoom to a specific WFS layer.

Step 1:The consumer finds the relevant WFS-T to use in this test by using the GeoMetOc portal. The
correct WFS-T.
Step 2:Consumer attempts to connect to the service and edit the published data.
Step 3: Consumer disconnects and then reconnects and is able to see the edited changes.
correct WFS.
Step 2:Consumer attempts to connect to the service and consume the dynamic data.
correct WFS.
Step 2:Consumer selects specific features from the WFS using OGC filter expressions.
Validation Criteria
SUCCESS:
* the consumer system shall be able to parse the GetCapabilities Request and receives a valid result
* the consumer system shall be able to retrieve a map based on a valid GetMap request
* the map shall be required in the valid EPSG Code.
LIMITED SUCCESS:
* Usability of the services is limited due to not intuitive or useful enough functionality
* minor technical issues occur, that can be handled by re-configuration on consumer side
* minor security issues occur, that can be handled by re-configuration on provider or consumer side, or within the network
INTEROPERABILITY ISSUE:
* usability of the WMS services is limitied by technical issues that can´t be handled by reasonable re-configuration on provider or
consumer side
* security issues occurs, that can't be handled by re-configuration on provider or consumer side, or within the network
SUCCESS:
* the consumer system shall be able to parse the GetCapabilities Request and receives a valid result
* the consumer system shall be able to retrieve a map based on a valid GetMap request
* the map shall be requested in EPSG:4326, no issues regarding x/y axis order shall occur
LIMITED SUCCESS:
* usability of the WMS is limitied by technical issues that can´t be handled by reasonable re-configuration on provider or
consumer side
* security issues occurs, that can't be handled by re-configuration on provider or consumer side* or within the network
* x/y axis are flipped
SUCCESS:
* the consumer system shall request "feature information" for the queried location
* the consumer system shall display the returned information in a legible way
LIMITED SUCCESS:
consumer side
SUCCESS:
* the operator of the consuming system should be able to connect to the service by copying either the service end point URL or
cutting relevant parts out of a copied GetCapabilities response. The client system shall allow the user to understand to what time
slot a specific result relates, based on the available time slots advertised in the capabilities document
* The consuming system shall request maps in desired EPSG code from the server, no re-projection shall be done on client side
* The consuming system shall support GetFeatureInfo request/response (interrogation of layer by clicking on the maps) and be
able to display GetFeatureInfo responses suitable for the operators. GFI response should be visible with units, The client system
shows a human readable name for the layers, based on the value of the layers Description tag. The client System shows "no data
areas" transparently.
LIMITED SUCCESS:
* The client does not respect the available time slots advertised in the capabilities document
consumer side
* The client provides no user interface for specifying the desired time slot at which to display the service
SUCCESS:
* the operator of the consuming system should be able to connect to the service by copying either the service end point URL or
cutting relevant parts out of a copied GetCapabilities response. The client system shall allow the user to understand to what time
slot a specific result relates, based on the available time slots advertised in the capabilities document
* The consuming system shall request maps in desired EPSG code from the server, no re-projection shall be done on client side
* The consuming system shall support GetFeatureInfo request/response (interrogation of layer by clicking on the maps) and be
able to display GetFeatureInfo responses suitable for the operators. GFI response should be visible with units, The client system
shows a human readable name for the layers, based on the value of the layers Description tag. The client System shows "no data
areas" transparently.
LIMITED SUCCESS:
* The client does not respect the available time slots advertised in the capabilities document
consumer side
* The client provides no user interface for specifying the desired time slot at which to display the service
SUCCESS:
* the client system reflects the layer structure of the services
* the client system supports turning on and off individual layers
* the client system is able to retrieve layers as transparent
LIMITED SUCCESS:
* usability of the services is limited due to not intuitive or useful enough functionality
* Hierarchical layer structures are "flattened" in the client
consumer side
SUCCESS:
* The layers in the clients ordinary map layer list is updated so that layers added on server side is added in client.
* Changed data content shows up in client after new GetMap request
LIMITED SUCCESS:
* minor technical issues occur, that can be handled by re-configuration on consumer side;
* minor security issues occur, that can be handled by re-configuration on provider or consumer side, or within the network.
Added layer on server side does not show up in client after re-configuration.
* usability of the WMS is limitied by technical issues that can´t be handled by reasonable re-configuration on provider or
consumer side
* security issues occurs; that can't be handled by re-configuration on provider or consumer side; or within the network.
SUCCESS:
* the operator of the consuming system is able to make the data be displayed in the consuming system
* consuming system displays the data correctly according to reference system, according to intructions provided by provider
* data can be used natively in GeoTIFF, no data conversion is carried out before display
LIMITED SUCCESS:
* the operator and/or system management of the consuming system needs additional support besides whats given by available
system documentation to make data displayed in the consuming system
* the system cannot download or display the data correctly
SUCCESS:
* consuming system displays the data correctly according to reference system, according to intructions provided by provider
* data can be used natively in GeoTIFF, no data conversion is carried out before display
LIMITED SUCCESS:
system documentation to make data displayed in the consuming system
SUCCESS:
* the display of the date appears to be accurate
* data can be used natively in GRIB1/2, no data conversion is carried out before display
LIMITED SUCCESS:
system documentation to make data displayed or used as an elevation data source in the consuming system
SUCCESS:
LIMITED SUCCESS:
SUCCESS:
LIMITED SUCCESS:
SUCCESS:
* the operator of the consuming system should be able to connect to the service by copying either the services end point URL or
cuting relevant parts out of a copied GetCapabilities response.
* The consuming system shall require maps in desired EPSG code from the server, no re-projection shall be done on client side
* The system shall support connecting to several OGC WMS at the same time,
* The client system reflects the layer structure of the services
* The client system supports turning on and off individual layers
* The client system shows a human readable name for the layers, based on the value of the layers Description tag.
* The client system shows "no data areas" transparently
* The layers in the clients ordinary map layer list is updated so that layers added on server side is added in client.
* Changed data content shows up in client after new GetMap request
LIMITED SUCCESS:
* minor technical issues occur, that can be handled by re-configuration on consumer side,
* Hierarchical layer structures are "flattened" in the client
* Added layer on server side does not show up in client after re-configuration
consumer side
SUCCESS:
* Consumer succesfully consumes the WFS without any issues, all available geographic data can be used.
LIMITED SUCCESS:
* A minor issue ocurrs, not being able to process all geographic data.
* no geographic data can be processed in the consuming system.
SUCCESS:
* Consumer succesfully consumes the WFS without any issues, all available geographic data can be used.
LIMITED SUCCESS:
* A minor issue ocurrs, not being able to process all geographic data.
* no geographic data can be processed in the consuming system.
SUCCESS:
* the cascaded WFS shall contain the layers and the features identical to the original WFS.
LIMITED SUCCESS:
* the cascaded WFS does not contain the layers and the features identical to the original WFS
Interoperability Issue:
* the cascaded WFS can't be processed and no layers are available.
SUCCESS:
* The consumer is able to retrieve the WFS layers in the specified projection without any errors.
LIMITED SUCCESS:
* Not all CRS can be retreived in the specified projection.
* The consumer is not able to retrieve WFS layers in the specified projection.
SUCCESS:
* Consumer can connect to the WFS-T
* Consumer can edit the attribute of the published features.
* Consumer can edit the geometries of the published features.
* Consumer can add new features.
* Consumer can remove features.
LIMITED SUCCESS:
* Consumer can connect to the WFS-T but some of the editing features listed above do not work.
* Consumer cannot connect to the WFS-T or is not able to do any form of editing.
SUCCESS:
* Consumer is able to consume the service in the consumer system. Updates to the dynamic information in the service (such as
new vehicle tracks) are automatically processed in the consumer system.
LIMITED SUCCESS:
* Consumer is able to consume the service in the consumer system, but limited manual steps are required to make updates to
the dynamic information in the service (such as new vehicle tracks) visible in the consumer system.
* Consumer cannot consume the service, or there is no easy way to refresh the dynamic information in the service.
SUCCESS:
* Consumers receive features matching the provided filter and is able to display them in the consumers system.
LIMITED SUCCESS:
* Consumer receives data that is not entirely conformant to provided filters, only some filters are interpreted and applied
correctly by the provider.
* Consumer cannot connect to the WFS, or no filtering is performed.
Information Products Standards Protocols Services
*Geospatial Data *WMS 1.3 *HTTP *Geospatial Services



*Geospatial Data *NISP Standard - *HTTP *Geospatial Services

GeoTIFF
*Geospatial Data *NISP Standard - *HTTP *Geospatial Services

GeoTIFF
*Geospatial Data *HTTP *Geospatial Services


*Geospatial Data *WFS 2.0 *HTTP *Geospatial Services
* WFS 1.1


Comments Providers
Support just one provider
Support just one provider
Explitly add version to title


Consumers
Generation
2 Templates
Number Title
GeoMetOc - WMS ELEVATION parameter
GeoMetOc - WMS map legend

GeoMetOc - JPEG2000 data dissemination
GeoMetOc - WCS 2.0 NetCDF
GeoMetOc - WCS 2.0 GRIB1
GeoMetOc - WCS 2.0 GRIB2

GeoMetOc - WMS 1.3 named styles
GeoMetOc - OGC GeoPackage Raster
GeoMetOc - KML
GeoMetOc - GML in JPEG2000
Objectives Keywords
The objective of this testcase is to ensure that the

provider provides a WMS capable of handling ELEVATION *elevation parameter
parameter (at least one layer for that dimension) and the *GeoMetOc
consumer is able to consume this service. *GeoMetoc Portal
*map
Consumer's WMS client attempts to consume this layer *Service
using this parameter. *WMS
*Geodata

provider provides a WMS that supports GetLegend *GeoMetOc
request for all published layers and the consumer is able *WMS
to display the legend. *Geodata
*map legend
*Service
*GeoMetoc Portal
provider is able to provide and the consumer can *Service
download and use a provided raster file in JPEG2000 *jpeg2000
format. *GeoMetoc Portal
*GeoMetOc
Provider provides raster data (e.g. satellite images) and *Geodata
elevation data in JPEG2000 format via HTTP download. *data dissemination

provider is able to provide and the consumer is able to *Service
consume a WCS containing MetOc data with NetCDF as an *Network Common Data
output format. Format
*wcs
Provider provides a WCS containing forecast data. *netcdf
*GeoMetOc
The provided service shall support NetCDFas an output *GeoMetoc Portal
format. *Geodata

provider is able to provide and the consumer is able to *GeoMetOc
consume a WCS containing MetOc data with GRIB1 as an *GeoMetoc Portal
output format. *Geodata
*Service
*wcs
*GRIB1

provider is able to provide and the consumer is able to *GeoMetOc
consume a WCS containing MetOc data with GRIB2 as an *GeoMetoc Portal
output format. *Geodata
*Service
*wcs
*GRIB2
consumer is able to make use of predefined named styles *GeoMetoc Portal
for the map display. *named styles
The service allows clients to choose between different *Geodata
styles of rendering. *GeoMetOc
*WMS
*Service
*map

provider is able to provide and the consumers can *Geodata
download and use a provided raster file in OGC *download
GeoPackage 1.2 format. *GeoMETOC
*GeoMetoc Portal
Provider provides raster data (e.g. satellite images) in *Service
OGC GeoPackage format via HTTP download. *single access point
*local data
*geopackage
*data dissimination

download and use a provided vector file in KML *download
(Keyhole Markup Language) format. *GeoMETOC
*GeoMetoc Portal
Provider provides vector data (e.g. points of interest) *Service
in KML format via HTTP download. *single access point
*local data
*kml
*data dissimination
download and use a provided JPEG2000-raster in *download
GML format. *GeoMETOC
*GeoMetoc Portal
Provider provides JPEG2000-raster data (e.g. satellite *Service
image) in GML format via HTTP download. *single access point
*local data
*gml
*jpeg2000
*data dissimination
Steps
Step 1:The consumer finds the relevant WMS to use in this test by using the GeoMetOc
portal. The GeoMetOc portal shall provide all information needed to make sure the end
users can identify the correct WMS.
Step 2:The consumer connects to the WMS through the web portal by copying either the
URL endpoint or the GetCapabilities response and displays the information.
Step 3:Consumer sends WMS GetMap requests that make use of the ELEVATION
parameter.
users can identify the correct WMS
Step 2:Consumer requests a map legend from the WMS

Step 1:The consumer finds the relevant data files to download for this test by using the
GeoMetOc portal. The GeoMetOc portal shall provide all information needed to make
sure the end users can identify the correct files to download.
Step 2:Consumer downloads the data and attempts to display it in the consumer system.
Step 1:The consumer finds the relevant WCS to use in this test by using the GeoMetOc
users can identify the correct WCS.
Step 2:The consumer connects to the WCS through the web portal by copying either the
URL endpoint or the GetCapabilities response, consumes the data, adds it as an forecast
data source and makes use of the information.
users can identify the correct WMS.
Step 2:Consumer attempts to consume the service and switch between the named styles.
Step 1:The consumer finds the relevant data files to download for this test by
using the GeoMetOc portal. The GeoMetOc portal shall provide all information
needed to make sure the end users can identify the correct files to download.
Step 2:Consumer downloads the data and displays it in the consumer system.
Validation Criteria
SUCCESS:
A WMS Layer is succesfully retrieved and its content is affected by ELEVATION parameter in a correct
fashion.
LIMITED SUCCESS:
Client is able to affect the returned map by providing ELEVATION, but the client and server do not agree
on the interpretation of these values
No WMS layer succesfully retrieved from the service, or WMS Layer is retrieved but is not affected by
ELEVATION parameter
SUCCESS:
* Consumer is able to request and display a map legend from the WMS. The legend contains symbols
describing areas, lines and points consistent with the portrayal of each object.
LIMITED SUCCESS:
* Not all layers are displayed in the legend or wrong symblogy is displayed.
* WMS does not provide legends
SUCCESS:
* the operator of the consuming system shall be able to use the GeoMetOc portal and find the correct
files to download for this test
* consumer is able to download the data
LIMITED SUCCESS:
* the system cannot download the data, other means must be used to distribute the data to the
consuming system
* the operator and/or system management of the consuming system needs support besides whats given
by available system documentation to make data displayed or used as an elevation data source in the
consuming system
* the system cannot display the data correctly
* the data can not be used as an elevation data source in the system, not even if technichal specialists are
available to re-configure/import the data
SUCCESS:
* The consumer system is able to connect to and retrieve data from the WCS in the offered format
* The retrieved data can be used to provide a forecast in the consumer system
LIMITED SUCCESS:
* The service has to be reconfigured in order to be usable in the consumer system
* The consumer system cannot make use of the WCS as a data source for forecasts.
SUCCESS:
LIMITED SUCCESS:
SUCCESS:
LIMITED SUCCESS:
SUCCESS:
Client is able to choose between different named styles
LIMITED SUCCESS:
Client is able to choose between different named styles, but switching between styles does not produce
the expected result.
WMS service does not provide named styles, or switching between styles is not possible in the client.
SUCCESS:
* the operator of the consuming system shall be able to use the GeoMetOc portal and find the
correct files to download for this test
* the operator of the consuming system is able to make the data be displayed in the consuming
system
LIMITED SUCCESS:
consuming system
* the operator and/or system management of the consuming system needs support besides
whats given by available system documentation to make data displayed or used as an elevation
data source in the consuming system
* the data can not be used as an elevation data source in the system, not even if technichal
specialists are available to re-configure/import the data
SUCCESS:
system
LIMITED SUCCESS:
consuming system
SUCCESS:
system
LIMITED SUCCESS:
consuming system
Information Products Standards Protocols Services

*Geospatial Data *NISP *HTTP *Geospatial Services
Standard -
JPEG 2000
*Geospatial Data *WCS 2.0 *HTTP *Geospatial Services

*Geospatial Data *OGC 12- *HTTP *Geospatial Services

128r12, OGC
GeoPackage
Encoding
Standard
Version 1.1,
04 August
2015

147r2,
Keyhole
Markup
Language
(KML) 2.2.0,
April 2008
047r3:
OpenGIS
GML in JPEG
2000 for
Geographic
Imagery
(GMLJP2)
Encoding
Specification
1.0.0,
January 2006
Comments Providers
Moved from generation 2, and

replaces #512
Consumers
SDI Templates
Title Objectives
Number
GeoMetOc - Portal - register web The objective of this testcase is to ensure that the
application via web page consumer is able to register and publish a web
application on the GeoMetOc portal.
Provider provides a portal, accessible from the classified

CWIX network. Consumer is a FA GeoMetOc participant
who is providing a web application, such as a gazetteer
site. The consumer wishes to publish this web application
in the provider's portal. Provider provides "Named User
Access" to selected nations/users for adding content to
the portal.
GeoMetOc - Portal - register service via The objective of this testcase is to ensure that the
web page consumer is able to register and publish a service on the
GeoMetOc portal.
CWIX network.
Consumer is a FA GeoMetOc participant who is providing
services. The consumer wishes to publish one of these
services in the provider's portal. Provider provides
"Named User Access" to selected nations/users for
adding content to the portal.
Consumer fills in a web page provided by the provider

containing the following information:
* URL to service
* Name of service
* Description of service
GeoMetOc - Portal - Search The objective of this testcase is to ensure that the
provider is able to provide and the consumer is able to
use a GeoMetOc portal in a meaningful way.

CWIX network.
The portal shall at least provide all information and
functionality in English. The Portal will provide
"anonomous" acess to all nations/users for "read only"
access.
This portal contains:

* Information about how to use the portal including
search tools (a user guide)
* A list of available approved services and:
** relevant metadata for the services
** functionality to preview a service
** functionality to copy URL to service
** functionality to retrieve GetCapability response for
each service
* A set of search tools for finding GeoMetOc information
of interest (e.g. search for keywords; browse through
records/services)
* A news feed that advertises news regarding GeoMetOc
information.
* A list of web applications available for the consumers:
At least the following shall be available:
** Gazetteers (search for a place)
** Tactical Descission Aid (TDA) suite.
* Contact details for forecaster who can provide Met RFI
incl. TDA briefings
New template from CAN

GeoMetOc - GGDM Symbology The Objective of this test case is to evaluate the 50k
symbology developed for Ground- Warfighter Geospatial
Data Model vector datasets.
The provider will symbolize a GGDM Dataset derived

from MGCP and or OSM with a custom built tool that
automatically symbolizes a GGDM dataset to a 50k
specification.
The provider will then publish the data as a WMS service.
The consumer will discover the URL of the service via the
GeoMetOc Portal and connect to the service.
The consumer will view the data at the 25k to 100k range
in their client and provide feedback related to the
symbology.
Keywords
*GeoMetOc
*GeoMetoc Portal
*Service
*Geodata
*GeoMetOc
*publish
*Geodata
*GeoMetoc Portal
*Service
*URL
*Service
*wms
*wmts
*Geodata
*search
*wfs
*wps
*wcs
*GeoMetoc Portal
*GeoMETOC
*GeoMetOc
*GeoMetoc Portal
*WMS
*GGDM
*Symbology
*50k
Steps
Step 1:Consumer signs in on the GeoMetOc portal.

Step 2:Consumer fills in a web page provided by the provider containing the following information:
* URL to web application
* Name of web application
* Description of web application
and adds the web application to the portal.
Step 1:Consumer signs in on the GeoMetOc portal

Step 2:Consumer fills in a web page provided by the provider containing the following information:
* URL to service
* Name of service
* Description of service
and adds the service to the portal.
Step 1:The consumer connects to the GeoMETOC portal as single access point to the information
through a web browser
Step 1:Consumer signs in on the GeoMetOc portal and locates the URL for the service by searching for
the test case number
Step 2:Consumer loads service into their client and displays the data at the 20k-100k scale range.
Validation Criteria Information Standards
Products
SUCCESS:
* The user is able to register on the portal *Geospatial Data
* The registered web application has to be visible in the GeoMetOc portal
* URL, name and description shall be displayed and searchable
* Consumers can search for the registered application.
LIMITED SUCCESS:
* the web application can be registered in the GeoMetOc portal but is either
not fully searchable or not displayed with URL, name and description.
* the web application cannot be registered in the GeoMetOc portal
* the web application is not searchable
SUCCESS:
* The user is able to register on the portal *Geospatial Data
* The service has to be visible in the GeoMetOc portal
* URL, name and description shall be displayed and is searchable.
* Consumers can search for the registered service
LIMITED SUCCESS:
* the service can be registered in the GeoMetOc portal but either not fully
searchable or not displayed with URL, name and description.
* the service cannot be registered in the GeoMetOc portal
* the service is not searchable
SUCCESS:
The consumer is able to verify that the portal meets the following criteria: *Geospatial Data
* Information and functionality is available in English
* Information on how to use the portal (user guide) is easily found and
understandable
* the list of services can be found and used easily, amongst others:
* metadata can be displayed
* services can be previewed
* URL to services can be copied
* GetCapability response for services can be retrieved
* the search tools can be found and used easily
* the GeoMETOC news feed is readable
LIMITED SUCCESS:
* usability of the portal is limited by poor user guide and/or not intuitive
functionality
* minor technical issues occurs, that can be handled by re-configuration on
consumer side
* minor security issues occur, that can be handled by re-configuration on
provider or consumer side, or within the network
* usability of the portal is limited by technical issues that can´t be handled by
reasonable re-configuration on provider or consumer side
* security issues occur, that can´t be handled by re-configuration on provider or
consumer side
SUCCESS: GGDM
* the service is displayed at the 20k to 100k scale range by the client *Geospatial Data OGC
* the symbology at the prescribed zoom levels is useable and acceptable to the
consumer
LIMITED SUCCESS:
* the symbology at the prescribed zoom levels has diminished useability and is
not ideal for the consumer
* the service cannot be displayed by the consumer
FAILURE:
* the symbology is unnaceptable and unuseable to the consumer
Protocols Services Comments Providers
*HTTP *Geospatial Services

CAN-DLCSPM/MCE@CWIX 2018
*HTTP *WMS
Please provide fe
Consumers
Technical Testcases Templates
Number Title
CSW Templates
GeoMetOc - CSW Harvesting
GeoMetOc - CSW NGMP -

Portal Search
GeoMetOc - CSW - ISO
Consumer Search
GeoMetOc - CSW NGMP -

Consumer Search
GeoMetOc - Implementation
Specific CSW & ArcMap Plugin
GeoMetOc - CSW - CITE

TeamEngine
WCS Templates
GeoMetOc - WCS 2.0 DGIWG
Geo Profile
GeoMetOc - WCS basic
GeoMetOc - WCS advanced
WFS Templates
GeoMetOc - WFST MIP Update
incl. lock
GeoMetOc - DGIWG WFS
Feature Version

Response Paging
GeoMetOc - DGIWG WFS SOAP
GeoMetOc - WFS MIP
GeometOc - CITE Testcases WFS

DGIWG
WMS Templates
GeoMetOc - DGIWG WMS
raster & vector data
GeoMetOc - WMS - B71GGDM

Symbology
GeoMetOc - WMS Update
sequence
Metadata Elements
GeoMetOc - WMS with

dynamic data
GeoMetOc - WMS cascading-
advanced
GeoMetOc - WMS printing
GeoMetOc - WMS transparent

background - CIMIC
GeoMetOc - WMS Output
formats
GeoMetOc - WMS access using

PKI

SOAP
GeoMetOc - WMS cascading-
simple
GeoMetOc - TDA with WMS
GeometOc - CITE Testcases

WMS DGIWG
WMTS Templates
GeoMetOc - WMTS basic
GeoMetOc - WMTS advanced
REST Templates
GeoMetOc - REST MapService
GeoMetOc - REST
FeatureService
GeoMetOc - REST Geo-
Processing Service - "Drive
Times"

Processing Service - Routing

Processing Service - Range
Rings
GeoMetOc - REST Tiled
MapService
REST tiles export from Tiled

Map Service
REST MapService with Time -

MetOc Services
REST ImageService with Time -
MetOc Service
REST Image Service using raster

function templates
REST Geocoding
OGC Context Templates

GeometOc - OGC Web Map
Context (WMC) Basic
GeoMetOc - OGC Web Service

(OWS) Context
GeoMetOc - OGC Web Map
Context (WMC) Advanced
AML
GeoMetOc - AML STANAG 7170
& AGeoP-19 Review
GeoMetOc - STANAG 7071 -
AML Vector - S57

AML Gridded - GRIB

AML Gridded - NetCDF
Other Templates
GeoMetOc - TDA with
application
GeoMetOc - W3DS
consumption
GeoMetOc - DGIF GML flat

consumption
GeoMetOc - CSV
GeoMetOc - WPS-Route
forecast data
GeoMetOc - KML with TIME
GeoMetOc - MetCM
Objectives
The objective of this testcase is to ensure that one CSW can be harvested in
another CSW.
Provider publishes a catalogue service in accordance with CSW that exposes

geospatial services and data downloads
Consumer harvests the CSW service and displays the geospatial services within
their own catalog service.
In the consumer's catalogue service the following fields must be searchable: Title,
Abstract, Keywords, Point of Contact, Latest Revision Date, Geographical Extent,
Language
Consumer is able to retrieve a list of services matching their search criteria

aggregated from both the consumers existing data as well as the newly harvested
data. The results of a successful implementation must include correct URLs to the
services and the consumer must be able to ingest the providers response.
The objective of this testcase is to publish and search a CSW according to the
NGMP Profile via a Portal.

geospatial services and data downloads.
Consumer searches the catalogue for specific information. The following fields
must be searchable:
* Title
* Abstract,
* Keywords,
* Point of Contact,
* Latest Revision Date,
* Geographical Extent,
* Language
The objective of this testcase is to ensure that the provider is able to publish a
CSW using the ISO profile, and the consumer is able to search the catalogue via
the CSW protocol.

must be searchable:
* Title
* Abstract,
* Keywords,
* Point of Contact,
* Language
This test requires the consumer to search via CSW. Example consumer clients may
be:
* a third party application which can interact using CSW e.g. GIS with a CSW plugin
such as QGIS
* a browser operated by an engineer providing direct CSW calls over http
The objective of this testcase is to publish and search a CSW according to the
NGMP Profile.
Provider publishes a catalogue service in accordance with CSW according to the

NGMP Profile that exposes geospatial services and data downloads
must be searchable:
* Title
* Abstract,
* Keywords,
* Point of Contact,
* Language
The objective of this testcase is to ensure that the provider is able to publish an
ESRi ArcMap CSW Client Plugin designed to work with the provider's
implementation/profile of CSW (e.g. Eb-RIM), and that the consumer is able to
search the catalogue by using the plug-in.
Provider publishes a catalogue service in accordance with their chosen

implementation of CSW that exposes geospatial services and data downloads
Consumer installs and uses the provider's published ArcMap plug-in to search the
catalogue for specific information. The following fields must be searchable:
* Title
* Abstract,
* Keywords,
* Point of Contact,
* Language
The objective of this testcase is to tests the Catalogue Service for Web (CSW)
implementation accordding to the specification.
The consumer publishes a catalogue service in accordance with CSW that exposes
Testcase requires CITE Testdata: Testdata can be found here:
http://cite.opengeospatial.org/teamengine/about/csw/2.0.2/site/
The provider publishes the testcases via the OGC Teamengine.
The consumer uses the Teamengine to test the CSW implementation
The objective of this testcase is to evaluate the new/emerging DGIWG geo profile
for WCS. Providing systems will attempt where possible to configure their WCS
service in accordance with the profile.
Consumer systems retrieves and displays/processes data in a desired format,

resolution and provided projection.
The objective of this testcase is to ensure that the provider is able to provide a
WCS containing coverage data and the consumer is able to consume it.
Consumer retrieves and displays data in a desired formats (other than GRIB and
NetCDF which are tested elsewhere), resolution and provided projection.
WCS containing coverage data and the consumer is able to consume it. More than
one projection is to be supported by the provider.
Consumer retrieves and displays data in a desired format (other than GRIB or
NetCDF), resolution and projection. Required CRSs are: EPSG:4326/CRS84, World
Mercator (EPSG:3395) and UTM zones.
The objective of this testcase is to ensure that the consumer is able to update a
MIP-Feature by using WFS-T
The objective of this testcase is to ensure that the provider is able to provide and
the consumer is able to consume WFS according to the DGIWG profile.
Consume WFS using the Defence Geospatial Information Working Group (DGIWG)
profile to receive vector data of roads, vegetation, settlements or similar
information for further analysis. Information could be also aeornautical obstacles
or naviagtion landmarks.
The WFS provides a map using the GetFeature operation in the following formats:
* GML 3.2
* JSON
* GML 2
Provider provides a WFS supporting at least these coordinate reference systems:

EPSG:4326 (geographic projection in WGS84)
EPSG:32627(UTM zone 27N) EPSG:32628 (UTM zone 28N) EPSG:32629 (UTM zone
29N) EPSG:32630 (UTM zone 30N) EPSG:32631 (UTM zone 31N) EPSG:32632
(UTM zone 32N) EPSG:32633 (UTM zone 33N) EPSG:32634 (UTM zone 34N)
EPSG:32635 (UTM zone 35N) EPSG:32636 (UTM zone 36N) EPSG:32637 (UTM
zone 37N)
The objective of this testcase is to ensure that the WFS supports Feature Version
for defined Features.
Provider provides a WFS that allows

Feature VersionThe consumer finds the relevant WFS service to use in this test by
needed to make sure the end users Can identify the correct WFS.
The objective is to ensure that the WFS Features can be selected in chunks and
provide them step by step Provider provides a WFS containing at least 30 Features
in a Layer.
The WFS shall support the Response Paging Conformance Class.

The consumer finds the relevant WFS service to use in this test by using the
GeoMetOc portal. The GeoMetOc portal shall provide all information needed to
make sure the end users can identify the correct WFS service.
WFS implementing the SOAP conformance class
Provider provides a WFS with SOAP conformace Class containing environmental

information to be used in this test.
The WFS service shall support a map projection according to the BBox of the data:
The WFS service shall support GetFeatureInfo requests to specific layers within the
service.
The WFS Service shall be organised so that the service content is in a structure
suitable for the end users.
The consumer finds the relevant WFS to use in this test by using the GeoMetOc
portal. The GeoMetOc portal shall provide all information needed to make sure
the end users can identify the correct WFS.
The objective of this testcase is to ensure that the provider is able to provide
geodata for the use with MIP-4 using WFS and the consumer is able to consume it.
The objective of this testcase is to conduct a basic conformance test.
The provider provides the OGC TeamEngine which incorporated different

testsuites for different profiles:
* OGC-WFS
* DGIWG-WFS
WMS based on the Defence Geospatial Information Working Group (DGIWG)
profile and the consumer is able to consume it. The test focuses on a number of
key DGIWG requirements specified in the profile (V2.1.0).
The service shall serve contain raster data.
REQUIREMENT #3
The WMS shall support GetFeatureInfo requests to specific layers within the
service. The SHALL support both text/xml AND text/html.
REQUIREMENT #5
The WMS provides a map using the GetMap operation in the following formats:
* image/png (Portable Network Graphics)
* image/gif (Graphics Interchange Format)
* image/jpeg (Joint Photographics Expert Group)
The output formats shall be listed in the GetCapabilities response
REQUIREMENT #6
The WMS shall support map projection according to the following EPSG codes:,
EPSG:4326 (geographic projection in WGS84)
EPSG:32627(UTM zone 27N) EPSG:32628 (UTM zone 28N) EPSG:32629 (UTM zone
29N) EPSG:32630 (UTM zone 30N) EPSG:32631 (UTM zone 31N) EPSG:32632
(UTM zone 32N) EPSG:32633 (UTM zone 33N) EPSG:32634 (UTM zone 34N)
EPSG:32635 (UTM zone 35N) EPSG:32636 (UTM zone 36N) EPSG:32637 (UTM
zone 37N)
REQUIREMENT #14
A DGIWG WMS server shall always provide at least one style element and that
style shall be advertised even if it's only the default style.
REQUIREMENT #25
The Objective of this test case is to evaluate the 50k symbology developed for
Ground- Warfighter Geospatial Data Model vector datasets.
The provider will symbolize a GGDM Dataset derived from MGCP and or OSM with
a custom built tool that automatically symbolizes a GGDM dataset to a 50k
specification.
The provider will then publish the data as a WMS service.
The consumer will discover the URL of the service via the GeoMetOc Portal and
connect to the service.
The consumer will view the data at the 25k to 100k range in their client and
provide feedback related to the symbology.
WMS exposing the update sequence parameter and the consumer is able to
consume it.
The EPSG codes shall be listed in the GetCapabilities response.
service.
The WMS shall be organised so that the service content is in a structure suitable
for the end users.
WMS exposing mandatory Capabilities to the consumer and the consumer shall
be aware to use them.
Provider provides a WMS, containing information for

* DataUrl
* MetadataURL
* FeatureListURL
The WMS service shall support a map projection according to the BBox of the
data:,
The WMS service shall support GetFeatureInfo requests to specific layers within
the service.
The consumer finds the relevant WMS service to use in this test by using the
GeoMetOc portal. The GeoMetOc portal shall provide all information needed to
make sure the end users can identify the correct WMS service.
the consumer is able to consume a WMS with dynamic data such as weather
variance.
The objective of this testcase is to ensure that the provider is able to cascade a
WMS from a third party, add additional layers and the consumer is able to
consume it. This may facilitate a REP for a specific kind of mission. e.g.
amphibious, humanitarian assistance, combat search and rescue (CSAR) etc.
The provider republishes (""cascades"") a service supporting GetFeatureInfo

requests, Legends, MetadataURLs and named styles provided by a third party (for
example NATO Core GIS) and adds additional layers to the republished service.
The objective of this testcase is to ensure that the provider's and the consumer's
systems allow to create prints (pdf or hardcopy) with WMS as a data source.
Provider provides a WMS. Consumer attempts to use the service as a data source
when printing map, either to a physical printer or to a PDF printer.
The printed map should have a realistic size and resolution (A3 format at 300 DPI).
The test exercises both the providers ability to serve quality image suitable for
printing (e.g. symbology), as well as the clients ability to request sufficient pixels
and then print.
spatial data for CIMIC and the consumer is able to consume it.
Provider provides a WMS basic profile containing environmental information to be

used in this test.
service.
for the end users.
WMS supporting multiple output formats (PNG8, PNG24, JPG, GIF, SVG) in order
to influence the file size of the exchanged tiles.
The objective of this testcase is to ensure that it is possible to secure the WMS
request by using SSL mechanism.
Consumer provides a OGC WMS. The WMS shall support a map projection
according to the BBox of the data.
service.
for the end users.
The objective is to ensure that a WMS implements the SOAP conformance class.
Provider provides a WMS with SOAP conformace Class containing environmental

information to be used in this test.
The WMS shall support a map projection according to the BBox of the data:,
service.
for the end users.
The objective of this testcase is to ensure that the provider is able to cascade a
WMS from a third party and the consumer is able to consume it. This may
facilitate a REP for a specific kind of mission. e.g. amphibious, humanitarian
assistance, combat search and rescue (CSAR) etc.
Provider republishes ("cascades") a service provided by a third party (for example

NATO Core GIS).
Decision Aid services as WMS and the consumer is able to consume it.
C2 systems access WMS TDA and evaluate the content as far as display quality,
metadata availability, thresholds display.
The objective of this testcase is to conduct a basic conformance test.
The provider provides the OGC TeamEngine which incorporated different

testsuites for different profiles:
* OGC-WMS
* DGIWG-WMS
WMTS and the consumer is able to consume it.
Provider provides a WMTS containing GeoMetOc information.
The WMTS shall support a map projection according to the BBox of the data.
WMTS and the consumer is able to consume it.
Provider provides a WMTS containing GeoMetOc information.
The WMTS shall support a map projection according to the BBox of the data.
The WMTS shall support GetFeatureInfo requests to specific layers within the
service.
maps to a client as a GeoService for MapService via the REST API and the
consumer is able to consume them.
The client issues requests to resources on the server identified by the URL of the
GeoService. The client is able to interact with the map to create e.g. the Common
Operational Picture or Recognized Enironmental Picture as an image.
The objective of this testcase is to ensure that the provider is able to make
geospatial features accessible to a client as a GeoService for Feature Service via
the REST API and the consumer is able to consume them.
GeoService. The client is able to retrieve feature data and use it locally. The client
may also create additional features of the provided featureTypes and transfer
them to the server.
The objective of this test case is to ensure that the provider is able to provide geo-
analytical capabilities and the consumer is able to use them.
In this particular case “Drive Time Analysis” as a GeoService for Geoprocessing via
the REST API. Instead of accessing all the geodata required for a particular geo-
analytical task and then do the analysis locally which also requires to have the
functionality locally, the client can access a service, identifies the geo-analytical
task offered by the service, and initiates the calculation on the server by
transferring all the required parameters. The results are returned directly to the
client or via a Map Service to render the results to be overlayed to other maps. In
this case the output are areas that can be reached within a given drive time or
drive distance areas covered
In this particular case “Routing Service for Logistics including vehicle height,
weight and road restrictions” as a GeoService for Geoprocessing via the REST API.
Instead of accessing all the geodata required for a particular geo-analytical task
and then do the analysis locally which also requires to have the functionality
locally, the client can access a service, identifies the geo-analytical task offered by
the service, and initiates the calculation on the server by transferring all the
required parameters. The results are returned directly to the client or via a Map
Service to render the results to be overlayed to other maps. In this case the
output is the fastest route between at least two points and a drive turns auxiliary
document.
In this particular case “Range Rings” as a GeoService for Geoprocessing via the
REST API. Instead of accessing all the geodata required for a particular geo-
analytical task and then do the analysis locally which also requires to have the
functionality locally, the client can access a service, identifies the geo-analytical
task offered by the service, and initiates the calculation on the server by
transferring all the required parameters. The results are returned directly to the
client or via a Map Service to render the results to be overlayed to other maps. In
this case the output are range rings with radials around points at specified
intervals and distances.
maps to a client as a GeoService for Tiled MapService via the REST API and the
consumer is able to consume them.
GeoService. The client is able to interact with the map to create e.g. the Common
Operational Picture or Recognized Enironmental Picture as an image.
maps to a client as a GeoService for Tiled MapService via the REST API and the
consumer is able to download them to a TPK.
GeoService. The client is able to download the tiles creating a TPK and consume
them on the client side to create e.g. the Common Operational Picture or
Recognized Enironmental Picture as an image.
maps to a client as a GeoService for MapService with Time dimention enabled via
the REST API and the consumer is able to consume them taking advantage of the
Time capability.
GeoService. The client is able to interact with the map filtering the layers by Time
to create e.g. the Common Operational Picture or Recognized Enironmental
Picture as an image.
maps to a client as a GeoService for ImageService with Time dimension enabled
via the REST API and the consumer is able to consume them taking advantage of
the Time capability.
GeoService. The client is able to interact with the map filtering the layers by Time
to create e.g. the Common Operational Picture or Recognized Environmental
Picture as an image.
maps to a client as a GeoService for ImageService using raster functions via the
REST API and the consumer is able to consume them taking advantage of the
functions.
GeoService. The client is able to request the raster functions available the service
and display correctly.
The objective of this test case is to ensure that the provider is able to provide
geocoding capabilities and the consumer is able to use them.
In this particular case “a Skolkan Gazetteer” as a Geocode Service via the REST API.
The client access the service and should be able to find any Skolkan place by
typing the name of the place. The results are a location of the requested place.
The objective of this testcase is for the provider to provide and consumer to
consume a Web Map Context (WMC) file. This may be used to support the
distribution of a REP view within a COP.
The provider will create a WMC file referencing one or more WMS map layers,
according to the OGC specification. The consumer will load/ingest the file and be
able to select and view the referenced layers without additional configuration.
consume an OWS Context file containing a set of pre-configured services (e.g.
WMS layers, WFS features) and/or in-line content. This may be used to support
the distribution of a REP view for a COP.
The provider will create a OWS Context file referencing one or more services
according to the OGC specification. The consumer will load/ingest the file and be
able to select the referenced services and inline content without additional
configuration. The legend associated with any specified map layer style should be
displayable within the client.
consume a Web Map Context (WMC) file containing layers with one or more
styles. This may be used to support the distribution of a REP view for a COP.
The provider will create a WMC file referencing one or more WMS map layers,
each with one or styles, according to the OGC specification. The consumer will
load/ingest the file and be able to select the referenced layers and associated
styles without additional configuration. The legend associated with each style
should be displayable within the client.
The objective of this test is to ensure that the consumer is able to understand the
concepts, terminology and descriptions contained with the documents to enable
them to create and/or develop a product as defined in said document/s.
Provider provides STANAG 7170 and AGeoP-19 documents for downlo+C23ad
Consumer downloads documents, performs review and annotates review

template for collation against testcase outcome.
Vector AML in S-57 (i.e. LBO, SBO, CLB, ESB, MFF, RAL), and the consumer is able
to consume it.
The objective of this test is to ensure that the products created and published in
accordance with the referenced specification are capable of meeting said
specification/s criteria for success
Provider provides a vector AML encoded according to STANAG 7071 and AGeoP-
19, and corresponding Product Specifiction, via HTTP download.
gridded AML in GRIB (i.e. AMC, GS-ESB), and the consumer is able to consume it.
Provider provides a gridded AML encoded according to STANAG 7071 and AGeoP-
gridded AML in NetCDF (i.e. IWC), and the consumer is able to consume it.
Provider provides a gridded AML encoded according to STANAG 7071 and AGeoP-
Tactical Decision Aid via an application and the consumer is able to consume it.
Provider is able to provide Decision Aid services on an application and the

consumer is able to use it.
C2 systems access TDAs via the provider's portal and evaluate the content as far as
display quality, metadata availability, thresholds display.
the consumer is able to consume a W3DS diplaying 3D-Vector graphics from
CityGML using VRML or similiar.
The Client Application consumes information about a W3DS using the

GetCapabilities Operation.
The Client Application consumes a 3D graphic using the GetScene operation in the
following formats:
* VRML model/x3d+vrml
* XML model/x3d or model/x3d+xml
* Binary model/x3d+binary
The objective of this testcase is ensure that the provider is able to provide and the
consumer is able to consume a GML 3.2.1 file (flat style) compliant to the Defence
Geospatial Information Framework (DGIF 2016-2) specification.
the consumer is able to consume a CSV service.
Provider provides a CSV service. The CSV service contains vector data, including
hyperlinks to other provider services.
the consumer is able to consume a WPS.
Provider provides a WPS processing data output for a route.
KML service and the consumer is able to consume it.
The KML service contains vector data including hyperlinks to other provider
services. The vector data will be temporal in nature.
MetCM, and the consumer is able to consume it.
Provider provides a MetCM (artillery message) according to STANAG 4082 via

HTTP download.
Keywords Steps
Step 1:Consumer connects to the the providers

*GeoMetoc Portal CSW
*Havesting Result 1:see Validation Criteria
*CSW
*Harvest Step 2:Consumer harvests the providers
*GeoMetOc Result 2:see Validation Criteria
*Service
*Search
*Geodata
Step 1:The consumer finds either the CSW

*Service endpoint or directly the CSW GetCapabilities URL
*Geodata by using the GeoMetOc portal.
*Search Result 1:see Validation Criteria
*CSW
*NGMP Step 2:The consumer uses the providers portal to
*GeoMetoc Portal search metadata
*OGC endpoint or directly the CSW GetCapabilities URL
*CSW Result 1:see Validation Criteria
*GeoMetoc Portal
*GeoMetOc Step 2:Consumer searches the catalogue via CSW
*Search for specific information.
*ISO Result 2:see Validation Criteria
*Service

*NGMP endpoint or directly the CSW GetCapabilities URL
*Search by using the GeoMetOc portal.
*Geodata Result 1:see Validation Criteria
*CSW
*GeoMetoc Portal Step 2:The consumer uses its Client to send a
*Service search request
Step 1:The consumer finds the plugin from the
*ArcMap Geometoc portal and configures their system to
*Geodata use it.
*Search Result 1:see Validation Criteria
*GeoMetOc
*Service Step 2:The consumer uses the plugin to search the
*CSW providers portal .
*OGC Result 2:see Validation Criteria
*GeoMetoc Portal
Step 1:Provider finds the CITE tool from the

*GeoMetoc Portal GeoMetOc portal and logs into CITE Teamengine
*TeamEngine Result 1:see Validation Criteria
*GeoMetOc
*CITE Step 2:Provider tests the consumer CSW with the
*Search configured testdata
*Service Result 2:see Validation Criteria
*CSW
*Geodata
Step 1:The consumer connects to the WCS through

*DGIWG the web portal by copying either the URL endpoint
*GeoMetOc or the GetCapabilities response.
*format Result 1:see Validation Criteria
*GeoMetoc Portal
*coverage
*resolution
*WCS Access
*projection
*Geodata
*Geo Profile
*WCS
*Service
*coverage the web portal by copying either the URL endpoint
*WCS or the GetCapabilities response.
*WCS Access
*format
*Geodata
*GeoMetOc
*projection
*resolution
*GeoMetoc Portal

*EPSG:4326/CRS84 the web portal by copying either the URL endpoint
*Service or the GetCapabilities response.
*World Mercator Result 1:see Validation Criteria
*UTM zones
*GeoMetoc Portal
*Geodata
*bounding box
*GeoMetOc
*coverage
*projection
*EPSG:3395
*WCS
*WCS Access
Step 1:The consumer finds the relevant WFS to use

*update in this test by using the GeoMetOc portal. The
*GeoMetoc Portal GeoMetOc portal shall provide all information
*Geodata needed to make sure the end users can identify the
*WFS-T correct WFS
*editing Result 1:see Validation Criteria
*GeoMetOc
*transactional Step 2:Consumers edits a MIP-Feature of the WFS
*Service and updates it via WFS-T
*feature Result 2:see Validation Criteria
*MIP
*publish Step 3:Consumers checks if the server locks the
*vector data Feature
*EPSG:32635 (UTM zone 35N) in this test by using the GeoMetOc portal. The
*feature GeoMetOc portal shall provide all information
*EPSG:32634 (UTM zone 34N) needed to make sure the end users can identify the
*EPSG:32628 (UTM zone 28N) correct WFS.
*Defence Geospatial Information Working Result 1:see Validation Criteria
Group
*GeoMetOc Step 2:Consumer attempts to display the output of
*GeoMetoc Portal the WFS
*WFS Result 2:see Validation Criteria
*EPSG:4326 (geographic projection in
WGS84)
*Service
*EPSG:32661 (WGS 84 / UPS North)
*DGIWG
*Geodata
Step 1:The consumer finds either the WFS
*Geodata endpoint or directly the WMS GetCapabilities URL
*Service by using the GeoMetOc portal.
*Feature Version
*GeoMetoc Portal Step 2:The consumer connects to the WFS copying
*GeoMetOc either the URL endpoint or the GetCapabilities URL.
Step 3:The consumer uses its client to send a

GetFeature Insert Request to the providers WFS.

GetFeature Request to the provider to retrieve the
inserted feature in the step above.

GetFeature Update Request to the providers WFS.

GetFeature Request to the provider to retrieve the
updated feature in the step above.

*GeoMetOc endpoint or directly the WFS GetCapabilities URL
*GeoMetoc Portal
*Response Paging Step 2:The consumer connects to the WFS copying
*Service either the URL endpoint or the GetCapabilities URL

GetFeature Request with response paging
parameters to the server and finds all relevant
information in the response document
Step 4:The consumer uses the provided "NextURL"

in the client to retrieve the next Features
*Service endpoint or directly the WFS GetCapabilities URL
*WFS by using the GeoMetOc portal.
*SOAP
*GeoMetoc Portal Step 2:The consumer connects to the WFS copying
*Geodata either the URL endpoint or the GetCapabilities URL
Step 3:The consumer uses its SOAP Client to send a

- WFS GetCapabilities
- WFS GetFeature
- WFS DescribeFeatureType
- WFS GetFeatureWithLock
- WFS DescribeStoredQueries
- WFS ListStoredQueries
- WFS LockFeature
- WFS GetPropertyValue
request with SOAP Envelope to the WFS Service

*Geodata in this test by using the GeoMetOc portal. The
*feature GeoMetOc portal shall provide all information
*WFS Access needed to make sure the end users can identify the
*GeoMetoc Portal correct WFS
*Service
*MIP Step 2:Consumers attempt to display the output of
*WFS the WFS
Step 1:The consumer finds all relevant information

*Conformance for the access of the CITE TeamEngine by using the
*DGIWG GeoMetOc portal.
*Test
*GeoMetOc Step 2:The consumer configures the testrun within
*TeamEngine the CITE TeamEngine.
*CITE Result 2:see Validation Criteria
Step 1:The consumer finds the relevant WMS to
*EPSG:32636 (UTM zone 36N) use in this test by using the GeoMetOc portal. The
*DGIWG GeoMetOc portal shall provide all information
*map needed to make sure the end users can identify the
*EPSG:32630 (UTM zone 30N) correct WMS.
*GeoMetoc Portal Result 1:see Validation Criteria
*raster data Step 2:The consumer connects to the WMS by
*EPSG:32635 (UTM zone 35N) copying either the URL endpoint or the
*gif GetCapabilities URL response and displays the
*png information.
*Defence Geospatial Information Working Result 2:see Validation Criteria
Group
*EPSG:32661 (WGS 84 / UPS North)
*jpeg
*EPSG:4326 (geographic projection in
WGS84)
*getcapability
*Service
*WMS
*Geodata
*GeoMetOc
Step 1:Consumer signs in on the GeoMetOc portal

*GeoMetOc and locates the URL for the service by searching for
*GeoMetoc Portal the test case number
*WMS Result 1:see Validation Criteria
*GGDM
*Symbology Step 2:Consumer loads service into their client and
*50k displays the data at the 25k-100k scale range.
*Service use in this test by using the GeoMetOc portal. The
*Geodata GeoMetOc portal shall provide all information
*single access point needed to make sure the end users can identify the
*GeoMetOc correct WMS.
*GeoMetoc Portal
*Update Step 2:The provider changes relevant information
of the WMS and increases automatically or
manually the update sequence.
Step 3:The consumer client automatically updates

the WMS content.
*wms use in this test by using the GeoMetOc portal. The
*Service GeoMetOc portal shall provide all information
*GeoMetoc Portal needed to make sure the end users can identify the
Step 2:The consumer connects to the WMS copying
either the URL endpoint or the GetCapabilities URL

GetCapabilities Request to the server and finds all
relevant information in the response document
Step 4:The consumer uses the provided DataURL to

download the data provided by the WMS
Step 5:The consumer uses the provided

FeatureListURL to download the List of Features
provided by the WMS
Step 6:The consumer uses the provided

MetadataURL to find Metadata of the provided
WMS.

*weather variance use in this test by using the GeoMetOc portal. The
*weather forecast GeoMetOc portal shall provide all information
*map Result 1:see Validation Criteria
*WMS
*GeoMetoc Portal Step 2:The consumer connects to the WMS by
*Service copying either the URL endpoint or the
*weather warning GetCapabilities URL response and displays the
*dynamic data information.
Step 1:The consumer finds both relevant WMS
*GeoMetoc Portal (original and the cascaded) to use in this test by
*GeoMetOc using the GeoMetOc portal. The GeoMetOc portal
*named styles shall provide all information needed to make sure
*NATO Core GIS the end users can identify the correct WMS.
*map Expected result:
*Service
*Metadata Step 2:The consumer compares both services
*GetFeatureInfo
*cascading
*Legends

*GeoMetOc use in this test by using the GeoMetOc portal. The
*printing needed to make sure the end users can identify the
*map correct WMS.
*GeoMetoc Portal
*Geodata Step 2:Print the map

*Geodata use in this test by using the GeoMetOc portal. The
*GeoMetoc Portal GeoMetOc portal shall provide all information
*wms needed to make sure the end users can identify the
*CIMIC Result 1:see Validation Criteria
*Service
*single access point Step 2:The consumer sets the transparancy
parameter for the WMS
*PNG8 use in this test by using the GeoMetOc portal. The
*GIF GeoMetOc portal shall provide all information
*output format correct WMS.
*map
*PNG24 Step 2:Compare File Size
*file size Result 2:see Validation Criteria
*WMS
*GeoMetOc
*GeoMetoc Portal
*JPG
Step 1:The consumer requests a PKI by the PKI

*WMS provider
*PKI
*WMS Access Step 2:The consumer configures the WMS to use
*Geodata the PKI
*Service
Step 3:Another conumser uses the secured WMS

*SOAP use in this test by using the GeoMetOc portal. The
*WMS needed to make sure the end users can identify the
*GeoMetoc Portal
Step 2:The consumer connects to the WMS copying
either the URL endpoint or the GetCapabilities URL
Step 3:The consumer uses its SOAP Client to send a

- WMS GetCapabilities
- WMS GetMap
- WMS GetFeatureInfo
request with SOAP Envelope to the WMS Service
Step 1:The consumer finds both relevant WMS
*cascading (original and the cascaded) to use in this test by
*map using the GeoMetOc portal. The GeoMetOc portal
*NATO Core GIS shall provide all information needed to make sure
*GeoMetoc Portal the end users can identify the correct WMS.
*Geodata
*Service Step 2:The consumer compares both Services
Step 1:The consumer finds the WMS by using the

*display quality GeoMetOc portal.
*wms Result 1:see Validation Criteria
*Geodata
*TDA Step 2:The consumer connects to the WMS by
*application copying either the URL endpoint or the
*c2 systems GetCapabilities URL response and displays the
*Service information.
*GeoMetoc Portal
*metadata
Step 1:The consumer finds all relevant information

*GeoMetOc for the access of the CITE TeamEngine by using the
*CITE GeoMetOc portal.
*Conformance Result 1:see Validation Criteria
*Test
*TeamEngine Step 2:The consumer configures the testrun within
the CITE TeamEngine.
Step 1:The consumer connects to the WMTS

*WMTS through the web portal by copying either the URL
*GeoMetOc endpoint or the GetCapabilities URL response and
*Geodata displays the information.
*Service
Step 2:Consumers attempt to consume and display
the WMTS. Clients are able to send GetFeatureInfo
requests and get a response for any object.
Step 1:The consumer connects to the WMTS
*getfeatureinfo through the web portal by copying either the URL
*tile endpoint or the GetCapabilities URL response and
*WMTS displays the information URL.
*GeoMetOc
*Service Step 2:Consumers attempt to consume and display
*Geodata the WMTS. Clients are able to send GetFeatureInfo
requests and get a response for any object.
Step 3:Consumer uses a GetFeatureInfo Request in

its client
Step 1:The consumer connects to the REST API

*rest map service provided by the GeoMetOC Portal and displays the
*rest api information.
*rep Result 1:see Validation Criteria
*GeoMetoc Portal
*Geodata
*Service
*cop
*geoservice
*GeoMetOc

*cop provided by the GeoMetOC Portal and displays the
*feature data Result 1:see Validation Criteria
*Geodata
*rest api Step 2:The client is able to retrieve feature data
*GeoMetOc and use it locally. The client may also create
*feature type additional features of the provided featureTypes
*rest map service and transfer them to the server.
*geoservice
*GeoMetoc Portal
*Geodata provided by the GeoMetOC Portal and displays the
*feature type information.
*Geoprocessing
*rep Step 2:The client can access a service, identifies the
*cop geo-analytical task offered by the service, and
*GeoMetoc Portal initiates the calculation on the server by
*Geo-analytical transferring all the required parameters.
*geoservice
*feature data
*rest api
*rest map service

*feature data provided by the GeoMetOC Portal and displays the
*cop information.
*geoservice
*Geoprocessing Step 2:The client can access a service, identifies the
*Service geo-analytical task offered by the service, and
*rep initiates the calculation on the server by
*rest map service transferring all the required parameters.
*feature type Result 2:see Validation Criteria
*GeoMetoc Portal
*Geo-analytical
*rest api
*Geodata

*geoservice provided by the GeoMetOC Portal and displays the
*GeoMetOc information.
*feature data Result 1:see Validation Criteria
*Geodata
*GeoMetoc Portal Step 2:The client can access a service, identifies the
*rep geo-analytical task offered by the service, and
*rest api initiates the calculation on the server by
*Geo-analytical transferring all the required parameters.
*Geoprocessing Result 2:see Validation Criteria
*feature type
*cop
*rest map service
*Service
*GeoMetOc provided by the GeoMetOC Portal and displays the
*cop Result 1:see Validation Criteria
*GeoMetoc Portal
*rest map service
*Geodata
*rep
*geoservice
*rest api

*geoservice provided by the GeoMetOC Portal and displays the
*GeoMetoc Portal information.
*cop Result 1:see Validation Criteria
*Service
*rep
*rest map service
*GeoMetOc
*rest api
*Geodata
Step 1:Step: The consumer connects to the REST

*GeoMetoc Portal API provided by the GeoMetOC Portal and displays
*Geodata the information.
*rest map service
*rep
*Service
*rest api
*geoservice
*cop
*rest api information.
*Geodata
*geoservice
*Service
*rep
*GeoMetOc
*cop

*cop information.
*rest api
*GeoMetOc
*geoservice
*GeoMetoc Portal
*rep
*Service
Step 1:The consumer connects to the Geocode

*GeoMetOc Service and gets the location of the requested
*Service place on the client side.
*rest map service Result 1:see Validation Criteria
*geoservice
*Geodata
*cop
*rep
*GeoMetoc Portal
*rest api
Step 1:The consumer finds the relevant WMC to
*single access point use in this test by using the GeoMetOc portal. The
*ogc GeoMetOc portal shall provide all information
*Service correct WMC file.
*Geodata
*wms Step 2:The consumer loads/ingests the WMC file
*WMC
Step 3:The consumer is able to select and display
each layer
Step 1:The consumer finds the relevant OWS

*Context Context to use in this test by using the GeoMetOc
*single access point portal. The GeoMetOc portal shall provide all
*Service information needed to make sure the end users can
*wms identify the correct context file.
*ogc
*GeoMetOc Step 2:The consumer loads/ingests the OWS
*OWS Context file
*GeoMetoc Portal
each service

the required style for each WMS layer
Step 5:The consumer is able to display the legend

associated with each WMS style
Step 1:The consumer finds the relevant WMC to
*single access point use in this test by using the GeoMetOc portal. The
*GeoMetOc needed to make sure the end users can identify the
*ogc correct WMC file.
*wms
*rep Step 2:The consumer loads/ingests the WMC file.
*WMC
each layer

the required style for each layer.
Step 5:The consumer is able to display the legend

associated with each style.
*document Step 1: The consumer downloads documents from

*AML the CWIX 2018 Wiki
Result 1: see Validation Criteria
Step 2: The consumer undertakes review

*S-57 Step 1: The provider supplies vector AML S-57
*dataset product for download, along with any associated
*exchange set specifications or linked documents/files
*AML Result 1: see Validation Criteria
Step 2: Consumer loads AML into their system

*GRIB Step 1: The provider supplies AML GRIB product for

*dataset download, along with any associated specifications
*AML or linked documents/files

*NetCDF Step 1: The provider supplies AML NetCDF product

*dataset for download, along with any associated
*exchange set specifications or linked documents/files
*AML Result 1: see Validation Criteria
*IWC
Step 1:Consumer accesses the TDA application via
*GeoMetoc Portal webbrowser and consumes the TDA
*application Result 1:see Validation Criteria
*c2 systems
*display quality
*Service
*TDA
*Geodata
*metadata
*GeoMetOc
Step 1:The consumer finds the W3DS endpoint

*GeoMetoc Portal using the GeoMetOc portal.
*Service
*Geodata Step 2:The consumer consumes a 3D graphic using
the client application.
Step 1:The consumer finds the DGIF GML File using

*DGIF the GeoMetOc portal.
*Defence Geospatial Information Result 1:see Validation Criteria
Framework
*gml Step 2:The consumer consumes the DGIF GML File.
*GeoMetoc Portal
*Geodata
*GeoMetOc
Step 1:The consumer finds the relevant CSV service

*CSV to use in this test by using the GeoMetOc portal.
*Service The GeoMetOc portal shall provide all information
*Geodata correct CSV service
*vector data
*hyperlink Step 2:Consumer correctly displays all data
received and experiences no responsiveness issues.
Step 1:The consumer finds the relevant WPS to use
*GeoMetoc Portal in this test by using the GeoMetOc portal. The
*Route forecast data needed to make sure the end users can identify the
*process correct WPS
*WPS Result 1:see Validation Criteria
*Service
*GeoMetOc Step 2:Consumers attempt to call the service,
providing details of a specific route (e.g. MSR), and
retrieve Met data for the route for use in the
consumer client.
Step 1:The consumer finds the relevant service to

*KML use in this test by using the GeoMetOc portal. The
*GeoMetOc GeoMetOc portal shall provide all information
*Service correct service.
Step 2:Consuming system attempts to consume

and render the KML, use temporal controls and
activate hyperlinks.
*MetCM Step 1:Consumer locates the link to download the

*GeoMetOc file using the GeoMetOc portal.
*Service
*GeoMetoc Portal Step 2:The consumer downloads the file and
consumes it in their system.
Validation Criteria Information Products
SUCCESS:
* Geographical search must be supported. *Geospatial Data
* All listed fields are searchable.
* Functioning service URL’s.
* Consumer successfully ingests the service response.
* Response is within the bounds of the search parameters.
LIMITED SUCCESS:
* Only some of the listed fields are searchable
* Only some of the service URL’s function properly and/or provide a
consumable response.
* Response contains data beyond the scope of the search, but all other
steps have been successful.
* Search is not supported
SUCCESS:
LIMITED SUCCESS:
SUCCESS:
LIMITED SUCCESS:
SUCCESS:
LIMITED SUCCESS:
SUCCESS:
LIMITED SUCCESS:
SUCCESS:
* The CITE Teamengine can be run with the CSW *Geospatial Data
* all tests can be run successful
LIMITED SUCCESS:
* not all tests can be run successful, but the issues can be configured
* None of the tests can be run successful
* it is not clear why tests fail
SUCCESS:
* Provider understands the profile and can configure the service *Geospatial Data
accordingly
* WCS output is correctly displayed in the client layer.
* The bounding box advertized by the GetCapabilities document is
appropriately configured to allow the screen to fit to the actual data
published by the WCS layer.
LIMITED SUCCESS:
* Provider understands the majority of the profile and/or can configure
their services for the majority of the requirements
* WCS output is correctly displayed in the client layer.
* The bounding box advertized by the GetCapabilities document is not
* Provider does not understand the profile and/or is unable to configure
the service to meet the requirements of the profile
* WCS output is not correctly displayed in the client layer.
SUCCESS:
* WCS output is correctly displayed in the client layer *Geospatial Data
* The bounding box advertized by the GetCapabilities document is
LIMITED SUCCESS:
* WCS output is correctly displayed in the client layer
* The bounding box advertized by the GetCapabilities document is not
* WCS output is not correctly displayed in the client layer
SUCCESS:
* All service requests (GetCapabilities, GetCoverage) work as specified *Geospatial Data
* All CRSs are available and display within the client as expected
LIMITED SUCCESS:
* The WCS can be requested but the coverage is not downloadable
* Not all of the request operations work properly
* Not all output formats can be requested
* WCS output is not correctly displayed in the client layer
SUCCESS:
* Consumer succesfully consumes the WFS without any issues, all *Geospatial Data
available geographic data can be used.
* The edited Feature is locked
* The lock is released after the specified time
LIMITED SUCCESS:
* Consumer succesfully consumes the WFS without any issues, all
* The edited Feature is locked
* The lock is not released after the specified time
* During editing the Feature is not locked
SUCCESS:
* All service requests (GetCapabilities, GetFeatureInfo) work as specified *Geospatial Data
* The GetCapabilities response contains the correct EPSG codes and

advertises a correct bounding box.
* The consumer is able to retrieve WFS layers without any errors.

* Filtering works
LIMITED SUCCESS:
* Vectordata can be consumed but not analysed or processed.
* The GetCapabilities response is not entirely conformant but the
consumer is still able to display WFS layers
The consumer is not able to display WFS layers
SUCCESS:
* The consumer can connect to the WFS and is able to insert a Featuses *Geospatial Data
* The consumer retrieves the inserted feature with the version number
* The consumer is able to update the feature
* The version number increases with an update
LIMITED SUCCESS:
* The consumer is able to insert a feature and retrieves a version number
* The version number does not increase
* The consumer is not able to retrieve a version number
SUCCESS:
* The consumer can connect to the WFS and retrieves a first chunk of *Geospatial Data
Features
* The consumer is able to use the ""NextURL"" and retrieves the next
chunk of Features
LIMITED SUCCESS:
* The conumer is not able to use the ""NextURL"
* the consumer is not able to use the respone paging parameters
SUCCESS:
* All WFS operations can be used within the SOAP client *Geospatial Data
LIMITED SUCCESS:
* Usability of the services is limited due to not intuitive or useful enough
functionality
* minor technical issues occur, that can be handled by re-configuration
on consumer side,
* The use of a WSDL is necessary in the client
The WFS doesn't support the SOAP conformance class
SUCCESS:
Consumer successfully consumes the WFS without any issues, all *Geospatial Data
LIMITED SUCCESS:
A minor issue ocurrs, not being able to process all geographic data.
No geographic data can be processed in the consuming system.
SUCCESS:
* The conformance test results are valid. All failures are limited to *Geospatial Data
testdata configurations and not to functional failures.
LIMITED SUCCESS:
* Minor conformance classes fail.
* It is not clear why tests fail.
* The basic conformance classes fail.
SUCCESS:
The consumer has to be able to use the the service without experiencing *Geospatial Data
major difficulties.
The system shall support connecting to several WMS at the same time,
All requirements specified are fulfilled e.g.:

* All service requests (GetCapabilities, GetMap, GetFeatureInfo) work as
specified
* Map is displayed as specified and the different output formats can be
used
* Map can be projected to any of the specified EPSG codes.
* All exceptions types are available
* At least one style per layer is provided
* Text/HTML is supported by GetFeatureInfo
LIMITED SUCCESS:
* The WMS can't be used with all formats
* Get FeatureInfo does not support text/html
* The WMS can't be used with all EPSG codes
* Not all exception types are supported
* Style(s) not provided for each layer
* Not all operationes as specified work properly
on consumer side,
* Added layer on server side does not show up in client after re-
configuration
* GetFeatureInfo does not work correct
* usability of the WMS is limitied by technical issues that can´t be
handled by reasonable re-configuration on provider or consumer side
* security issues occurs, that can't be handled by re-configuration on
SUCCESS:
* the service is displayed at the 25k to 100k scale range by the client *Geospatial Data
* the symbology at the prescribed zoom levels is useable and acceptable
to the consumer
LIMITED SUCCESS:
* the symbology at the prescribed zoom levels has diminished useability
and is not ideal for the consumer
* the service cannot be displayed by the consumer
FAILURE:
* the symbology is unnaceptable and unuseable to the consumer
SUCCESS:
* the consumer connects to the service by copying either the services *Geospatial Data
end point URL or cuting relevant parts out of a copied GetCapabilities
response.
* The update Sequence increases after changing the settings by the
provider
LIMITED SUCCESS:
functionality
on consumer side,
* minor security issues occur, that can be handled by re-configuration on
* Hierarchical layer structures are ""flattened"" in the client
* Added layer on server side does not show up in client after re-
configuration
SUCCESS:
* In the Capabilities the DataURL, FeatureListURL and MetadataURL *Geospatial Data
provide a valid URL
* The consumer is able to use the URL to download the relevant
information
LIMITED SUCCESS:
* In the capabilities document the information is provided
* consumer can't use the provided URL's
* no information in provided in the Capabilities document
SUCCESS:
Consumer is able to consume the service in the consumer system. *Geospatial Data
Updates to the dynamic information in the service (such as new weather
observations, warnings and forecasts) are automatically displayed in the
consumer system.
LIMITED SUCCESS:
Consumer is able to consume the service in the consumer system, but
limited manual steps are required to make updates to the dynamic
information in the service (such as new weather information) visible in
the consumer system.
Consumer cannot consume the service, or there is no easy way to refresh
the dynamic information in the service.
SUCCESS:
The consumer can connect to and consume both services. The services *Geospatial Data
are functionally equivalent from the client's perspective, except for the
added layers in the second service:
* GetFeatureInfo requests return the same results
* The MetadataUrls are preserved in the GetCapabilities result
* Legends from the original service are supported in the cascaded service
* Named styles from the original service are supported in the cascaded
service
* The consumer can consume both services, but they are not functionally
equivalent as described above.
* Original and cascaded service do not fit together (geographical extent,
map content, coordinate system ...)
SUCCESS:
* No error occurs during printing. *Geospatial Data
* The printed map has a resolution appropriate for the printer, the
printed image does not look blurry or pixelated.
* The time it takes from the time the print command is issued until the
printing is completed is acceptable (< 3')
LIMITED SUCCESS:
* only smaller maps (A4) are printed correctly
* The time it takes from the time the print command is issued until the
printing is completed is inacceptable (>3')
* the map is not printed correctly at all
SUCCESS:
* the consumer is able to connect to the service by copying either the *Geospatial Data
services end point URL or cuting relevant parts out of a copied
GetCapabilities response.
* The background of the WMS can be set transparent
* GetFeatureInfo works as expected
* Map can be projected to any of the specified EPSG codes.
* The layer structure is suitable for consumer use
LIMITED SUCCESS:
* The background of the WMS can't be set transparent
SUCCESS:
* Alternative output formats are available and provide means to *Geospatial Data
reduce/increase output size.
LIMITED SUCCESS:
* Alternative output formats are available, but due to poor compression
they do not decrease the size of images
* information about file size is not available.
* No alternative output formats are available
SUCCESS:
* The PKI can be requested sucessfully *Geospatial Data
* The WMS can be secured
* The consumer can connect to the secured WMS
LIMITED SUCCESS:
* The PKI can be requested
* The service can't be configured to use it
* The PKI can't be requested
SUCCESS:
* All WMS operations can be used within the SOAP client. *Geospatial Data
LIMITED SUCCESS:
functionality
on consumer side,
* The use of a WSDL is necessary in the client
The WMS doesn't support the SOAP conformance class.
SUCCESS:
The consumer can connect to and consume both services. The services *Geospatial Data
are functionally equivalent from the client's perspective:
* The layer lists are the same in both services
* The returned map images look the same from both services
LIMITED SUCCESS:
* The consumer can consume both services, but a minor issue (such as a
mismatch in the published layer lists) occurs.
* Original and cascaded service do not fit together (geographical extent,
map content, coordinate system ...)
SUCCESS:
Consumer is able to access the TDA as WMS and the content is *Geospatial Data
satisfactory
LIMITED SUCCESS:
Consumer is able to access the TDA as WMS but is only partially
satisfactory
Consumer is not able to access the TDA as WMS or the content is useless
SUCCESS:
* The conformance test results are valid. All failures are limited to *Geospatial Data
testdata configurations and not to functional failures.
LIMITED SUCCESS:
* Minor conformance classes fail.
* It is not clear why tests fail.
* The basic conformance classes fail.
SUCCESS:
The WMTS is correctly displayed and georeferenced in the client. *Geospatial Data
The WMTS is not correctly displayed and georeferenced in the client.
SUCCESS:
The WMTS is correctly displayed and georeferenced in the client. Client is *Geospatial Data
able to send GetFeatureInfo request and display server response in a
human readable format.
Client is not able to send GetFeatureInfo request and receive a response
from the server.
SUCCESS:
Consumer is able to invoke the service and retrieve the requested maps. *Geospatial Data
The maps are displayed correctly.
Consumer is not able to invoke the service, no correct maps are
displayed
SUCCESS:
Consumer is able to invoke the service and retrieve feature data as *Geospatial Data
requested. The features contain all properties including feature type,
properties and geometry.
LIMITED SUCCESS:
Consumer is able to invoke the service, but system is not responding all
the desired information. Nonetheless, the features are reusable by the
consumer. Systems with limited success shall report the problems they
have with the feature data.
Consumer is not able to get feature data from the service.
SUCCESS:
Consumer is able to invoke the service, gets prompted to provide *Geospatial Data
parameters and to conduct the geo-process based on these parameters.
The analytical results are displayed correctly.
LIMITED SUCCESS:
Consumer is able to access the service, but the parameter exchange
mechanism has limited functionality.
Consumer is not able to get useful information from the service or the
service is responding with incorrect geo-analytical results.
SUCCESS:
LIMITED SUCCESS:
SUCCESS:
LIMITED SUCCESS:
SUCCESS:
*Geospatial Data
Consumer is able to invoke the service and retrieve the requested maps.
The maps are displayed correctly.
LIMITED SUCCESS:
the desired information. Nonetheless, a correct map is displayed.
Consumer is not able to get useful information from the service.
SUCCESS:
*Geospatial Data
Consumer is able to invoke the service and download the requested tiles
(TPK). The TPK is displayed correctly.
LIMITED SUCCESS:
Consumer is able to invoke the service and download the requested tiles
(TPK) but the client is not able to use them correctly.
Consumer is not able to download the TPK and use them on the client
side.
SUCCESS:
*Geospatial Data
The layers of the service are filtered by time/date and the layers of the
maps are displayed correctly.
LIMITED SUCCESS:
SUCCESS:
*Geospatial Data
The layers of the service are filtered by time/date and the layers of the
maps are displayed correctly.
LIMITED SUCCESS:
SUCCESS:
*Geospatial Data
Consumer is able to invoke the service and retrieve the requested maps
and displayed correctly using the raster functions available.
LIMITED SUCCESS:
the desired symbology/values. Nonetheless, a map is displayed.
SUCCESS:
*Geospatial Data
Consumer is able to invoke the Geocode Service and get the location of
the requested place on the client side.
LIMITED SUCCESS:
Consumer is able to invoke the Geocode service, but system is not

responding or not sending the exact location. Nonetheless, a result is
displayed.
Consumer is not able to get useful information from the Geocode
service.
SUCCESS:
* the WMC file can be identified and downloaded from the portal *Geospatial Data
* the file is loaded/ingested into the consumers system and all
referenced layers are visible without any additional configuration
LIMITED SUCCESS:
* The consuming system requires additional configuration about the
server/services in order to view the layers
* usability of the WMC is limitied by technical issues that can´t be
SUCCESS:
* the OWS Context file can be identified and downloaded from the portal *Geospatial Data
referenced layers, services and in-line content are visible without any
additional configuration
* the consuming system is able to select the appropriate style for each
WMS layer
* the consuming system is able to display the legend associated with
each WMS layer
LIMITED SUCCESS:
* usability of the OWS Context is limitied by technical issues that can´t be
SUCCESS:
* the WMC file can be identified and downloaded from the portal *Geospatial Data
referenced layers are visible without any additional configuration
* the consuming system is able to select the appropriate style for each
layer
* the consuming system is able to display the legend associated with
each layer
LIMITED SUCCESS:
* usability of the WMC is limitied by technical issues that can´t be
SUCCESS:
The consumer has to be able to review the documents and demonstrate *Geospatial Data
an understanding of the content.
* Document is available in English and/or French

* Document is clearly structured, easy to read and understandable
* Document provides sufficient guidance within the technical
specification chapters to afford the development of a product
LIMITED SUCCESS:
* Document is difficult to comprehend and requires domain knowledge
* Specification is poorly worded or incomplete, limiting the scope of a
successful development of a product
* Document is non-sensical and illogical in its structure
* Incomplete or missing specification documents that do not allow
product development
SUCCESS:
The consumer is be able to load the AML into their system and visualise *Geospatial Data
the information, ensuring:
* S-57 AML product renders correctly
* Product meets relevant AML category specification/requirements
LIMITED SUCCESS:
* S-57 AML renders, but with issues
* Partial compliance with targetted category specification
*Issues identified and documented
* S-57 AML product unable to be rendered
SUCCESS:
* Gridded AML product renders correctly
LIMITED SUCCESS:
* Gridded AML renders, but with issues
* Gridded AML product unable to be rendered
SUCCESS:
* Gridded AML product renders correctly
LIMITED SUCCESS:
* Gridded AML renders, but with issues
* Gridded AML product unable to be rendered
SUCCESS:
Consumer is able to access the TDA and the content is satisfactory *Geospatial Data
LIMITED SUCCESS:
Consumer is able to access the TDA but is only partially satisfactory
Consumer is not able to access the TDA or the content is useless
SUCCESS:
* The client can connect to the W3DS. *Geospatial Data
* 3D model is displayed correctly and usable.
LIMITED SUCCESS:
* The 3D model can be requested but not displayed correctly.
* Not all of the request operations work properly.
* Not all output formats can be requested.
* No 3D model can be displayed.
SUCCESS:
* The GML file can be consumed and further processed *Geospatial Data
* The GML file's content is complete
LIMITED SUCCESS:
* The GML can be read but not further used.
* The GML can not be read.
SUCCESS:
* Consumer correctly displays all data received. *Geospatial Data
* Consumer experiences no responsiveness issues.
* When overlaying layers where there is no data, the result is
transparent.
* Hyperlinks can be activated resulting in providers service being called
e.g. display web page, or open PDF file.
* Temporal controls work correctly
LIMITED SUCCESS:
* Consumer correctly displays some but not all of the data in the CSV
document, or experiences minor responsiveness issues.
* Hyperlinks cannot be executed
* Temporal controls do not work as expected.
* Consumer can't display the data in the CSV document correctly, nor
activate the hyperlinks.
SUCCESS:
The consumer can call the service, passing a details of a route. The *Geospatial Data
process then returns a resulting dataset of containing forecast
information for consumption by the consumer client. The resulting
dataset has to reflect that a process has been run on the data.
LIMITED SUCCESS:

SUCCESS:
* Consumer correctly displays all data received. *Geospatial Data
* Consumer experiences no responsiveness issues.
* When overlaying layers where there is no data, the result is
transparent.
* Hyperlinks can be activated resulting in providers service being called
e.g. display web page, or open PDF file.
* Temporal controls work correctly
LIMITED SUCCESS:
* Consumer correctly displays some but not all of the data in the KML
document, or experiences minor responsiveness issues.
* Hyperlinks cannot be executed
* Temporal controls do not work as expected.
* Consumer can't display the data in the KML document correctly, nor
activate the hyperlinks.
SUCCESS:
* the operator of the consuming system is able to ingest the data to be *Geospatial Data
processed by the consuming system
* consuming system displays the data correctly according to reference
system, according to intructions provided by provider
* data can be used natively, no data conversion is carried out before
processing
LIMITED SUCCESS:
* the operator and/or system management of the consuming system
needs additional support besides whats given by available system
documentation to make data displayed in the consuming system
Standards Protocols Services Comments
*CSW 2.0.2 ISO *HTTP *Geospatial

Services
*CSW 2.0.2 NGMP *HTTP *Geospatial

Services
Services
*CSW 2.0.2 NGMP *HTTP *Geospatial

Services
Discuss with GBR - UKHO
Services
GBR Able to host CITE tool again

Services
*WCS 2.0 *HTTP *Geospatial

Services
Services

Services
*WFS 2.0 *HTTP *Geospatial

Services
*WFS 2.0 DGIWG *HTTP *Geospatial
Services
Moved into WFS group
Services
Corrected typo
Services
Services
REMOVE?
*NISP Standard - MIP BL 4 *HTTP *Geospatial
*WFS 2.0 Services
Moved into WFS group

*HTTP *Geospatial
Services
*WMS 1.3 DGIWG *HTTP *Geospatial
Services
GGDM
OGC *HTTP *WMS
*WMS 1.3 *HTTP *Geospatial
Services
Services

Services
Services

Services

Services
Services

Services

Services
Services

Services
Remove OGC tests due to complexity of

*HTTP *Geospatial loading OGC test data set?
Services
Moved into WMS group
*WMTS 1.0 *HTTP *Geospatial

Services
*WMTS 1.0 *HTTP *Geospatial
Services
NEW GROUP CREATED from OTHERS
*NISP Standard - ESRI REST *HTTP *Geospatial

Spec. Services

Spec. Services
Spec. Services

Spec. Services

Spec. Services
Spec. Services

Spec. Services

Spec. Services
Spec. Services

Spec. Services

Spec. Services
CREATED NEW GROUP from OTHER

*WMC 1.1.0 *HTTP *Geospatial
Services
*OWS Context 1.1.0 *HTTP *Geospatial

Services
*WMC 1.1.0 *HTTP *Geospatial
Services
* STANAG 7071
*HTTP *Geospatial
Services
* STANAG 7071
*HTTP *Geospatial
Services
* STANAG 7071
*HTTP *Geospatial
Services
* STANAG 7071
*HTTP *Geospatial
Services
*HTTP *Geospatial
Services
*W3DS 0.3 *HTTP *Geospatial

Services
*GML 3.2.1 DGIF flat *HTTP *Geospatial

Services
*CSV *HTTP *Geospatial

Services
*WPS 1.0 *HTTP *Geospatial
Services
*KML 2.2 *HTTP *Geospatial

Services
* MetCM
*HTTP *Geospatial
Services
Providers Consumers

Testare Si Evaluare Pagini Web Suport de Curs

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Testare Si Evaluare Pagini Web Suport de Curs

Uploaded by

Copyright:

Available Formats

Generation 1 Templates

GeoMetOc - WMS 1.3 basic

GeoMetOc - WMS 1.3 basic with EPSG:4326

GeoMetOc - WMS 1.3 with TIME parameter (no span)

GeoMetOc - WMS 1.3 layerstructure turn on/off layer

GeoMetOc - GeoTiff 8 bit - local data dissemination

GeoMetOc - GeoTiff 16 bit - local data dissemination

GeoMetOc - GRIB1 - local data dissemination - with I & j

GeoMetOc - GRIB2 - local data dissemination

GeoMetOc - WFS 1.1 basic

GeoMetOc - WFS 2.0 cascading

GeoMetOc - WFS-T 2.0

GeoMetOc - WFS 2.0 with dynamic data

The WMS service shall support EPSG:4326.

Provider provides a WMS containing temporal information to be used in this test.

Provider provides a WMS containing temporal information to be used in this test.

The WMS Service shall contain a hierarchy of layers

Provider provides a WMS containing GeoMetOc information.

Provider provides a WFS serving dynamic data such as vehicle tracks.

Consumer consumes the service.

Provider provides a WFS.

*NATO Core GIS

The EPSG codes shall be listed in the GetCapabilities response

Step 4: The consumer displays the retrieved layer.

Step 4: The consumer displays the retrieved layer.

Step 4: The consumer displays the retrieved layer.

Step 3: The consumer toggles on/off of layers

Step 2:The consumer downloads the file.

Step 2:The consumer downloads the file.

Step 2:The consumer downloads the file.

Step 2:The consumer downloads the file.

Step 2:The consumer downloads the file.

Step 2:Consumer attempts to select and zoom to a specific WFS layer.

*Geospatial Data *WMS 1.3 *HTTP *Geospatial Services

*Geospatial Data *WMS 1.3 *HTTP *Geospatial Services

*Geospatial Data *WMS 1.3 *HTTP *Geospatial Services

*Geospatial Data *WMS 1.3 *HTTP *Geospatial Services

*Geospatial Data *NISP Standard - *HTTP *Geospatial Services

*Geospatial Data *NISP Standard - *HTTP *Geospatial Services

*Geospatial Data *HTTP *Geospatial Services

*Geospatial Data *HTTP *Geospatial Services

*Geospatial Data *WMS 1.3 *HTTP *Geospatial Services

*Geospatial Data *WFS 2.0 *HTTP *Geospatial Services

*Geospatial Data *WFS 2.0 *HTTP *Geospatial Services

*Geospatial Data *WFS 2.0 *HTTP *Geospatial Services

Explitly add version to title

Explitly add version to title

Explitly add version to title

Explitly add version to title

GeoMetOc - WMS ELEVATION parameter

GeoMetOc - WMS map legend

GeoMetOc - WCS 2.0 NetCDF

GeoMetOc - WCS 2.0 GRIB1

GeoMetOc - WCS 2.0 GRIB2

GeoMetOc - OGC GeoPackage Raster

The objective of this testcase is to ensure that the

The objective of this testcase is to ensure that the

The objective of this testcase is to ensure that the

The objective of this testcase is to ensure that the

The objective of this testcase is to ensure that the

The objective of this testcase is to ensure that the

The objective of this testcase is to ensure that the

Step 2:Consumer requests a map legend from the WMS

*Geospatial Data *WMS 1.3 *HTTP *Geospatial Services

Geospatial Data WMS 1.3 HTTP Geospatial Services

Geospatial Data WMS 1.3 HTTP Geospatial Services

Geospatial Data WMS 1.3 HTTP Geospatial Services

Geospatial Data WMS 1.3 HTTP Geospatial Services

Geospatial Data NISP Standard - HTTP Geospatial Services

Geospatial Data NISP Standard - HTTP Geospatial Services

Geospatial Data HTTP *Geospatial Services

Geospatial Data HTTP *Geospatial Services

Geospatial Data WMS 1.3 HTTP Geospatial Services

Geospatial Data WFS 2.0 HTTP Geospatial Services

Geospatial Data WFS 2.0 HTTP Geospatial Services

Geospatial Data WFS 2.0 HTTP Geospatial Services

Geospatial Data WMS 1.3 HTTP Geospatial Services

Geospatial Data WMS 1.3 HTTP Geospatial Services

Geospatial Data WCS 2.0 HTTP Geospatial Services

Geospatial Data WCS 2.0 HTTP Geospatial Services

Geospatial Data WCS 2.0 HTTP Geospatial Services

Geospatial Data OGC 12- HTTP Geospatial Services

Geospatial Data OGC 07- HTTP Geospatial Services

HTTP Geospatial Services

HTTP Geospatial Services