Re: [Geoserver-users] Questions about layer naming

On Sun, Apr 26, 2015 at 7:44 AM, Martin Davis wrote: > 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/p

Re: [Geoserver-users] Questions about layer naming

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 wrote: > On Fr

Re: [Geoserver-users] Questions about layer naming

Ok. For minimizing troubles might be good to mention that ASCII characters are most safe Jukka Lähettäjä: Andrea Aime Lähetetty: ‎25.‎4.‎2015 16:03 Vastaanottaja: Rahkonen Jukka (MML)

Re: [Geoserver-users] Questions about layer naming

On Sat, Apr 25, 2015 at 3:00 PM, Rahkonen Jukka (MML) < jukka.rahko...@maanmittauslaitos.fi> wrote: > Isn't it NCName only for WCS 2.x and QName for WFS? Think about > topp:states. > GeoServer builds a QName by prefixing it with the workspace name, thus, to have a valid QName, you must give GeoS

Re: [Geoserver-users] Questions about layer naming

Isn't it NCName only for WCS 2.x and QName for WFS? Think about topp:states. Jukka Lähettäjä: Andrea Aime Lähetetty: ‎25.‎4.‎2015 12:08 Vastaanottaja: Martin Davis Kopio: Rahkonen Jukka (MML)

Re: [Geoserver-users] CSS module questions

On Fri, Apr 24, 2015 at 8:20 PM, Jim Hughes wrote: > >> 2. How does the CSS extension interact with GeoServer's SLD extensions? >> > > It's a translator to SLD, GeoServer and the rendering subsytem really > only handle the latter. > If you are about to ask about working off the CSS directly, It

Re: [Geoserver-users] Questions about layer naming

On Fri, Apr 24, 2015 at 9:42 PM, Martin Davis 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 >