Closed j3r3m1 closed 8 months ago
Thanks I will check
I'm on it
400000 this is a crazy area ;-)
The issue seems at another place. Indeed, Aatest case returns
java.lang.NullPointerException: Cannot invoke method minus() on null object
at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:91)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:44)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:34)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:139)
at org.orbisgis.geoclimate.geoindicators.RsuIndicators.frontalAreaIndexDistribution(RsuIndicators.groovy:2020)
The returned OSM file is too large. The OSM file contains the following message
<remark> runtime error: Query ran out of memory in "query" at line 18. It would need at least 905 MB of RAM to continue. </remark>
Fixed with #892
Some users have tried to run a very large area. It goes up to the end of the calculation but there is no data processed. It seems the data are downloaded but they are not imported (or correctly imported) within H2GIS database. I wonder where is the problem but there is definitely an error that should be logged while GeoClimate goes up to the end but create no results.