Hi community,
I think I've solved the problem with setting up oracle spatial data for use with Geoserver. The reason why Geoserver wasn't able to generate bbox values for my polygon featuretypes was that geoserver could not interpret/handle the EType "1005" in the SDO_ELEMENT_INFO Array. The SDO_ELEMENT_INFO array my data in the oracle spatial database were in looks like this (1005 stands for 'Compund Polygons'):
SDO_ELEM_INFO(1,1005,1,1,2,1)
Because Geoserver couln't interpret ETypes of '1005' it brought back the error maessage:
The FeatureType 'RWG_TBS' has a NULL extent.
HINT: the dataset is empty or has no default geometry attribute.
Now I generated a new test table setting the SDO_ELEM_INFO to 'simple Polygons'(SDO_ELEM_INFO(1,1003,1)). When generating the bbox in the config/data/featuretype section of the Geoserver admin tool everything went fine and I can map the featuretype in the 'mapPreview.do'.
The problem is that the data I want to use in a WMS have the SDO_ELEM_INFO of 'compund polygons' (SDO_ELEM_INFO(1,1005,1,1,2,1)
) which means that they consist of arcs and line segments (in contrast to only line segments used with 'simple polygons'). Does anybody know whether the dveloper guys are working on a solution to this problem? Or is there still a solution to my problem existing and I don't know this?
Thank you all for your support, help, ideas and your time.
best regards
Daniel
--
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer