Re: [JPP-Devel] Some Sextante tools don't like negative pixel values
not sure on the how. not familiar with XML2Java myself. but any solution not throwing errors but using senseful defaults if appropriate sounds reasonable to me. it's already dealt with conditionally in com.vividsolutions.jump.util.java2xml.XML2Java$1.attributeSpecFound(XML2Java.java:147) so why not instead of logging an error setting a default value? again, only if that makes sense. this seems to be thrown even when starting OJ and have it create an initial project. why? where exactly are these xml infos (styles?) stored that OJ is trying to restore? after a look i could give a more informed opinion. ..ede On 27.12.2020 19:43, Michaud Michael wrote: > Hi Ede, > > I'm not aware of a mechanism to define a default value in XML2Java framework. > Currently, the default behaviour is to throw an exception if an attribute > defined in a .java2xml configuration file is not there (null). Warning > instead of throwing an exception is just a nasty hack we added to assure > backward compatibility (attribute names logging a warn message are hard-coded > in the XML2Java class). > > It could make sense to add a "default" attribute in the .java2xml object > specification to manage this kind of situation in a proper way. Ex : > > > > I can do a Feature Request in that way if you think it is a good idea. > > Michaël > > >> envoyé : 27 décembre 2020 à 16:38 >> de : edgar.sol...@web.de >> à : jump-pilot-devel@lists.sourceforge.net >> objet : Re: [JPP-Devel] Some Sextante tools don't like negative pixel values >> >> >> Mike, >> >> On 23.12.2020 11:42, Rahkonen Jukka (MML) wrote: >> >>> - about the warning : yes, this warning has been added with the interior >>> border capability. Maybe it is not really useful. It throws a warning >>> because 'interior' attribute is not really an optional tag, but it is >>> accepted (hard-coded exception) in order to guarantee backward >>> compatibility. >>> >> is there a specific reason why it is mandatory as opposed to just use a >> default value when it is missing? isn't it safe to assume we come from a old >> version if it is missing? >> >> ..ede >> >> >> ___ >> Jump-pilot-devel mailing list >> Jump-pilot-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >> > > > ___ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Some Sextante tools don't like negative pixel values
Hi Ede,I'm not aware of a mechanism to define a default value in XML2Java framework. Currently, the default behaviour is to throw an exception if an attribute defined in a .java2xml configuration file is not there (null). Warning instead of throwing an exception is just a nasty hack we added to assure backward compatibility (attribute names logging a warn message are hard-coded in the XML2Java class).It could make sense to add a "default" attribute in the .java2xml object specification to manage this kind of situation in a proper way. Ex :I can do a Feature Request in that way if you think it is a good idea.Michaëlenvoyé : 27 décembre 2020 à 16:38de : edgar.sol...@web.deà : jump-pilot-devel@lists.sourceforge.netobjet : Re: [JPP-Devel] Some Sextante tools don't like negative pixel valuesMike,On 23.12.2020 11:42, Rahkonen Jukka (MML) wrote:- about the warning : yes, this warning has been added with the interior border capability. Maybe it is not really useful. It throws a warning because 'interior' attribute is not really an optional tag, but it is accepted (hard-coded exception) in order to guarantee backward compatibility.is there a specific reason why it is mandatory as opposed to just use a default value when it is missing? isn't it safe to assume we come from a old version if it is missing?..ede___Jump-pilot-devel mailing listJump-pilot-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/jump-pilot-devel ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Some Sextante tools don't like negative pixel values
Mike, On 23.12.2020 11:42, Rahkonen Jukka (MML) wrote: > - about the warning : yes, this warning has been added with the interior > border capability. Maybe it is not really useful. It throws a warning because > 'interior' attribute is not really an optional tag, but it is accepted > (hard-coded exception) in order to guarantee backward compatibility. is there a specific reason why it is mandatory as opposed to just use a default value when it is missing? isn't it safe to assume we come from a old version if it is missing? ..ede ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Some Sextante tools don't like negative pixel values
Hi, About the NumberFormatException with OpenJDK 11, it seems to have something to do with the locale. Error happens with my default settings (Finnish) but not when I use set JAVA_OPTS=%JAVA_OPTS% -Duser.language=en -Duser.country=EN It would be irritating if characters used as decimal separator will start to make trouble with JDK 11 and higher. Let’s hope that it does not happen generally. -Jukka Rahkonen- Lähettäjä: Michaud Michael Lähetetty: keskiviikko 23. joulukuuta 2020 12.11 Vastaanottaja: Rahkonen Jukka (MML) Aihe: Re: [JPP-Devel] Some Sextante tools don't like negative pixel values Wow, These are other errors. Not sure it is related to yesterday's report. May be it is worth writing a proper bug report about each : - NumberFormatException in yesterday's report : probably a bug in the way we display numbers in the dialog of VectorizeToContoursPlugIn. I need to reproduce the problem but until now I can't (I used your image with negative values and OpenJDK11) - NullPointerException in VectorizeToPolygonsPlugIn with java 8 : I can reproduce. Will investigate and try to fix ASAP. - NoSuchFileException : no idea. There is no plugin name in the stacktrace. Seems to happen during OpenJUMP initialization. I don't know what is this "OpenJUMP-20201222-r6656-PLUS\conf" file or directory it is looking for. Maybe Ede will have a better idea as the error happens in the PlugInClassLoader - about the warning : yes, this warning has been added with the interior border capability. Maybe it is not really useful. It throws a warning because 'interior' attribute is not really an optional tag, but it is accepted (hard-coded exception) in order to guarantee backward compatibility. Michaël envoyé : 23 décembre 2020 à 10:10 de : "Rahkonen Jukka (MML)" mailto:jukka.rahko...@maanmittauslaitos.fi>> à : Michaud Michael mailto:m.michael.mich...@orange.fr>>, OpenJump develop and use mailto:jump-pilot-devel@lists.sourceforge.net>> objet : Re: [JPP-Devel] Some Sextante tools don't like negative pixel values Hi, Yes, the tools are in the Raster menu. It seems that this issue happens with Java 11 but not with Java 8 ( versions I have are OpenJDK 11 and Corretto 8) With Java 8 * Countours are OK (but user should know that contours must be created for the raw, not colorized image) * Histogram is OK * Create Polygons From Raster – AdbToolbox gives NPE java.lang.NullPointerException at org.openjump.core.rasterimage.algorithms.VectorizeAlgorithm.toPolygonsAdbToolBox(VectorizeAlgorithm.java:111) at org.openjump.core.ui.plugin.raster.VectorizeToPolygonsPlugIn.run(VectorizeToPolygonsPlugIn.java:170) at com.vividsolutions.jump.workbench.ui.task.TaskMonitorManager$TaskWrapper.run(TaskMonitorManager.java:151) Start with Java 11 prints also something that Java 8 does not into console window: ---Start OJ--- java.nio.file.NoSuchFileException: C:\ohjelmat\OJ\OpenJUMP-20201222-r6656-PLUS\conf at java.base/sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:85) at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:96) at java.base/sun.nio.fs.WindowsLinkSupport.getRealPath(WindowsLinkSupport.java:257) at java.base/sun.nio.fs.WindowsPath.toRealPath(WindowsPath.java:891) at java.base/sun.nio.fs.WindowsPath.toRealPath(WindowsPath.java:42) at com.vividsolutions.jump.workbench.plugin.PlugInClassLoader.toFileURL(PlugInClassLoader.java:140) at com.vividsolutions.jump.workbench.plugin.PlugInClassLoader.addClassPathToUCP(PlugInClassLoader.java:121) at com.vividsolutions.jump.workbench.plugin.PlugInClassLoader.(PlugInClassLoader.java:27) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) at java.base/java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1977) at java.base/java.lang.System.initPhase3(System.java:2069) And both Java 8 and Java 11 prints this warning about 30 times during the startup. It must have something to do with the new style option “Interior border (slow)”. [WARN] 10:50:51.916 Expected 'interior' attribute but found none. Tag = line; Attributes = [Attribute: enabled="true"], [Attribute: width="1"] -Jukka- Lähettäjä: Michaud Michael mailto:m.michael.mich...@orange.fr>> Lähetetty: tiistai 22. joulukuuta 2020 23.36 Vastaanottaja: OpenJump develop and use mailto:jump-pilot-devel@lists.source
Re: [JPP-Devel] Some Sextante tools don't like negative pixel values
Hi, I guess that the warnings about the missing interior tags come from the predefined styles that we have in the style editor. Would it break opening OJ projects with older versions if this tag would be added to predefined styles? -Jukka- Lähettäjä: Michaud Michael Lähetetty: keskiviikko 23. joulukuuta 2020 12.11 Vastaanottaja: Rahkonen Jukka (MML) Aihe: Re: [JPP-Devel] Some Sextante tools don't like negative pixel values Wow, These are other errors. Not sure it is related to yesterday's report. May be it is worth writing a proper bug report about each : - NumberFormatException in yesterday's report : probably a bug in the way we display numbers in the dialog of VectorizeToContoursPlugIn. I need to reproduce the problem but until now I can't (I used your image with negative values and OpenJDK11) - NullPointerException in VectorizeToPolygonsPlugIn with java 8 : I can reproduce. Will investigate and try to fix ASAP. - NoSuchFileException : no idea. There is no plugin name in the stacktrace. Seems to happen during OpenJUMP initialization. I don't know what is this "OpenJUMP-20201222-r6656-PLUS\conf" file or directory it is looking for. Maybe Ede will have a better idea as the error happens in the PlugInClassLoader - about the warning : yes, this warning has been added with the interior border capability. Maybe it is not really useful. It throws a warning because 'interior' attribute is not really an optional tag, but it is accepted (hard-coded exception) in order to guarantee backward compatibility. Michaël envoyé : 23 décembre 2020 à 10:10 de : "Rahkonen Jukka (MML)" mailto:jukka.rahko...@maanmittauslaitos.fi>> à : Michaud Michael mailto:m.michael.mich...@orange.fr>>, OpenJump develop and use mailto:jump-pilot-devel@lists.sourceforge.net>> objet : Re: [JPP-Devel] Some Sextante tools don't like negative pixel values Hi, Yes, the tools are in the Raster menu. It seems that this issue happens with Java 11 but not with Java 8 ( versions I have are OpenJDK 11 and Corretto 8) With Java 8 * Countours are OK (but user should know that contours must be created for the raw, not colorized image) * Histogram is OK * Create Polygons From Raster – AdbToolbox gives NPE java.lang.NullPointerException at org.openjump.core.rasterimage.algorithms.VectorizeAlgorithm.toPolygonsAdbToolBox(VectorizeAlgorithm.java:111) at org.openjump.core.ui.plugin.raster.VectorizeToPolygonsPlugIn.run(VectorizeToPolygonsPlugIn.java:170) at com.vividsolutions.jump.workbench.ui.task.TaskMonitorManager$TaskWrapper.run(TaskMonitorManager.java:151) Start with Java 11 prints also something that Java 8 does not into console window: ---Start OJ--- java.nio.file.NoSuchFileException: C:\ohjelmat\OJ\OpenJUMP-20201222-r6656-PLUS\conf at java.base/sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:85) at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:96) at java.base/sun.nio.fs.WindowsLinkSupport.getRealPath(WindowsLinkSupport.java:257) at java.base/sun.nio.fs.WindowsPath.toRealPath(WindowsPath.java:891) at java.base/sun.nio.fs.WindowsPath.toRealPath(WindowsPath.java:42) at com.vividsolutions.jump.workbench.plugin.PlugInClassLoader.toFileURL(PlugInClassLoader.java:140) at com.vividsolutions.jump.workbench.plugin.PlugInClassLoader.addClassPathToUCP(PlugInClassLoader.java:121) at com.vividsolutions.jump.workbench.plugin.PlugInClassLoader.(PlugInClassLoader.java:27) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) at java.base/java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1977) at java.base/java.lang.System.initPhase3(System.java:2069) And both Java 8 and Java 11 prints this warning about 30 times during the startup. It must have something to do with the new style option “Interior border (slow)”. [WARN] 10:50:51.916 Expected 'interior' attribute but found none. Tag = line; Attributes = [Attribute: enabled="true"], [Attribute: width="1"] -Jukka- Lähettäjä: Michaud Michael mailto:m.michael.mich...@orange.fr>> Lähetetty: tiistai 22. joulukuuta 2020 23.36 Vastaanottaja: OpenJump develop and use mailto:jump-pilot-devel@lists.sourceforge.net>> Aihe: Re: [JPP-Devel] Some Sextante tools don't like negative pixel values Hi Jukka, Did you mean tools of Raster menu working on Sextante raster ? Exceptio
Re: [JPP-Devel] Some Sextante tools don't like negative pixel values
Hi, Yes, the tools are in the Raster menu. It seems that this issue happens with Java 11 but not with Java 8 ( versions I have are OpenJDK 11 and Corretto 8) With Java 8 * Countours are OK (but user should know that contours must be created for the raw, not colorized image) * Histogram is OK * Create Polygons From Raster – AdbToolbox gives NPE java.lang.NullPointerException at org.openjump.core.rasterimage.algorithms.VectorizeAlgorithm.toPolygonsAdbToolBox(VectorizeAlgorithm.java:111) at org.openjump.core.ui.plugin.raster.VectorizeToPolygonsPlugIn.run(VectorizeToPolygonsPlugIn.java:170) at com.vividsolutions.jump.workbench.ui.task.TaskMonitorManager$TaskWrapper.run(TaskMonitorManager.java:151) Start with Java 11 prints also something that Java 8 does not into console window: ---Start OJ--- java.nio.file.NoSuchFileException: C:\ohjelmat\OJ\OpenJUMP-20201222-r6656-PLUS\conf at java.base/sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:85) at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:96) at java.base/sun.nio.fs.WindowsLinkSupport.getRealPath(WindowsLinkSupport.java:257) at java.base/sun.nio.fs.WindowsPath.toRealPath(WindowsPath.java:891) at java.base/sun.nio.fs.WindowsPath.toRealPath(WindowsPath.java:42) at com.vividsolutions.jump.workbench.plugin.PlugInClassLoader.toFileURL(PlugInClassLoader.java:140) at com.vividsolutions.jump.workbench.plugin.PlugInClassLoader.addClassPathToUCP(PlugInClassLoader.java:121) at com.vividsolutions.jump.workbench.plugin.PlugInClassLoader.(PlugInClassLoader.java:27) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) at java.base/java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1977) at java.base/java.lang.System.initPhase3(System.java:2069) And both Java 8 and Java 11 prints this warning about 30 times during the startup. It must have something to do with the new style option “Interior border (slow)”. [WARN] 10:50:51.916 Expected 'interior' attribute but found none. Tag = line; Attributes = [Attribute: enabled="true"], [Attribute: width="1"] -Jukka- Lähettäjä: Michaud Michael Lähetetty: tiistai 22. joulukuuta 2020 23.36 Vastaanottaja: OpenJump develop and use Aihe: Re: [JPP-Devel] Some Sextante tools don't like negative pixel values Hi Jukka, Did you mean tools of Raster menu working on Sextante raster ? Exception seems to come from VectorizeToContoursPlugIn. I tried to reproduce the error with your last image (values from -16 to 0), but it produced contours without error. Michaël envoyé : 22 décembre 2020 à 16:22 de : "Rahkonen Jukka (MML)" mailto:jukka.rahko...@maanmittauslaitos.fi>> à : "jump-pilot-devel@lists.sourceforge.net<mailto:jump-pilot-devel@lists.sourceforge.net>" mailto:jump-pilot-devel@lists.sourceforge.net>> objet : [JPP-Devel] Some Sextante tools don't like negative pixel values Hi, I believe that the stack trace below means that the tool does not accept negative values. Tools which generate these errors are in the Sextante menu: * histogram * create polygons with the Adbtoolbox algorithm * create contours java.lang.NumberFormatException: For input string: "?16.257333755493" at java.base/jdk.internal.math.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2054) at java.base/jdk.internal.math.FloatingDecimal.parseDouble(FloatingDecimal.java:110) at java.base/java.lang.Double.parseDouble(Double.java:543) at java.base/java.lang.Double.valueOf(Double.java:506) at com.vividsolutions.jump.util.StringUtil.toString(StringUtil.java:397) at com.vividsolutions.jump.workbench.ui.AbstractMultiInputDialog.addDoubleField(AbstractMultiInputDialog.java:723) at com.vividsolutions.jump.workbench.ui.AbstractMultiInputDialog.addDoubleField(AbstractMultiInputDialog.java:705) at org.openjump.core.ui.plugin.raster.VectorizeToContoursPlugIn.setDialogValues(VectorizeToContoursPlugIn.java:154) at org.openjump.core.ui.plugin.raster.VectorizeToContoursPlugIn.execute(VectorizeToContoursPlugIn.java:109) at com.vividsolutions.jump.workbench.plugin.AbstractPlugIn$1.actionPerformed(
Re: [JPP-Devel] Some Sextante tools don't like negative pixel values
Hi Jukka,Did you mean tools of Raster menu working on Sextante raster ? Exception seems to come from VectorizeToContoursPlugIn.I tried to reproduce the error with your last image (values from -16 to 0), but it produced contours without error.Michaël envoyé : 22 décembre 2020 à 16:22de : "Rahkonen Jukka (MML)" à : "jump-pilot-devel@lists.sourceforge.net" objet : [JPP-Devel] Some Sextante tools don't like negative pixel valuesHi, I believe that the stack trace below means that the tool does not accept negative values. Tools which generate these errors are in the Sextante menu:histogramcreate polygons with the Adbtoolbox algorithmcreate contours java.lang.NumberFormatException: For input string: "?16.257333755493" at java.base/jdk.internal.math.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2054) at java.base/jdk.internal.math.FloatingDecimal.parseDouble(FloatingDecimal.java:110) at java.base/java.lang.Double.parseDouble(Double.java:543) at java.base/java.lang.Double.valueOf(Double.java:506) at com.vividsolutions.jump.util.StringUtil.toString(StringUtil.java:397) at com.vividsolutions.jump.workbench.ui.AbstractMultiInputDialog.addDoubleField(AbstractMultiInputDialog.java:723) at com.vividsolutions.jump.workbench.ui.AbstractMultiInputDialog.addDoubleField(AbstractMultiInputDialog.java:705) at org.openjump.core.ui.plugin.raster.VectorizeToContoursPlugIn.setDialogValues(VectorizeToContoursPlugIn.java:154) at org.openjump.core.ui.plugin.raster.VectorizeToContoursPlugIn.execute(VectorizeToContoursPlugIn.java:109) at com.vividsolutions.jump.workbench.plugin.AbstractPlugIn$1.actionPerformed(AbstractPlugIn.java:344) at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967) at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308) at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405) at java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262) at java.desktop/javax.swing.AbstractButton.doClick(AbstractButton.java:369) at java.desktop/javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1020) at java.desktop/javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1064) at java.desktop/java.awt.Component.processMouseEvent(Component.java:6632) at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342) at java.desktop/java.awt.Component.processEvent(Component.java:6397) at java.desktop/java.awt.Container.processEvent(Container.java:2263) at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5008) at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321) at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840) at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918) at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547) at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488) at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307) at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772) at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840) at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95) at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745) at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743) at java.base/java.security.AccessController.doPrivileged(Native Method) at
Re: [JPP-Devel] Some Sextante tools don't like negative pixel values
On 22.12.2020 16:22, Rahkonen Jukka (MML) wrote: > Hi, > > > > I believe that the stack trace below means that the tool does not accept > negative values. Tools which generate these errors are in the Sextante menu: that's ok. i don't like nor accept negative values either :)).. have fun holidays all, ede ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
[JPP-Devel] Some Sextante tools don't like negative pixel values
Hi, I believe that the stack trace below means that the tool does not accept negative values. Tools which generate these errors are in the Sextante menu: * histogram * create polygons with the Adbtoolbox algorithm * create contours java.lang.NumberFormatException: For input string: "?16.257333755493" at java.base/jdk.internal.math.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2054) at java.base/jdk.internal.math.FloatingDecimal.parseDouble(FloatingDecimal.java:110) at java.base/java.lang.Double.parseDouble(Double.java:543) at java.base/java.lang.Double.valueOf(Double.java:506) at com.vividsolutions.jump.util.StringUtil.toString(StringUtil.java:397) at com.vividsolutions.jump.workbench.ui.AbstractMultiInputDialog.addDoubleField(AbstractMultiInputDialog.java:723) at com.vividsolutions.jump.workbench.ui.AbstractMultiInputDialog.addDoubleField(AbstractMultiInputDialog.java:705) at org.openjump.core.ui.plugin.raster.VectorizeToContoursPlugIn.setDialogValues(VectorizeToContoursPlugIn.java:154) at org.openjump.core.ui.plugin.raster.VectorizeToContoursPlugIn.execute(VectorizeToContoursPlugIn.java:109) at com.vividsolutions.jump.workbench.plugin.AbstractPlugIn$1.actionPerformed(AbstractPlugIn.java:344) at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967) at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308) at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405) at java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262) at java.desktop/javax.swing.AbstractButton.doClick(AbstractButton.java:369) at java.desktop/javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1020) at java.desktop/javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1064) at java.desktop/java.awt.Component.processMouseEvent(Component.java:6632) at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342) at java.desktop/java.awt.Component.processEvent(Component.java:6397) at java.desktop/java.awt.Container.processEvent(Container.java:2263) at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5008) at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321) at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840) at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918) at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547) at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488) at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307) at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772) at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840) at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95) at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745) at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742) at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
