> After reading the technical guidance, I come to the conclusion that three
> mandatory elements are missing:
>
> * Metadata about supported languages and response languages
> (inspire_vs:ExtendedCapabilities).
> * Metadata for each layer (ows:Metadata), this is optional in WMTS
> standard.
> * Styles legend URL this, is optional in WMTS standard.
>
> There is also the harmonized layer names requirement ... going through the
> GeoServer UI and INSPIRE module
> documentation I could not found if this is supported or not (basically we
> need to drop the work space prefix
> which can lead to layer names collisions this is why I'm wondering if this
> is supported or not).
>
What is the "harmonized layer name requirement"?
- Do the names need to be consistent within the service - if so including
the namespace prefix consistently everywhere would be fine?
- If not consider that only virtual WMS and WMTS services could be
compliant (not the global service).
What part of the prefix is throwing off the standard - do they enforce a
naming convention beyond the WMS spec?
>
> INSPIRE also brings this two mandatory constraints:
>
> * The output format should be either PNG or GIF format. (without LZW
> compression)
>
> * It is mandatory to use geographical coordinate system based on ETRS89 in
> continental Europe and ITRS outside continental Europe.
>
> A service admin page will be created for WMTS, we need this to provide a
> specific URL metedata that will
> describe the service itself.
>
You may need to pursue this in partnership with the GeoWebCache codebase,
since WMTS protocol is implemented there (and we embed the resulting
application).
Ideally all the needed changes will be contributed to the INSPIRE extension
> module. But first, we need a way to extend
> the WMTS service GetCapabilities operation result. I could not found any
> existing extension points that will
> allow me to do this. In this thread
>
> http://osgeo-org.1560.x6.nabble.com/Adding-a-multidimensional-extension-to-WMTS-as-a-GeoServer-community-module-with-integrations-with-G-td5268826.html
>
> Andrea Aime proposes the WMTSExtension interface ... this could be a
> solutions for this.
>
I do not know enough about the GeoWebCache codebase, perhaps join that
developer list and sort out an approach. You can also make a proposal when
ready to outline the approach you wish to take.
One more thing, the INSPIRE validator complains that
> MinTileRow, MaxTileRow, MinTileCol and MaxTileCol values are out of range,
> I still
> don't understand why he is complaining about those values.
>
What are the values?
> This is all the information I gathered until now, feedback on this will be
> appreciated :)
>
Thanks for sharing, look forward to hearing how this work goes :)
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
