> If we publish a layer that match a layer present in the INSPIRE data
> specifications we should use the pre-defined name:
>
> http://inspire.jrc.ec.europa.eu/documents/Data_Specifications/annex2and3_guidance_documents.zip
>
> GeoServer appends the workspace as a prefix to the layer name, hence
> (unless I miss something) we are not able to use the pre-defined name.
>
1. So use virtual web service end point and the prefix wont be listed /
required.
2. You could also publish these layers in the workspace nominated as the
default workspace, then the prefix would not be required. But I expect the
capabilities document would still list the prefix?
If you really need to suppress the prefix I expect you will need to follow
#2 and supress the prefix in the GetCapabilities document when publishing
the default workspace.
The images formats constraint can be forced with an ows:Constraint element
> for each layer in the get capabilities result.
> Being only able to query tiles in GIF or PNG is very restrictive, we may
> add the option to only include this constraints if we are in a strict
> INSPIRE compliance mode.
>
Surely that constraint is only addative in nature, listed formats that must
be required...
Good luck!
------------------------------------------------------------------------------
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
