Great, all good advice. I was curious about the provenance of the
featuretype naming standard, so spelunked through the standards docs to get
the final word... The WFS spec [1] says that a typename must be a XML
Qname, and the XML spec [2] says that a QName Name part must start with a
letter or underscore.
So now it could say:
Names must be compatible with their use in OWS service requests and
response documents. Names must start with a letter or underscore. Spaces
can be present, but will need to be escaped in URLs. For general use,
consider using only the following characters: upper and lowercase letters,
numbers, dash, underscore and period.
[1] https://portal.opengeospatial.org/files/?artifact_id=8339
[2] http://www.w3.org/TR/REC-xml/#NT-NameStartChar
(Wouldn't it be great if the OGC specs were HTML...)
On Fri, Apr 24, 2015 at 10:36 AM, Rahkonen Jukka (MML) <
[email protected]> wrote:
> Hi,
>
>
> Yes, spaces are allowed and they are very common in WMS services made
> with ESRI servers.
>
> I think that Geoserver users have had trouble with periods but I am not
> sure. Absolutely comma in a layer name has caused troubles, think about
> GetMap: &layers=fine_idea,of_my_own.
>
>
> WFS is so common service and folks are publishing layers with both WMS
> and WFS that it might be good to especially mention that name of a
> featuretype must not (according to standard) begin with a number or
> underscore.
>
>
> Good test for ourselves would be to test sometimes what Geoserver
> accepts and what kind of escaping is needed
>
> - What we can cascade with WMS?
>
> - What we can cascade with WFS?
>
>
> "Before you accuse me, have a look at yourself".
>
>
> -Jukka Rahkonen-
>
>
>
>
> ------------------------------
> Andrea Aime wrote:
>
> On Fri, Apr 24, 2015 at 4:49 PM, Martin Davis <[email protected]>
> wrote:
>
>> Roger that. How about:
>>
>> Names must be compatible with their use in OWS service requests and
>> response documents. In particular, they must not contain spaces. For
>> general use, it is best if they use only the following characters: upper
>> and lowercase letters, numbers, dash, underscore and period.
>>
>
> As far as I know, spaces are also valid (in WMS), you just have to
> url-encode them when making requests
>
> 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
