Mercurial > dive4elements > river
view artifacts/doc/conf/log4j.properties @ 8722:a83d519155ab
(issue1754) Do not base smoothing radius on calculation range
Using the calculation parameters for startkm and endkm in the
case that the domain axis had the default extend caused weird
behavior when zooming and led to too large radius values for
most data that only had valid values on a subset of the caluclation
range.
| author | Andre Heinecke <andre.heinecke@intevation.de> |
|---|---|
| date | Tue, 28 Apr 2015 14:22:47 +0200 |
| parents | e5349f886c93 |
| children | 28df64078f27 |
line wrap: on
line source
log4j.rootLogger=DEBUG, FLYS ########## EXTERNAL PACKAGES log4j.category.org.hibernate=WARN log4j.category.net.sf.ehcache=WARN log4j.category.org.eclipse=WARN log4j.category.org.restlet=INFO ########## APPENDER SETTINGS log4j.appender.FLYS.layout=org.apache.log4j.PatternLayout log4j.appender.FLYS.layout.ConversionPattern=%d{HH:mm:ss} [%t] %-5p %c{1} - %m%n log4j.appender.FLYS=org.apache.log4j.RollingFileAppender log4j.appender.FLYS.File=/var/log/d4e-river/d4e-server.log log4j.appender.FLYS.MaxFileSize=5000KB log4j.appender.FLYS.MaxBackupIndex=1 log4j.logger.org.dive4elements.artifactdatabase.rest.Standalone=INFO, START log4j.appender.START=org.apache.log4j.ConsoleAppender log4j.appender.START.Target = System.out log4j.appender.START.layout = org.apache.log4j.PatternLayout log4j.appender.START.layout.ConversionPattern=%d %m%n