Hi Andrea,
I am using in the SLD as per the instructions in the GeoServer User Manual.
But I have gotten a variety of error messages including:
NullPointerException
java.lang.RuntimeException: Unable to find function gridCoverageStats
java.lang.NoSuchMethodError:
org.apache.commons.io.filefilter.FileFilterUtils.and([Lorg/apache/commons/io/filefilter/IOFileFilter;)Lorg/apache/commons/io/filefilter/IOFileFilter;
So I tried to trace back through the log files and found the blacklisting.
At that point I figured I should ask for help before trying to dig into the
code.
I know it's still a community extension, but I have a temperature data set
in and ImageMosaic so the color ramp that works for 9000 pa is useless at
1000 pa and accommodating both is not a great solution. So I was really
happy when I saw this extension. I'm hoping you have a suggestion? Could it
be the Java version?
Ben Shender
On Fri, Apr 11, 2014 at 2:43 AM, Andrea Aime
<[email protected]>wrote:
> On Thu, Apr 10, 2014 at 11:19 PM, Benjamin Shender <[email protected]>wrote:
>
>> Hello all,
>>
>> I am running GeoServer 2.4.3 on Centos 6 using Tomcat6.
>>
>> Java version 1.7.0_51 OpenJDK
>>
>> I am trying to install and use the DynamicColorMap community extension. I
>> extracted the jar in to WEB-INF/lib and restarted the server as usual. On
>> the restart I am receiving this error:
>>
>> 2014-04-10 21:14:42,655 INFO [geoserver.wps] - Blacklisting process
>> ras:DynamicColorMap as the input colorRamp of type interface
>> org.geotools.styling.ColorMap cannot be handled
>>
>
> The process is meant to be used as a rendering transformation in SLD, it
> was not developed to be used as a stand alone process,
> as such, it misses the PPIO class that can parse/encode the input color
> ramp.
> The good news is, it should not be that hard to develop one
>
> About not using it in production, quality varies a lot among community
> modules, they indeed range from non working experiments
> to modules that are being used in anger, but do not yet satisfy all the
> requirements for graduating to official extension (e.g.
> see this proposal for a list of requirements that need to be satisified to
> graduate a module:
>
> http://geoserver.org/display/GEOS/GSIP+105+-+Promote+importer+module+to+extension+status
> )
>
> This one has been in production in a scientific app for a few months now,
> but it does not qualify yet for extension, one of the
> requirements is that it needs 3 known users, so far it has one.
>
> It is indeed true, though, that a module staying for a long time in
> community land tends to rot over time, as it's not normally
> even built (as such, it can stop compiling or passing tests without any
> warning).
>
> Cheers
> Andrea
>
> --
> ==
> Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK
> 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
>
> -------------------------------------------------------
>
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
