On Wed, Jul 27, 2011 at 12:08 PM, Rob Atkinson <robatkinson101@anonymised.com> wrote:
+1
sounds pretty cool.
It would be nice to allow a range and step size instead of just
discrete value list
maybe avalmin avalmax avalstep
or avalstep=start,end,stepsize
I also think you need an example of how CQL_filter would have an
avalue - i suspect it would need to be a parameter within a filter?
the avalue would be the full cql filter itself with the implementation
we have the time to make.
Both the templating idea and the stepping sound pretty cool, would
be great to implement them but we're pretty tight on time.
Anyways, if someone feels like to give them a crack it should not
be too hard, we'd just need to roll some sort of value generation
strategy that can be then fed with a list, a range and step, or a
template and a list of value to substitute into it, and have different
kvp for them, dunno, atemplate, atemplate_values, the latter could
be a list or a range, pretty much like the time/elevation support
that already has them
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
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
-------------------------------------------------------
