[Geoserver-users] MySQL WMS GetFeatureInfo in GeoServer 1.5.2

Hello.

I have GeoServer 1.5.2 installed with data from shapefiles and data from a
MySQL spatial database. I use this to load data into MapInfo, GoogleMaps and
GoogleEarth. All of which work fine.

However in MapInfo if I load a WMS layer I can query out the attribute data
with GetFeatureInfo. In GoogleEarth I can do this for shapefiles but not for
MySQL tables. All the boundaries appear to have no attribute data.

Does anyone know if this is a known bug or where I can look to fix it?

Thanks. Dan
--
View this message in context: http://www.nabble.com/MySQL-WMS-GetFeatureInfo-in-GeoServer-1.5.2-tf4804909.html#a13746321
Sent from the GeoServer - User mailing list archive at Nabble.com.

lunarfish ha scritto:

Hello.

I have GeoServer 1.5.2 installed with data from shapefiles and data from a
MySQL spatial database. I use this to load data into MapInfo, GoogleMaps and
GoogleEarth. All of which work fine.

However in MapInfo if I load a WMS layer I can query out the attribute data
with GetFeatureInfo. In GoogleEarth I can do this for shapefiles but not for
MySQL tables. All the boundaries appear to have no attribute data.

Does anyone know if this is a known bug or where I can look to fix it?

I don't know exactly... just tried with some sample data I have and
GetFeatureInfo works against my MySql install. Maybe it's something specific with the shapefile you're using. Can you provide it to us
(send by private mail, attach to a jira issue).

I'd suggest you try out the latest GeoServer nightly from
here:
http://traffic.openplans.org/geoserver/trunk/
GeoServer 1.5.4 is the last release from the 1.5.x series, we
won't make another one, so if a bug is to be fixed, it'll be
fixed in a 1.6.x release.

Cheers
Andrea

Hi Andrea - Thanks for your response

aaime wrote:

".. GetFeatureInfo works against my MySql install. Maybe it's something
specific with the shapefile you're using. Can you provide it to us (send
by private mail, attach to a jira issue)."

The shapefile works fine it's only the MySQL data which is not working. I'd
like to try to track this down before I try upgrading to 1.5.4? I don't
think that this coincided with my upgrade to 1.5.2 so I think it may be
something which has become corrupted on our server. I have replaced the core
MySQL and MySQL extension jar and restarted tomcat to ensure that these are
being used. Are there any other specific jar files I could try replacing
before I try migrating to 1.5.4?

Thanks. Dan
--
View this message in context: http://www.nabble.com/MySQL-WMS-GetFeatureInfo-in-GeoServer-1.5.2-tf4804909.html#a13768597
Sent from the GeoServer - User mailing list archive at Nabble.com.

lunarfish ha scritto:

Hi Andrea - Thanks for your response

aaime wrote:

".. GetFeatureInfo works against my MySql install. Maybe it's something
specific with the shapefile you're using. Can you provide it to us (send
by private mail, attach to a jira issue)."

The shapefile works fine it's only the MySQL data which is not working. I'd
like to try to track this down before I try upgrading to 1.5.4? I don't
think that this coincided with my upgrade to 1.5.2 so I think it may be
something which has become corrupted on our server. I have replaced the core
MySQL and MySQL extension jar and restarted tomcat to ensure that these are
being used. Are there any other specific jar files I could try replacing
before I try migrating to 1.5.4?

None, but the mysql datastore is not in a mantained state so I doubt
using 1.5.4 would make any difference. I'm asking for the shapefile
because I think that once imported in mysql it triggers some bug (some
data type that the mysql datastore does not handle properly, stuff
like that).

Cheers
Andrea