[Gvsig_english] gvSIG 1.9 (1243) some issues regarding the latest version::link with joined table
Wolfgang Qual
Wolfgang.Qual at muenchen.de
Thu Aug 20 13:10:39 CEST 2009
Hi Roser,
I tested again, whether it is possible to use a joined table as a source
for an event theme. I could specify the x- and y-column, but the event
theme was not generated. The following error is written into the
logfile (see below). Hope that helps to find the bug.
Best,
Wolfgang
From the logfile:
java.lang.ArrayIndexOutOfBoundsException: 33
at
com.iver.cit.gvsig.fmap.layers.SelectableDataSource.getFieldValue(SelectableDataSource.java:253)
at
com.iver.gvsig.addeventtheme.AddEventThemeDriver.getY(AddEventThemeDriver.java:133)
at
com.iver.gvsig.addeventtheme.AddEventThemeDriver.getFullExtent(AddEventThemeDriver.java:145)
at
com.iver.cit.gvsig.fmap.layers.VectorialAdapter.getFullExtent(VectorialAdapter.java:137)
at
com.iver.cit.gvsig.fmap.drivers.featureiterators.SpatialQueryFeatureIterator$FastSpatialCheck.isBoundedShapesNecessary(SpatialQueryFeatureIterator.java:409)
at
com.iver.cit.gvsig.fmap.drivers.featureiterators.SpatialQueryFeatureIterator$FastSpatialCheck.<init>(SpatialQueryFeatureIterator.java:383)
at
com.iver.cit.gvsig.fmap.drivers.featureiterators.SpatialQueryFeatureIterator.<init>(SpatialQueryFeatureIterator.java:131)
at
com.iver.cit.gvsig.fmap.layers.VectorialAdapter.getFeatureIterator(VectorialAdapter.java:219)
at com.iver.cit.gvsig.fmap.layers.FLyrVect._draw(FLyrVect.java:368)
at com.iver.cit.gvsig.fmap.layers.FLyrVect.draw(FLyrVect.java:600)
at
com.iver.cit.gvsig.fmap.DefaultMapContextDrawer.draw(DefaultMapContextDrawer.java:209)
at
com.iver.cit.gvsig.fmap.DefaultMapContextDrawer.draw(DefaultMapContextDrawer.java:175)
at com.iver.cit.gvsig.fmap.MapContext.draw(MapContext.java:1088)
at
com.iver.cit.gvsig.fmap.MapControl$PaintingRequest.paint(MapControl.java:1043)
at
com.iver.cit.gvsig.fmap.MapControl$Drawer2$Worker.run(MapControl.java:1234)
at java.lang.Thread.run(Unknown Source)
WARN AWT-EventQueue-1 com.iver.andami.PluginServices - Plugin
com.iver.core -- Konnte Übersetzung nicht finden für: Informations-Konsole
WARN AWT-EventQueue-1 com.iver.andami.PluginServices - Plugin
com.iver.core -- Konnte Übersetzung nicht finden für: Aktiviert das
Fenster
DEBUG AWT-EventQueue-1 com.iver.core.mdiManager.NewSkin - Activando
Informations-Konsole
DEBUG AWT-EventQueue-1 com.iver.andami.ui.mdiFrame.MDIFrame - Memory
usage 112139 KB
DEBUG Thread-8287 com.iver.andami.messages.NotificationManager - 33
java.lang.ArrayIndexOutOfBoundsException: 33
at
com.iver.cit.gvsig.fmap.layers.SelectableDataSource.getFieldValue(SelectableDataSource.java:253)
at
com.iver.gvsig.addeventtheme.AddEventThemeDriver.getY(AddEventThemeDriver.java:133)
at
com.iver.gvsig.addeventtheme.AddEventThemeDriver.getFullExtent(AddEventThemeDriver.java:145)
at
com.iver.cit.gvsig.fmap.layers.VectorialAdapter.getFullExtent(VectorialAdapter.java:137)
at
com.iver.cit.gvsig.fmap.drivers.featureiterators.SpatialQueryFeatureIterator$FastSpatialCheck.isBoundedShapesNecessary(SpatialQueryFeatureIterator.java:409)
at
com.iver.cit.gvsig.fmap.drivers.featureiterators.SpatialQueryFeatureIterator$FastSpatialCheck.<init>(SpatialQueryFeatureIterator.java:383)
at
com.iver.cit.gvsig.fmap.drivers.featureiterators.SpatialQueryFeatureIterator.<init>(SpatialQueryFeatureIterator.java:131)
at
com.iver.cit.gvsig.fmap.layers.VectorialAdapter.getFeatureIterator(VectorialAdapter.java:219)
at com.iver.cit.gvsig.fmap.layers.FLyrVect._draw(FLyrVect.java:368)
at com.iver.cit.gvsig.fmap.layers.FLyrVect.draw(FLyrVect.java:600)
at
com.iver.cit.gvsig.fmap.DefaultMapContextDrawer.draw(DefaultMapContextDrawer.java:209)
at
com.iver.cit.gvsig.fmap.DefaultMapContextDrawer.draw(DefaultMapContextDrawer.java:175)
at com.iver.cit.gvsig.fmap.MapContext.draw(MapContext.java:1088)
at
com.iver.cit.gvsig.fmap.MapControl$PaintingRequest.paint(MapControl.java:1043)
at
com.iver.cit.gvsig.fmap.MapControl$Drawer2$Worker.run(MapControl.java:1234)
at java.lang.Thread.run(Unknown Source)
DEBUG Thread-8287 com.iver.andami.messages.NotificationManager - 33
java.lang.ArrayIndexOutOfBoundsException: 33
at
com.iver.cit.gvsig.fmap.layers.SelectableDataSource.getFieldValue(SelectableDataSource.java:253)
at
com.iver.gvsig.addeventtheme.AddEventThemeDriver.getY(AddEventThemeDriver.java:133)
at
com.iver.gvsig.addeventtheme.AddEventThemeDriver.getFullExtent(AddEventThemeDriver.java:145)
at
com.iver.cit.gvsig.fmap.layers.VectorialAdapter.getFullExtent(VectorialAdapter.java:137)
at
com.iver.cit.gvsig.fmap.drivers.featureiterators.SpatialQueryFeatureIterator$FastSpatialCheck.isBoundedShapesNecessary(SpatialQueryFeatureIterator.java:409)
at
com.iver.cit.gvsig.fmap.drivers.featureiterators.SpatialQueryFeatureIterator$FastSpatialCheck.<init>(SpatialQueryFeatureIterator.java:383)
at
com.iver.cit.gvsig.fmap.drivers.featureiterators.SpatialQueryFeatureIterator.<init>(SpatialQueryFeatureIterator.java:131)
at
com.iver.cit.gvsig.fmap.layers.VectorialAdapter.getFeatureIterator(VectorialAdapter.java:219)
at com.iver.cit.gvsig.fmap.layers.FLyrVect._draw(FLyrVect.java:368)
at com.iver.cit.gvsig.fmap.layers.FLyrVect.draw(FLyrVect.java:600)
at
com.iver.cit.gvsig.fmap.DefaultMapContextDrawer.draw(DefaultMapContextDrawer.java:209)
at
com.iver.cit.gvsig.fmap.DefaultMapContextDrawer.draw(DefaultMapContextDrawer.java:175)
at com.iver.cit.gvsig.fmap.MapContext.draw(MapContext.java:1088)
at
com.iver.cit.gvsig.fmap.MapControl$PaintingRequest.paint(MapControl.java:1043)
at
com.iver.cit.gvsig.fmap.MapControl$Drawer2$Worker.run(MapControl.java:1234)
at java.lang.Thread.run(Unknown Source)
DEBUG AWT-EventQueue-1 com.iver.core.mdiManager.NewSkin - Activando
Informations-Konsole
roser schrieb:
> Hi Wolfgang, sorry for answering so late, I wasn't here yesterday
>
> I reported the bug to the developers including your log and screenshot,
> and another bug that I found when testing yours, I hope it gets fixed soon.
> And for the other bugs although I couldn't reproduce them, They've told
> me that they are going to have a look at them, so it's just a matter of
> time.
>
> Best regards
> roser
>
>
>
>
>
> Wolfgang Qual wrote:
>
>> Hi list,
>> I have to add that I was able to finalize the table work - _within gvSIG
>> 1.1.2_: using the manage fields dialogue in this version, I was able to
>> rename, delete fields without running into problems.
>> Truncation of field names did not appear. ;)
>> The Umlauts in my attribute table were displayed correctly, no problem.
>> Should I summarize the problems I ran into?
>>
>> Best regards. Comments are welcome - as always.
>> Wolfgang
>>
>> ---
>>
>> Wolfgang Qual schrieb:
>>
>>
>>> Hi list,
>>> again, I made a new test. I thought that empty cells may cause the
>>> problem with cropped/mixed cell content. Therefore, I deleted all
>>> columns that contain no values. Also colums were deleted
>>> which do contain only few empty cells. Then, I added some new fields
>>> and used the field calculator. Afterwards, I changed the name of some
>>> columns and closed the field manager.
>>> The table looked nice, but when my edits were saved (left the edit
>>> mode), all got mixed up again. Very frustrating. I could reproduce
>>> this behaviour more than 5 times. It seems as if using the field
>>> manager to delete some columns causes the problem. Screenshot enclosed
>>> (there are values like "llgemeinmedizin" and "rau", "err" which should
>>> be "Allgmeinmedizin", "Herr" and "Frau".
>>>
>>> Additionally, it seems to be very important to define the correct font
>>> encoding, _before_ one starts an editing session. Otherwise, the table
>>> will be not usable any more, as umlauts cannot be restored again...
>>>
>>> Best,
>>> Wolfgang
>>>
>>> ----
>>>
>>> Wolfgang Qual schrieb:
>>>
>>>
>>>> Hello Roser, list,
>>>> I just did some more table works (table has about 4400 records with
>>>> quite some string fields). I deleted some fields within the manage
>>>> fields dialogue,
>>>> saved the changes and: table is broken (gvSIG seems to have forgotten
>>>> the limits of all columns). Red lines mark former fields. Some fields
>>>> are truncated.
>>>> And another thing that I would like to mention:
>>>> integer values always get an ".0" when the table is opened for the
>>>> first time. i think I can resolve that in openoffice...
>>>> logfile and screenshot attached. (sigh)
>>>>
>>>> Best,
>>>> Wolfgang
>>>>
>>>>
>>>> roser schrieb:
>>>>
>>>>
>>>>> Hi Wolfgang, with the "bew" column I meant "new" column, sorry, and
>>>>> yes, I tried to export the shapefile with the joined table to a new
>>>>> shapefile and it worked fine.
>>>>>
>>>>> As I've said, I'm sorry not being of much help, perhaps the problem
>>>>> is the size of the shapes, I'll try to test all this with bigger
>>>>> shapes, and if you continue having problems, please send us the logs.
>>>>>
>>>>> Another little thing, about your second mail. Manuel is on holiday,
>>>>> so I'm sure that when he comes back he'll take into account your
>>>>> suggestions and answer your mail.
>>>>>
>>>>> regards
>>>>> roser
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Wolfgang Qual wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Hello Roser,
>>>>>> ok. I will describe my problems more detailed later.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Hi Wolfgang
>>>>>>> I've been testing the problems you repoted and everythig worked
>>>>>>> fine on my computer:
>>>>>>> I've been able to make a join with a bew column added to the table,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> What is the bew column? Did you try to export the shapefile with
>>>>>> the joined table to a new shapefile?
>>>>>>
>>>>>>
>>>>>>
>>>>>>> I've used the joined table to create an event theme
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> ok! I will test it again. It really did not work in my case. Will
>>>>>> send the logfile if the error happens again.
>>>>>>
>>>>>>
>>>>>>
>>>>>>> I've exported a table to dbf without problems
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> ok. Will send a screenshot or something else later.
>>>>>>
>>>>>>
>>>>>>
>>>>>>> I can select more than one item on my linked table that are
>>>>>>> reflected on the other table...
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> My table contains more than 4500 items. Maybe your table was
>>>>>> smaller...
>>>>>>
>>>>>>
>>>>>>
>>>>>>> The only thing that gave me problems is the encoding when
>>>>>>> exporting to shapefile the event theme, so I'm reporting this to
>>>>>>> the developers.
>>>>>>> I don't know exactly where is the problem with the other things, I
>>>>>>> mean, I don't know why it works on my computer and not on yours,
>>>>>>> I'm already using bn1244, perhaps it's that.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> It would be good, if a developer could write one sentence about
>>>>>> this. Could it be that all these issues have been sorted out in the
>>>>>> brand new 1244?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Sorry I'm not of much help
>>>>>>> Thank you for your reports
>>>>>>> best regards
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> I have to thank you!
>>>>>> Best,
>>>>>> Wolfgang
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> Gvsig_internacional mailing list
>>>>> Gvsig_internacional at listserv.gva.es
>>>>> http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> Gvsig_internacional mailing list
>>>> Gvsig_internacional at listserv.gva.es
>>>> http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
>>>>
>>>>
>>> ------------------------------------------------------------------------
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Gvsig_internacional mailing list
>>> Gvsig_internacional at listserv.gva.es
>>> http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
>>>
>>>
>>>
>>
>>
>
> _______________________________________________
> Gvsig_internacional mailing list
> Gvsig_internacional at listserv.gva.es
> http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
>
>
--
*Wolfgang Qual
* *Referat für Gesundheit und Umwelt*
Umweltschutz
Umweltvorsorge
RGU-UW 11
Bayerstraße 28a
80335 München
Telefon +49 - 89 - 233 - 4 77 17
Telefax +49 - 89 - 233 - 4 77 05
http://www.muenchen.de/umweltatlas
uw11.rgu at muenchen.de
Bitte beachten Sie die Hinweise zur elektronischen
Kommunikation mit der Landeshauptstadt München:
http://www.muenchen.de/ekomm
More information about the Gvsig_internacional
mailing list