[Gvsig_english] gvSIG and geoprocessing: problem with union

[Lucía Martínez]

Hello Wolfgang,
developers should see the problem, they would need more information 
about the error.
Follow steps until the error, close gvsig. gvsig.log file will be 
cappear with the error (c:\Documents and settings\[user]\gvSIG for Windows).

Could you send it to the list?

Thank you
Lucía

-- 
Lucía Martínez Palomero
Proyecto gvSIG
Consellería de Infraestructuras y Transportes (GVA)
Valencia (Spain)



El 20/04/11 14:57, Wolfgang Qual escribió:
> Dear list,
>
> I used the union-geoprocess, but several times, the process stopped.
> Error message was:
>
> null java.lang.NullPointerException: null
>      com.iver.cit.gvsig.fmap.drivers.shp.SHP.findEnd(SHP.java:212)
>      com.iver.cit.gvsig.fmap.drivers.shp.SHP.getShxFile(SHP.java:208)
>      com.iver.cit.gvsig.fmap.drivers.shp.IndexedShpDriver.open(IndexedShpDriver.java:171)
>      com.iver.cit.gvsig.fmap.layers.VectorialFileAdapter.start(VectorialFileAdapter.java:106)
>      com.iver.cit.gvsig.fmap.layers.FLyrVect.getFullExtent(FLyrVect.java:309)
>      com.iver.cit.gvsig.fmap.operations.strategies.DefaultStrategy.isSpatialIndexNecessary(DefaultStrategy.java:445)
>      com.iver.cit.gvsig.fmap.operations.strategies.ShpStrategy.process(ShpStrategy.java:690)
>      com.iver.cit.gvsig.fmap.operations.strategies.ShpStrategy.process(ShpStrategy.java:670)
>      com.iver.cit.gvsig.geoprocess.impl.intersection.fmap.IntersectVisitor.visit(IntersectVisitor.java:211)
>      com.iver.cit.gvsig.fmap.operations.strategies.DefaultStrategy.process(DefaultStrategy.java:398)
>      com.iver.cit.gvsig.geoprocess.impl.union.fmap.UnionGeoprocess$UnionMonitorableTask.run(UnionGeoprocess.java:378)
>      com.iver.utiles.swing.threads.MonitorableDecoratorMainFirst.run(MonitorableDecoratorMainFirst.java:155)
>      com.iver.andami.PluginServices$1.construct(PluginServices.java:405)
>      com.iver.utiles.swing.threads.SwingWorker$2.run(SwingWorker.java:108)
>      java.lang.Thread.run(Unknown Source)
>
> It seems that this problem is connected to the spatial index
> (calculation works, if no spatial index is used). Any ideas what went wrong?
> Colleagues of me told me that they found other problems when a spatial
> index for a shapefile was available (some elements were not displayed
> etc...)
> Are there other known / similar problems with spatial indexes in gvSIG?
> Ideas to solve this?
>
> Best,
> Wolfgang
>