+1.
The XSLT module ticks all the quality boxes, including substantial
documentation. I can think of a bunch of interesting uses cases,
including fake complex features (unless we have reverse XSLT like
deegree 2 or apache cocoon to support filters!) or an output format to
simplify/translate a
On Mon, Apr 8, 2013 at 10:54 PM, Phil Scadden wrote:
>
> > Simple, you don't.
>
> Okay, I will put a particular use-case to you then. Suppose you have an
> database file with rather ugly set of attributes. (ie highly normalised
> or coded attributes). In an ideal world you would construct a view
> Simple, you don't.
Okay, I will put a particular use-case to you then. Suppose you have an
database file with rather ugly set of attributes. (ie highly normalised
or coded attributes). In an ideal world you would construct a view that
delivers human-readable form and serve that from geoserv
+1.
On Mon, Apr 8, 2013 at 1:07 AM, Andrea Aime wrote:
> On Sun, Apr 7, 2013 at 11:33 PM, Phil Scadden wrote:
>
>> Hi. I looked at the documentation page. What is not clear to me is how
>> you request a particular transform when making a getfeature request.
>>
>
> Simple, you don't.
> The XSLT mo
On Sun, Apr 7, 2013 at 11:33 PM, Phil Scadden wrote:
> Hi. I looked at the documentation page. What is not clear to me is how
> you request a particular transform when making a getfeature request.
>
Simple, you don't.
The XSLT module is an output format generator just like the OGR output
format,
Hi. I looked at the documentation page. What is not clear to me is how
you request a particular transform when making a getfeature request.
Otherwise +1
--
Phil Scadden, Senior Scientist GNS Science Ltd 764 Cumberland St,
Private Bag 1930, Dunedin, New Zealand Ph +64 3 4799663, fax +64 3 477 5
