[Geoserver-devel] Commas in custom dimensions and getCapabilities

GeoServer GeoServer Developer
1

Hi all,
I’m trying to build a mosaic using a custom domain which contains special characters (commas, apostrophe, etc) in dimension values.

In my CROP dimension I have
1 Cereals
2 Oil, crops
3 Root

The result in the getCapabilities is:
…
Cereals,Oil,crops,Root

…

Which is exactly what the standard says but essentially it is wrong…

<<The extent string declares what value(s) along the Dimension axis are appropriate for the corresponding layer.
The extent string has the syntax shown in Table C.2.>>
Ref:
http://www.opengeospatial.org/standards/wms

To be correct it should be something like:

…

“Cereals”,“Cereals”,“Oil, crops”,“Root”

…

Anyhow this is not very close to the standard.
I’m considering adding quotes to all of my dimension values but this is probably not acceptable for all.

What do you think?

Cheers,
Carlo

–

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Dott. Carlo Cancellieri
@cancellieric
Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
mobile: +39 3371094494
fax: +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

2

On Fri, Oct 11, 2013 at 7:05 PM, carlo cancellieri <
carlo.cancellieri@anonymised.com> wrote:

Hi all,
I'm trying to build a mosaic using a custom domain which contains special
characters (commas, apostrophe, etc) in dimension values.

In my CROP dimension I have
1 Cereals
2 Oil, crops
3 Root

The result in the getCapabilities is:
....
<Dimension name="CROP"
default="Cereals"
units="">Cereals,Oil,crops,Root
</Dimension>
...

Which is exactly what the standard says but essentially it is wrong...

<<The extent string declares what value(s) along the Dimension axis are
appropriate for the corresponding layer.
The extent string has the syntax shown in Table C.2.>>
Ref:
http://www.opengeospatial.org/standards/wms

To be correct it should be something like:
....
<Dimension name="CROP"
default="Cereals"
units="">"Cereals","Cereals","Oil, crops","Root"
</Dimension>
...

Anyhow this is not very close to the standard.
I'm considering adding quotes to all of my dimension values but this is
probably not acceptable for all.

Adding quotes around the dimension values will most likely break the wms
standard, and standard clients
will simply ignore them.
In other words, to a compliant standard, the above list defines the
following possible values:
"Cereals"
"Cereals"
"Oil
crops"
"Root"

ant then they will add to the GetMap request ...&DIM_CROP="Oil&...

Long story short, your use case places you out of the WMS standard reach,
and the solution will break
any standard client.

My suggestion: don't try to use human readable values for your dimensions,
use codes and have a lookup
table to turn them into human readable ones for your clients

Cheers
Andrea

--

Our support, Your Success! Visit http://opensdi.geo-solutions.it 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

-------------------------------------------------------

3

On Fri, Oct 11, 2013 at 7:46 PM, Andrea Aime
<andrea.aime@anonymised.com>wrote:

In other words, to a compliant standard, the above list defines the
following possible values:

Ah hem... "to a standard compliant client, the above list..."

Cheers
Andrea

--

Our support, Your Success! Visit http://opensdi.geo-solutions.it 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

-------------------------------------------------------