gvSIG bugs #4626

gvSIG Intersection: Can't execute postProcess on output layers

Added by Antonio Falciano over 6 years ago. Updated over 6 years ago.

Status:Closed% Done:

0%

Priority:NormalSpent time:-
Assignee:Francisco Díaz Carsí
Category:Geoprocess
Target version:2.4.0-2836 (rev. org.gvsig.desktop-2.0.203)
Severity:Major Add-on version:
gvSIG version:2.4.0 Add-on build:
gvSIG build:2833 Add-on resolve version:
Operative System: Add-on resolve build:
Keywords: Proyecto:
Has patch: Hito:
Add-on name:Unknown

Description

The output layers of the gvSIG Intersection are always empty:

INFO 2476772 pool-9-thread-1 es.unex.sextante.core.SextanteLogHandler - Executing command: autoextent("true")
Executing command: runalg("gvSIG-intersection", "layer1", "layer2", "false", "false", "#", "#", "#")
Starting algorithm execution...:18-ago-2017 11.37.03
Finished algorithm execution:18-ago-2017 11.37.03
Execution time (millisecs):100

WARN 2476772 pool-9-thread-1 org.gvsig.geoprocess.lib.sextante.dataObjects.FlyrVectIVectorLayer - Can't execute postProcess on 'Intersezione (poligoni) '.
java.lang.NullPointerException
    at org.gvsig.fmap.dal.impl.DefaultDataManager.openStore(DefaultDataManager.java:387)
    at org.gvsig.geoprocess.lib.sextante.dataObjects.FlyrVectIVectorLayer.postProcess(FlyrVectIVectorLayer.java:498)
    at es.unex.sextante.core.GeoAlgorithm.postProcessOutputDataObjects(GeoAlgorithm.java:291)
    at es.unex.sextante.core.GeoAlgorithm.execute(GeoAlgorithm.java:241)
    at org.gvsig.geoprocess.lib.sextante.AbstractSextanteGeoProcess.execute(AbstractSextanteGeoProcess.java:84)
    at es.unex.sextante.core.GeoAlgorithm.execute(GeoAlgorithm.java:175)
    at es.unex.sextante.core.ProcessTask.call(ProcessTask.java:59)
    at es.unex.sextante.core.ProcessTask.call(ProcessTask.java:13)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
WARN 2476772 pool-9-thread-1 org.gvsig.geoprocess.lib.sextante.dataObjects.FlyrVectIVectorLayer - Can't execute postProcess on 'Intersezione (linee) '.
java.lang.NullPointerException
    at org.gvsig.fmap.dal.impl.DefaultDataManager.openStore(DefaultDataManager.java:387)
    at org.gvsig.geoprocess.lib.sextante.dataObjects.FlyrVectIVectorLayer.postProcess(FlyrVectIVectorLayer.java:498)
    at es.unex.sextante.core.GeoAlgorithm.postProcessOutputDataObjects(GeoAlgorithm.java:291)
    at es.unex.sextante.core.GeoAlgorithm.execute(GeoAlgorithm.java:241)
    at org.gvsig.geoprocess.lib.sextante.AbstractSextanteGeoProcess.execute(AbstractSextanteGeoProcess.java:84)
    at es.unex.sextante.core.GeoAlgorithm.execute(GeoAlgorithm.java:175)
    at es.unex.sextante.core.ProcessTask.call(ProcessTask.java:59)
    at es.unex.sextante.core.ProcessTask.call(ProcessTask.java:13)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
WARN 2476772 pool-9-thread-1 org.gvsig.geoprocess.lib.sextante.dataObjects.FlyrVectIVectorLayer - Can't execute postProcess on 'Intersezione (punti) '.
java.lang.NullPointerException
    at org.gvsig.fmap.dal.impl.DefaultDataManager.openStore(DefaultDataManager.java:387)
    at org.gvsig.geoprocess.lib.sextante.dataObjects.FlyrVectIVectorLayer.postProcess(FlyrVectIVectorLayer.java:498)
    at es.unex.sextante.core.GeoAlgorithm.postProcessOutputDataObjects(GeoAlgorithm.java:291)
    at es.unex.sextante.core.GeoAlgorithm.execute(GeoAlgorithm.java:241)
    at org.gvsig.geoprocess.lib.sextante.AbstractSextanteGeoProcess.execute(AbstractSextanteGeoProcess.java:84)
    at es.unex.sextante.core.GeoAlgorithm.execute(GeoAlgorithm.java:175)
    at es.unex.sextante.core.ProcessTask.call(ProcessTask.java:59)
    at es.unex.sextante.core.ProcessTask.call(ProcessTask.java:13)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

Related issues

Related to Application: gvSIG desktop - gvSIG bugs #4627: gvSIG Union: Can't execute postProcess on output layer Closed 08/18/2017

Associated revisions

Revision 988
Added by Joaquín del Cerro Murciano over 6 years ago

refs #4627, #4626. corregido el que se estubiese destruyendo un store cuando aun se iban ha hacer operaciones con el.

Revision 994
Added by Francisco Díaz Carsí over 6 years ago

refs #4626 #4627 Fixed union and intersection gvSIG geoprocesses

History

#1 Updated by Antonio Falciano over 6 years ago

Related to #4627.

#2 Updated by Antonio Falciano over 6 years ago

The same error happens also with gvSIG Union (#4627) and gvSIG Buffer:

Executing command: runalg("gvSIG-buffer", "layer1", "false", "5.0", "0", "false", "false", "0", "0", "#")
Starting algorithm execution...:21-ago-2017 19.27.23
Finished algorithm execution:21-ago-2017 19.27.23
Execution time (millisecs):78

WARN 135057 pool-3-thread-1 org.gvsig.geoprocess.lib.sextante.dataObjects.FlyrVectIVectorLayer - Can't execute postProcess on 'Buffer'.
java.lang.NullPointerException
    at org.gvsig.fmap.dal.impl.DefaultDataManager.openStore(DefaultDataManager.java:387)
    at org.gvsig.geoprocess.lib.sextante.dataObjects.FlyrVectIVectorLayer.postProcess(FlyrVectIVectorLayer.java:498)
    at es.unex.sextante.core.GeoAlgorithm.postProcessOutputDataObjects(GeoAlgorithm.java:291)
    at es.unex.sextante.core.GeoAlgorithm.execute(GeoAlgorithm.java:241)
    at org.gvsig.geoprocess.lib.sextante.AbstractSextanteGeoProcess.execute(AbstractSextanteGeoProcess.java:84)
    at es.unex.sextante.core.GeoAlgorithm.execute(GeoAlgorithm.java:175)
    at es.unex.sextante.core.ProcessTask.call(ProcessTask.java:59)
    at es.unex.sextante.core.ProcessTask.call(ProcessTask.java:13)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

#3 Updated by Joaquín del Cerro Murciano over 6 years ago

  • Related to gvSIG bugs #4627: gvSIG Union: Can't execute postProcess on output layer added

#4 Updated by Joaquín del Cerro Murciano over 6 years ago

  • Target version changed from 2.4.0-2850-final (rev. org.gvsig.desktop-2.0.220) to 2.4.0-2834 (rev. org.gvsig.desktop-2.0.201)
  • Assignee set to Joaquín del Cerro Murciano
  • Status changed from New to Fixed

#5 Updated by Álvaro Anguix over 6 years ago

  • Status changed from Fixed to New

Resultado erroneo

#6 Updated by Álvaro Anguix over 6 years ago

  • Target version changed from 2.4.0-2834 (rev. org.gvsig.desktop-2.0.201) to 2.4.0-2839-RC2 (rev. org.gvsig.desktop-2.0.206)

#7 Updated by Francisco Díaz Carsí over 6 years ago

  • Target version changed from 2.4.0-2839-RC2 (rev. org.gvsig.desktop-2.0.206) to 2.4.0-2835 (rev. org.gvsig.desktop-2.0.202)
  • Assignee changed from Joaquín del Cerro Murciano to Francisco Díaz Carsí
  • Status changed from New to Fixed

#8 Updated by Antonio Falciano over 6 years ago

  • Target version changed from 2.4.0-2835 (rev. org.gvsig.desktop-2.0.202) to 2.4.0-2850-final (rev. org.gvsig.desktop-2.0.220)
  • Status changed from Fixed to New

The issue still persists in build 2835.

#9 Updated by Antonio Falciano over 6 years ago

Antonio Falciano wrote:

The issue still persists in build 2835.

More in detail, the warning message is disappeared in the log, the three layers are created and loaded in the ToC but are empty. Analogous results for gvSIG Buffer.

#10 Updated by Antonio Falciano over 6 years ago

  • Target version changed from 2.4.0-2850-final (rev. org.gvsig.desktop-2.0.220) to 2.4.0-2839-RC2 (rev. org.gvsig.desktop-2.0.206)
  • Status changed from New to Fixed

Antonio Falciano wrote:

The issue still persists in build 2835.

...because the org.gvsig.geoprocess.app.mainplugin and org.gvsig.geoprocess.app.algorithm were not updated in build 2835.

#11 Updated by Joaquín del Cerro Murciano over 6 years ago

Antonio Falciano wrote:

Antonio Falciano wrote:

The issue still persists in build 2835.

...because the org.gvsig.geoprocess.app.mainplugin and org.gvsig.geoprocess.app.algorithm were not updated in build 2835.

OOhh!!!
Es verdad no he recompilado los geoprocesos.

#12 Updated by Joaquín del Cerro Murciano over 6 years ago

  • Target version changed from 2.4.0-2839-RC2 (rev. org.gvsig.desktop-2.0.206) to 2.4.0-2836 (rev. org.gvsig.desktop-2.0.203)

#13 Updated by Antonio Falciano over 6 years ago

  • Status changed from Fixed to Closed

Also available in: Atom PDF