Hi,
I've created a new entity "SITE" on a new namespace "SUEZ".
When I go to the preview "http://localhost:8080/geoserver1.5/mapPreview.do"
for suez:SITE, the map is correctly displayed.
But when I click on an object I've got the following message:
83997 [PLUS FIN] org.vfny.geoserver.wms.responses.GetFeatureInfoResponse -
asking delegate for write to
org.vfny.geoserver.util.PartialBufferedOutputStream2@anonymised.com
84004 [FIN] org.vfny.geoserver.global.Data - getting type SITE
java.util.NoSuchElementException: Could not locate FeatureTypeConfig 'SITE'
at org.vfny.geoserver.global.Data.getFeatureTypeInfo(Data.java:1204)
Please the attached file.
I don't understand the pb because when I turned the log to FINEST level, I
see that the last call on org.vfny.geoserver.global.Data is done without the
namespace:
83940 [FIN] org.vfny.geoserver.servlets.AbstractService - reading request:
HEIGHT=550&SRS=EPSG%3A4326&WIDTH=390&STYLES=&LAYERS=suez%3ASITE&FORMAT=image%2Fpng&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&EXCEPTIONS=application%2Fvnd.ogc.se_xml&BBOX=-23.32451%2C-5.749462%2C29.71891%2C69.055362&X=172&Y=507&INFO_FORMAT=text%2Fhtml&QUERY_LAYERS=suez%3ASITE&FEATURE_COUNT=50&srs=EPSG%3A4326&styles=&layers=suez%3ASITE
...
83948 [FIN] org.vfny.geoserver.global.Data - getting type suez:SITE
...
83949 [FIN] org.vfny.geoserver.global.Data - getting type suez:SITE
...
84004 [FIN] org.vfny.geoserver.global.Data - getting type SITE
java.util.NoSuchElementException: Could not locate FeatureTypeConfig 'SITE'
I attached the log file.
Thanks for help.
Mikael. http://www.nabble.com/file/p12353407/WMS_GetFeatureInfo.log
WMS_GetFeatureInfo.log
--
View this message in context: http://www.nabble.com/WMS_GetFeatureInfo%3A-Could-not-locate-FeatureTypeConfig-tf4336982.html#a12353407
Sent from the GeoServer - User mailing list archive at Nabble.com.
Hi Mikael,
It appears to be dying when trying too lok up the directory for the type
in the data directory. Can you look into your
<geoserver_data_directory>/featureTypes directory and tell us what the
name of the directory is? I have a feeling there might be some wierd
case sensitive thing going.
Also it would be helpful to know the version of GeoServer you are running.
-Justin
mhoudu69 wrote:
Hi,
I've created a new entity "SITE" on a new namespace "SUEZ".
When I go to the preview "http://localhost:8080/geoserver1.5/mapPreview.do"
for suez:SITE, the map is correctly displayed.
But when I click on an object I've got the following message:
83997 [PLUS FIN] org.vfny.geoserver.wms.responses.GetFeatureInfoResponse -
asking delegate for write to
org.vfny.geoserver.util.PartialBufferedOutputStream2@anonymised.com
84004 [FIN] org.vfny.geoserver.global.Data - getting type SITE
java.util.NoSuchElementException: Could not locate FeatureTypeConfig 'SITE'
at org.vfny.geoserver.global.Data.getFeatureTypeInfo(Data.java:1204)
Please the attached file.
I don't understand the pb because when I turned the log to FINEST level, I
see that the last call on org.vfny.geoserver.global.Data is done without the
namespace:
83940 [FIN] org.vfny.geoserver.servlets.AbstractService - reading request:
HEIGHT=550&SRS=EPSG%3A4326&WIDTH=390&STYLES=&LAYERS=suez%3ASITE&FORMAT=image%2Fpng&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&EXCEPTIONS=application%2Fvnd.ogc.se_xml&BBOX=-23.32451%2C-5.749462%2C29.71891%2C69.055362&X=172&Y=507&INFO_FORMAT=text%2Fhtml&QUERY_LAYERS=suez%3ASITE&FEATURE_COUNT=50&srs=EPSG%3A4326&styles=&layers=suez%3ASITE
...
83948 [FIN] org.vfny.geoserver.global.Data - getting type suez:SITE
...
83949 [FIN] org.vfny.geoserver.global.Data - getting type suez:SITE
...
84004 [FIN] org.vfny.geoserver.global.Data - getting type SITE
java.util.NoSuchElementException: Could not locate FeatureTypeConfig 'SITE'
I attached the log file.
Thanks for help.
Mikael. http://www.nabble.com/file/p12353407/WMS_GetFeatureInfo.log
WMS_GetFeatureInfo.log
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Thanks for help Justin.
I'm working with Geoserver 1.5.3 and I've just fixed the problem by put into
WEB-INF/lib the additional jar for Oracle.
Now it works, but I'ge got a new pb on 1 layer when the geometry is
retrieved from the db.
13011474 [FIN] org.geotools.data.jdbc.JDBC1DataStore - About to execute
query: SELECT "OBJECTID", "SITECODE", "SITENAME", "HOTLINK", "TYPE",
"COUNTRY", "MAJ", "SHAPE" FROM "NATURA_2000"
13011474 [FIN] org.geotools.data.jdbc.ConnectionPool - Getting available
connection.
13012236 [FIN] org.geotools.data.oracle.attributeio.SDOAttributeIO - About
to create Geometry convertor for NATURA_2000.SHAPE
java.lang.IllegalArgumentException: Number of points must be 0 or >3
at
com.vividsolutions.jts.geom.LinearRing.validateConstruction(LinearRing.java:98)
at com.vividsolutions.jts.geom.LinearRing.<init>(LinearRing.java:90)
at
com.vividsolutions.jts.geom.GeometryFactory.createLinearRing(GeometryFactory.java:319)
at org.geotools.data.oracle.sdo.SDO.createLinearRing(SDO.java:2611)
at org.geotools.data.oracle.sdo.SDO.createPolygon(SDO.java:2528)
at org.geotools.data.oracle.sdo.SDO.createMultiPolygon(SDO.java:2827)
at org.geotools.data.oracle.sdo.SDO.create(SDO.java:2331)
at org.geotools.data.oracle.sdo.SDO.create(SDO.java:2289)
at
org.geotools.data.oracle.sdo.GeometryConverter.asGeometry(GeometryConverter.java:123)
So, I've create the same layer from the shapefile and it works perfectly.
I assume that there was a pb during the insertion in the db.
I'll have a look on it because I was not in charge of this part but
mdsys.sdo_geom.VALIDATE_GEOMETRY seems to failed on some elements.
Mikael.
--
View this message in context: http://www.nabble.com/WMS_GetFeatureInfo%3A-Could-not-locate-FeatureTypeConfig-tf4336982.html#a12366850
Sent from the GeoServer - User mailing list archive at Nabble.com.
Hi Mikael,
Cool, glad you solved your first problem. It could be a problem with the
data... it might also be a problem with oracle.. Let us know what you
find with the data.
-Justin
mhoudu69 wrote:
Thanks for help Justin.
I'm working with Geoserver 1.5.3 and I've just fixed the problem by put into
WEB-INF/lib the additional jar for Oracle.
Now it works, but I'ge got a new pb on 1 layer when the geometry is
retrieved from the db.
13011474 [FIN] org.geotools.data.jdbc.JDBC1DataStore - About to execute
query: SELECT "OBJECTID", "SITECODE", "SITENAME", "HOTLINK", "TYPE",
"COUNTRY", "MAJ", "SHAPE" FROM "NATURA_2000"
13011474 [FIN] org.geotools.data.jdbc.ConnectionPool - Getting available
connection.
13012236 [FIN] org.geotools.data.oracle.attributeio.SDOAttributeIO - About
to create Geometry convertor for NATURA_2000.SHAPE
java.lang.IllegalArgumentException: Number of points must be 0 or >3
at
com.vividsolutions.jts.geom.LinearRing.validateConstruction(LinearRing.java:98)
at com.vividsolutions.jts.geom.LinearRing.<init>(LinearRing.java:90)
at
com.vividsolutions.jts.geom.GeometryFactory.createLinearRing(GeometryFactory.java:319)
at org.geotools.data.oracle.sdo.SDO.createLinearRing(SDO.java:2611)
at org.geotools.data.oracle.sdo.SDO.createPolygon(SDO.java:2528)
at org.geotools.data.oracle.sdo.SDO.createMultiPolygon(SDO.java:2827)
at org.geotools.data.oracle.sdo.SDO.create(SDO.java:2331)
at org.geotools.data.oracle.sdo.SDO.create(SDO.java:2289)
at
org.geotools.data.oracle.sdo.GeometryConverter.asGeometry(GeometryConverter.java:123)
So, I've create the same layer from the shapefile and it works perfectly.
I assume that there was a pb during the insertion in the db.
I'll have a look on it because I was not in charge of this part but
mdsys.sdo_geom.VALIDATE_GEOMETRY seems to failed on some elements.
Mikael.
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Hi Justin,
Seems that there is around 50 elements which are not validate by Oracle via
sdo_geom.validate_geometry.
Most of them (45) give me the error code 13356 and few ones (3) the code
13349.
As most of the data in Oracle are validate, I don't think the pb comes from
the db. When I go to the preview where I can see clearly my layer on the
map; the pb occurs always when I click on the map to get feature info and
this whatever the element I click :S
Thus, I've got 2 other features which work perfectly but the geometries are
respectively points and polyline; and one of them also got some 13356 oracle
validating error code. (more an alert...)
The pb I see is on polygon.
According to me, the data are well got from Oracle but an exception occurs
during the creation of the response XML from the WMS servlet. It works with
the same data (a new entity created directly from the shapefile) but of
course it is not the same component which are used to transform data in XML.
So the pb is in
com.vividsolutions.jts.geom.LinearRing.validateConstruction(LinearRing.java:98)
???
Mikael.
--
View this message in context: http://www.nabble.com/WMS_GetFeatureInfo%3A-Could-not-locate-FeatureTypeConfig-tf4336982.html#a12370228
Sent from the GeoServer - User mailing list archive at Nabble.com.
mhoudu69 ha scritto:
Hi Justin,
Seems that there is around 50 elements which are not validate by Oracle via
sdo_geom.validate_geometry.
Most of them (45) give me the error code 13356 and few ones (3) the code
13349.
As most of the data in Oracle are validate, I don't think the pb comes from
the db. When I go to the preview where I can see clearly my layer on the
map; the pb occurs always when I click on the map to get feature info and
this whatever the element I click :S
Thus, I've got 2 other features which work perfectly but the geometries are
respectively points and polyline; and one of them also got some 13356 oracle
validating error code. (more an alert...)
The pb I see is on polygon.
According to me, the data are well got from Oracle but an exception occurs
during the creation of the response XML from the WMS servlet. It works with
the same data (a new entity created directly from the shapefile) but of
course it is not the same component which are used to transform data in XML.
So the pb is in
com.vividsolutions.jts.geom.LinearRing.validateConstruction(LinearRing.java:98)
Hmm... I don't see why this happens only in getFeatureInfo... the geometry reading code is the same, and that error usually happens if the linear rings aren't closed, that is, if the last and first coordinate of the linear ring aren't the same. Maybe this is valid for Oracle, but not
for JTS... can you provide us with a Oracle dump made with the "ext" command (by private mail on my address).
Cheers
Andrea