Hi,
I'd like to replace the GetFeatureInfo html output with something
better looking, more useful.
What I don't like about the current format is the table borders,
and the fact that most of the time it expands off the page.
Scrolling horizontally is usually considered less friendly
than scrolling horizontally.
What I'd propose is to have it look more or less like the
text version, that is, an unumbered list, with bold attributes,
plain text values, and for geometries, a link to GetFeature
that extracts just that attribute of that specific feature
(so that, if you need to, you can get the bbox of the
geometry, and the geometry itself, and quickly).
Oh, it would also be nice to have the FID as the Feature title,
and have it a link to GetFeature too (just like in RSS output).
What do you think?
Cheers
Andrea
+1. So I guess applying the same template as for kml and georss is
somewhat of a lost cause. I guess the two are sufficiently different.
Should we break out a seperate template for GetFeatureInfo?
Andrea Aime wrote:
Hi,
I'd like to replace the GetFeatureInfo html output with something
better looking, more useful.
What I don't like about the current format is the table borders,
and the fact that most of the time it expands off the page.
Scrolling horizontally is usually considered less friendly
than scrolling horizontally.
What I'd propose is to have it look more or less like the
text version, that is, an unumbered list, with bold attributes,
plain text values, and for geometries, a link to GetFeature
that extracts just that attribute of that specific feature
(so that, if you need to, you can get the bbox of the
geometry, and the geometry itself, and quickly).
Oh, it would also be nice to have the FID as the Feature title,
and have it a link to GetFeature too (just like in RSS output).
What do you think?
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:4007,468135dd83275219720167!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Justin Deoliveira ha scritto:
+1. So I guess applying the same template as for kml and georss is
somewhat of a lost cause. I guess the two are sufficiently different.
Should we break out a seperate template for GetFeatureInfo?
I'd say yes. This also give people freedom of using different templates
for different protocols.
Cheers
Andrea