Hi,
I was wondering, shall we add some template driven output to GetFeature
too? There was a plan to uniform GetFeatureInfo and GetFeature code, that would allow to get readable output from GetFeature too.
I was also thinking, that it would be a nice thing to have a readable
output out of DescribeFeatureType, in form of an HTML table, and then
associate it to the preview as a further way to explore data.
I mean, I know one can go to the administration panel, but a user
of Geoserver cannot do that...
Cheers
Andrea
Templates are fine for new formats, but shouldnt distract us from the need to actually model the feature types properly.
We want this partly to deliver proper GML (the normative form), though this can be achieved with templates I guess.
the problem is, you can munge the output to conform to a standard, but if we want to support SLD, we must be able to handle filters and attribute specifications that reference the properties externally defined feature type.
I'm dying to hear back from Justin as to exactly what and how much progress he's making with improving the feature type model for geotools 2.5
Rob A
Andrea Aime wrote:
Hi,
I was wondering, shall we add some template driven output to GetFeature
too? There was a plan to uniform GetFeatureInfo and GetFeature code, that would allow to get readable output from GetFeature too.
I was also thinking, that it would be a nice thing to have a readable
output out of DescribeFeatureType, in form of an HTML table, and then
associate it to the preview as a further way to explore data.
I mean, I know one can go to the administration panel, but a user
of Geoserver cannot do that...
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Andrea Aime wrote:
Hi,
I was wondering, shall we add some template driven output to GetFeature
too? There was a plan to uniform GetFeatureInfo and GetFeature code, that would allow to get readable output from GetFeature too.
+1
I was also thinking, that it would be a nice thing to have a readable
output out of DescribeFeatureType, in form of an HTML table, and then
associate it to the preview as a further way to explore data.
I mean, I know one can go to the administration panel, but a user
of Geoserver cannot do that...
Yeah I could go for that... although I am not sure how much value it adds over the ability to point and click in the map preview to explore features.
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:4007,46b338c733845210051143!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Justin Deoliveira ha scritto:
I was also thinking, that it would be a nice thing to have a readable
output out of DescribeFeatureType, in form of an HTML table, and then
associate it to the preview as a further way to explore data.
I mean, I know one can go to the administration panel, but a user
of Geoserver cannot do that...
Yeah I could go for that... although I am not sure how much value it adds over the ability to point and click in the map preview to explore features.
Well, it would let you know what's the type of an attribute, if it's
nullable or not, and so on. Useful if you're writing and SLD (given
that we accept external SLD, you may not be the admin when doing so).
Cheers
Andrea
Rob Atkinson wrote:
Templates are fine for new formats, but shouldnt distract us from the need to actually model the feature types properly.
We want this partly to deliver proper GML (the normative form), though this can be achieved with templates I guess.
the problem is, you can munge the output to conform to a standard, but if we want to support SLD, we must be able to handle filters and attribute specifications that reference the properties externally defined feature type.
Not sure I follow you here Rob... it sounds to me that all Andrea wants is an easier way to view the schema of a dataset. Something far simpler then GML or xml schema.
I'm dying to hear back from Justin as to exactly what and how much progress he's making with improving the feature type model for geotools 2.5
Still working away... i have the new feature model implementation from the fm branch (the one gabriel is using) on trunk... and the old model is extending it. I still need to do more testing at this point (GeoServer cite tests) to ensure that everything stays backwards compatible.
Rob A
Andrea Aime wrote:
Hi,
I was wondering, shall we add some template driven output to GetFeature
too? There was a plan to uniform GetFeatureInfo and GetFeature code, that would allow to get readable output from GetFeature too.
I was also thinking, that it would be a nice thing to have a readable
output out of DescribeFeatureType, in form of an HTML table, and then
associate it to the preview as a further way to explore data.
I mean, I know one can go to the administration panel, but a user
of Geoserver cannot do that...
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:4007,46b339df36131336712104!
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
!DSPAM:4007,46b339df36131336712104!
------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:4007,46b339df36131336712104!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Justin Deoliveira wrote:
Rob Atkinson wrote:
Templates are fine for new formats, but shouldnt distract us from the need to actually model the feature types properly.
We want this partly to deliver proper GML (the normative form), though this can be achieved with templates I guess.
the problem is, you can munge the output to conform to a standard, but if we want to support SLD, we must be able to handle filters and attribute specifications that reference the properties externally defined feature type.
Not sure I follow you here Rob... it sounds to me that all Andrea wants is an easier way to view the schema of a dataset. Something far simpler then GML or xml schema.
that was the second part of the email, I read the first part as
I was wondering, shall we add some template driven output to GetFeature
too? There was a plan to uniform GetFeatureInfo and GetFeature code, that would allow to get readable output from GetFeature too.
I'm dying to hear back from Justin as to exactly what and how much progress he's making with improving the feature type model for geotools 2.5
Still working away... i have the new feature model implementation from the fm branch (the one gabriel is using) on trunk... and the old model is extending it. I still need to do more testing at this point (GeoServer cite tests) to ensure that everything stays backwards compatible.
Cool, I'm trying to get to a stage where i can rebuild the complex-ds store with what you have done, so I guess I still need some handle on what exactly is changed and how to access the new implementation.
Rob
+1
And if we move to a rest like alternative to wfs then the html table of describeFeatureType would be useful there as well.
C
Andrea Aime wrote:
Hi,
I was wondering, shall we add some template driven output to GetFeature
too? There was a plan to uniform GetFeatureInfo and GetFeature code, that would allow to get readable output from GetFeature too.
I was also thinking, that it would be a nice thing to have a readable
output out of DescribeFeatureType, in form of an HTML table, and then
associate it to the preview as a further way to explore data.
I mean, I know one can go to the administration panel, but a user
of Geoserver cannot do that...
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:4005,46b338c733831628642973!