[Inspire-data] Re: [OSGeo-UK] GeoWebCache for INSPIRE WMS View Service

[Seven (aka Arnulf)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tom,
just two side notes: There is no such thing as an INSPIRE *compliant*
service. A real compliance would require a test suite which can be
passed by the service and no such thing has been provided by the
commission yet.

The second note is that the INSPIRE Technical Guidelines are not legally
binding. This means that nothing of what they say wrt. usage of a
standard is binding. Any means that gives access to your data and maps
and satisfies the Implementing Rules (which are legally binding as they
have been passed as laws in your country) will be just fine.

On one hand this is rather unfortunate because it will make
interoperability much harder than it would have been even by sticking
closely to an official OGC standard. On the other hand it means that you
can be a lot more creative with INSPIRE than it might first make the
impression.

There are other details like the "Transformation Services" which imply
by "service" that this need to be an Online tool. This is not the case.
The only requirement it to provide the data in a common coordinate
reference system and abiding to the rules for data encoding. "How" to do
this is up to you. The INSPIRE Technical Guidelines are just a friendly
suggestion of how it could be done.


I will try to blog about this in a coherent way and more detail over the
weeked as it seems that most everybody involved with INSPIRE believes
that it has legally binding technical requirements. It has not.

The situation is a bit different with the data specifications which are
in the doing now. Here the schemas give a much tighter framework which
has to be satisfied. But it will also need some official test suite to
prove "compliance" which as of now does not yet exist.

Cheers,
Arnulf

PS:
CCing INSPIRE data mailing list whichmight have more information.

On 08.12.2011 17:00, Tom Moore wrote:
> Forth Valley GIS have recently spent a lot of time investigating the use of
> GeoWebCache to deliver INSPIRE compliant View services.  Having to handle
> large data sets > 1million records means that INSPIRE compliant caching in
> GeoWebCache is a must.
> 
> So far we have done and discovered the following:
> 
> Our installation is currently very simple - we have one instance of
> geoserver, installed as a windows service.  We have been using the
> integrated version of geowebcache bundled with geosever, so geowebcahce is
> running as part of the same windows service as geoserver.  We have installed
> the INSPIRE community plugin on geoserver.
> 
> 
> Currently our service is INSPIRE and wms 1.3.0 compliant, but does not serve
> cached tiles.  Our objective is to be able to serve INSPIRE compliant WMS
> 1.3.0 tiles and capabilities documents to clients making both wms-c and
> arbitrary wms requests, and that is what we are having difficulty with.  
> 
> We have been able to seed our cache in geowebcache and switch on automatic
> integration with geowebcache on our test server, and have achieved the
> following results:
>  
> http://host_url/geoserver/wms?service=wms&version=1.1.1&request=getcapabilities
> - returns a 1.1.1 capabilities document without gridset information
> http://host_url/geoserver/wms?service=wms&version=1.1.1&request=getcapabilities&TILED=true
> - returns an empty capabilities document
> http://host_url/geoserver/wms?service=wms&version=1.3.0&request=getcapabilities&TILED=true
> - returns a 1.3.0 capabilities document without any gridset information
> http://host_url/geoserver/gwc/service/wms?service=wms&version=1.1.1&request=getcapabilities&TILED=true
> - returns a 1.1.1 capabilities document with gridset information
> http://host_url/geoserver/gwc/service/wms?service=wms&version=1.3.0&request=getcapabilities&TILED=true
> - returns a 1.1.1 capabilities document with gridset information
>  
> wms client making arbitrary 1.1.1 or 1.3.0 getmap (non wms-c) requests to
> http://host_url/geoserver/  - Does not cache.
> wms client making arbitrary 1.1.1 or 1.3.0 getmap (non wms-c) requests to
> http://host_url/geoserver/gwc/service  - Does not cache.
> wms-c client making gridset conforming 1.1.1 or 1.3.0 getmap requests to
> http://host_url/geoserver/gwc/service - Caches
> wms-c client making gridset conforming 1.1.1 getmap requests to
> http://host_url/geoserver - Caches
> wms-c client making gridset conforming 1.3.0 getmap requests to
> http://host_url/geoserver - does not cache
> 
> We have therefore come to the following conclusions/observations:
> Geowebcache only support wms 1.1.1 
> Geowebcache cannot publish capabilities documents for wms 1.3.0 services,
> and therefore cannot support INSPIRE since this is built on the 1.3.0
> standard, 
> The INPSPIRE and wms 1.3.0 capabilities of geoserver do not extend to
> geowebcache 
> The geowebcache documentation suggests that geowebcache can be configured to
> recombine and resample tiles to answer arbitrary WMS requests, but I this
> does not seem to be possible in the integrated/bundled version of
> geowebcache
> 
> 
> Has anyone else on this list had experience in regards to this problem? 
> Does anyone have a solution that works with GeoServer?
> We have contacted OpenGeo directly, but have not had a response in regards
> to the upgrade of GeoWebCache for WMS 1.3.0 and extended INSPIRE
> GetCapabilities documents.  Does anyone know of the delivery horizon for
> this functionality?  
> 
> --
> View this message in context: http://osgeo-org.1803224.n2.nabble.com/GeoWebCache-for-INSPIRE-WMS-View-Service-tp7074778p7074778.html
> Sent from the OSGeo UK Local Chapter mailing list archive at Nabble.com.
> _______________________________________________
> UK mailing list
> UK at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/uk


- -- 
Exploring Space, Time and Mind
http://arnulf.us
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7g7ZAACgkQXmFKW+BJ1b0JtgCeOaeyxWa9Vtc20gXPEwMwtBgN
mVMAniDgvhvzTvgjtwSRe0i/V58pLcwJ
=B8qa
-----END PGP SIGNATURE-----