Re: [Geotools-devel] symbology encoding: recode function

2010-05-20 Thread Michael Bedward
Yes, let's make it null. Michael On 20 May 2010 17:17, Andrea Aime wrote: > > So recode acts like an hashamp right, it's a key/value transformation? > I would say, we return null if the key is not known. Same contract > as a java Map? > ---

Re: [Geotools-devel] symbology encoding: recode function

2010-05-20 Thread Andrea Aime
Michael Bedward ha scritto: > Hi folks, > > I'm looking at getting the Recode function working but, as usual, the > symbology encoding specs are quiet about some of the fiddly bits... > It's basically just a table lookup. > > Questions: What do we return if the lookup value isn't found ? So re

Re: [Geotools-devel] symbology encoding: recode function

2010-05-20 Thread Jody Garnett
On 20/05/2010, at 4:53 PM, Michael Bedward wrote: > Hi Jody, > >> There is something you may of missed in the spec... >> >> See where it returns se:Function? That mandates that a "fallback" value is >> provided; I >> think that the fallback value may be used in cases where lookup value is not

Re: [Geotools-devel] symbology encoding: recode function

2010-05-19 Thread Michael Bedward
Hi Jody, > There is something you may of missed in the spec... > > See where it returns se:Function?  That mandates that a "fallback" value is > provided; I > think that the fallback value may be used in cases where lookup value is not > found. Unfortunately I don't think that's right. For func

Re: [Geotools-devel] symbology encoding: recode function

2010-05-19 Thread Jody Garnett
There is something you may of missed in the spec... See where it returns se:Function? That mandates that a "fallback" value is provided; I think that the fallback value may be used in cases where lookup value is not found. I agree that text lookups should be case-insensitvie. You may also enjo

[Geotools-devel] symbology encoding: recode function

2010-05-19 Thread Michael Bedward
Hi folks, I'm looking at getting the Recode function working but, as usual, the symbology encoding specs are quiet about some of the fiddly bits... It's basically just a table lookup. Questions: What do we return if the lookup value isn't found ? Should text lookups be case-insensitive ? (I woul