Jody Garnett ha scritto: > Andrea Aime wrote: >> Jody Garnett ha scritto: >> ... >>> So I can think of several recommendations of areas that would love >>> some work in the gt-main.jar: >>> - high priority, nobody working on it: EqualIntervalFunction and >>> EqualIntervalFunctionTest processes a FeatureCollection and returns a >>> "Classifier" (a series of ranges) that split the data up into groups >>> - this is used to generate really pretty styles. >> I'm using them right now and they seem to be working? > I had at least one of these functions failing its test cases last I > looked; have you been fixing things when I was not looking andrea?
Which test cases are you talking about? The build is working? Oh, do you mean the postgis feaure collection ones depending on a database you only have? Those I killed yesterday replacing them with tests that do work over the standard testing data (a correctness test does not need tables with thousands of data) and yes, they are working now (after my yesterday's patches, that is). >>> - low priority easy introduction: Eclesia has found a series of >>> excellent functions as part of the Symbology Encoding specification; >>> for things like concatenating Strings, formatting Dates and so on .. >>> all of these are nice small Functions that can be written up and are >>> a good introduction to how the library is stitched together. >> String concatenation we already have, look at FilterFunction_strConcat >> and at tens of its friends in the main module >> (org.geotools.filter.function package) > I know; but now the SE specification has a specific one out ... the joys > of interoperability results in some duplication. You guys were taking > part in OWS5 and did not catch this one ... so here we are. SLD was not in the picture during OWS5? We participated in WCS 1.1.1 cite, WFS 1.1 + xlink cite, KML experiments. We used a bit of SLD 1.0 in the last one, both us and Cubewerx (SE 1.1 was taken out of the question from day one since none of the testers supported it). > function: Substring > parameter 0: expression > parameter 1: position > parameter 2: length > > function: Concatenate > parameter N: expression > > function: ChangeCase > parameter 0: expression > parameter 1: direction - either "toUpper" or "toLower" (if you want you > can capture this as an enumeration "DirectionType" and define a > Converter ... > > function: Trim > parameter 0: expression > parameter 1: stripOffPosition - either "leading, trailing, or both > parameter 2: stripOffChar > > I am not saying these ones are hard, just that it is work needing doing. > > Andrea note that the "Concatenate" function takes any number of strings > which is a new trick for our Funtion API. I see, interesting... Does it mean we have to change the API (did not look). Cheers Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
