[Gvsig_english] Geoprocessing tool: Clip

Alvaro Zabala azabala at gmail.com
Wed Jan 9 10:27:10 CET 2008


The problems you've found possible must be dependent of the input data.

gvSIG 1.1's clip runs well with the greatest part of data input sets probed,
but in certain cases it could found problems,

If you can run it with gvSIG 1.1.1, probably this problem has been solved
yet.

Best regards!

2008/1/9, Fabio D'Ovidio <fabiodovidio at gmail.com>:
>
> Hi!
> I've check the log file and it returns as following (now, i'm trying to
> clip a polygonal vector layer from the file system. It's a SHP file):
>
> DEBUG AWT-EventQueue-1 com.iver.core.mdiManager.NewSkin$FrameListener -
> Riporta il focus aVista : Senza titolo - 0
> DEBUG AWT-EventQueue-1 com.iver.andami.ui.mdiFrame.MDIFrame - Memoria
> total: 48 MB
> DEBUG AWT-EventQueue-1 com.iver.andami.ui.mdiFrame.MDIFrame - Esegui
> comando:GEOPROCESSING_MANAGER
> DEBUG AWT-EventQueue-1 com.iver.core.mdiManager.NewSkin - Activando
> Gestore dei processi
> WARN AWT-EventQueue-1 com.iver.andami.PluginServices - Plugin
> com.iver.core -- Non si é incontrata la traduzione per Gestore dei
> processi
> WARN AWT-EventQueue-1 com.iver.andami.PluginServices - Plugin
> com.iver.core -- Non si é incontrata la traduzione per Gestore dei
> processi
> WARN AWT-EventQueue-1 com.iver.andami.PluginServices - Plugin
> com.iver.core -- Non si é incontrata la traduzione per Attiva la finestra
> DEBUG AWT-EventQueue-1 com.iver.andami.ui.mdiFrame.MDIFrame - Memoria
> total: 47 MB
> DEBUG AWT-EventQueue-1 com.iver.andami.ui.mdiFrame.MDIFrame - Memoria
> total: 47 MB
> INFO AWT-EventQueue-1 com.hardcode.gdbms.engine.data.AutomaticDataSource
> - timer start
> INFO AWT-EventQueue-1 com.hardcode.gdbms.engine.data.AutomaticDataSource
> - timer reset
> WARN AWT-EventQueue-1 com.iver.andami.PluginServices - Non si é
> incontrata la traduzione per PluginServices.Procesando
> INFO Thread-29 com.hardcode.gdbms.engine.data.AutomaticDataSource -
> timer start
> INFO Thread-29 com.hardcode.gdbms.engine.data.AutomaticDataSource -
> timer reset
> INFO Thread-29 com.hardcode.gdbms.engine.data.AutomaticDataSource -
> datasource closed
> INFO Thread-28 com.hardcode.gdbms.engine.data.AutomaticDataSource -
> datasource closed
>
> There are no errors. I'm working on Windows XP.
> So the problem is indipendent from the vector data type (linear,
> poligonal, ecc..)
>
>
> Sergio Clark ha scritto:
> > Hi Fabio,
> >
> > I've used Clip Geoprocessing, in gvSIG 1.1+1.1.1 patch, and it works
> > fine for me. I've tested it with Input cover=line shape and Clip
> > cover=polygon shape, like you. What is your error exactly? Could you
> > please send us the .log file?
> >
> > Thanks,
> >
> > Sergio.
> >
>
> --
> Ing. Fabio D'Ovidio
>
> iQuadro - Informatica e Innovazione s.r.l.
> Via C. Pisacane 23, Aversa (CE) - 81031
> Web : www.ii2.it
> Tel.: 081 197 57 600
> mail: fabiodovidio at gmail.com
>
> _______________________________________________
> Gvsig_internacional mailing list
> Gvsig_internacional at runas.cap.gva.es
> http://runas.cap.gva.es/mailman/listinfo/gvsig_internacional
>



-- 
Alvaro Zabala Ordóñez
Tlf: 657235082
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://runas.cap.gva.es/pipermail/gvsig_internacional/attachments/20080109/8e170942/attachment.htm


More information about the Gvsig_internacional mailing list