Great, that's very complete.
This could be added as a note in the section
http://docs.geoserver.org/stable/en/user/webadmin/data/layers.html#basic-info
... as soon as this is merged:
https://github.com/geoserver/geoserver/pull/1025
On Sat, Apr 25, 2015 at 2:08 AM, Andrea Aime <[email protected]>
wrote:
> On Fri, Apr 24, 2015 at 9:42 PM, Martin Davis <[email protected]> wrote:
>
>> Ok, how about:
>>
>> Names must be compatible with their use in OWS service requests and
>> response documents. For general use, consider using only the
>> characters: upper and lowercase letters, numbers, dash, underscore and
>> period. Spaces can be present, but will need to be escaped in URLs.
>>
>> The wording "consider using" is meant to indicate this is only a
>> suggestion to avoid possible pain, not a validation rule.
>>
>
> Let me try a (longer) variation, removing spaces from the general rule as
> they are not valid for WFS/WCS 2.0
>
>
> --------------------------------------------------------------------------------------------------------------------
> Different OGC protocol have different requirements on layer names.
> If you want a single rule that will make layer names across protocols, use
> only upper and lowercase letters, numbers, dash, underscore and period,
> and make sure the name starts with a letter.
>
> If instead you're interested in using only a subset of the protocols, here
> is a summary:
> * WCS 1.0, 1.1 and WMS pose no limit whatsoever on the layer names, which
> can contain pretty much any character
> * WFS (all versions) and WCS 2.0 require the layer name you give to
> GeoServer to be an NCName, that is, a non colonized name. A NCName cannot
> contain several symbol characters like colon, @, $, %, &, /, +, comma,
> semicolon, whitespace characters or different parenthesis. Furthermore an
> NCName cannot begin with a number, dot or minus character although they can
> appear later in an NCName.
>
> --------------------------------------------------------------------------------------------------------------------
>
> Cheers
> Andrea
>
>
> --
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/NWWaa2 for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 339 8844549
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
> darcene notizia via e-mail e di procedere alla distruzione del messaggio
> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
> principi dettati dal D.Lgs. 196/2003.
>
>
>
> The information in this message and/or attachments, is intended solely for
> the attention and use of the named addressee(s) and may be confidential or
> proprietary in nature or covered by the provisions of privacy act
> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> Code).Any use not in accord with its purpose, any disclosure, reproduction,
> copying, distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender
> does not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility for changes
> made after they were sent or for other risks which arise as a result of
> e-mail transmission, viruses, etc.
>
> -------------------------------------------------------
>
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
