On Wed, Jan 11, 2012 at 1:57 PM, Rahkonen Jukka
<[email protected]>wrote:
> **
> Hi,
>
> Getting min and max should be possible by doing getFeature with
> &propertyname=attribute&maxFeatures=1&sortBy=attribute+A and then with
> &propertyname=attribute&maxFeatures=1&sortBy=attribute+D. However, I would
> guess this is not tested too much.
>
Right, did not think about it but it's true. Starting with GeoServer 2.1.3
it should work with any data store,
though it will be efficient only if you are using a database as the backend
(older versions will have it
working on databases only, period, other stores did not support sorting).
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
