Thanks for the clarification Niels, I was not aware that Prop was part of
the current API.
Still we have some duplication here right? Should we try running the
property collectors, look at the results, and generate the schema
appropriate to store the results?
--
Jody Garnett
On 21 April 2016 at
> > Hum... wfs-ng was supposed to be a drop-in replacement, not having a
>> upgrade
>> > path seems to be a serious issue to me.
>> > Where is it documented?
>>
>> Quick search got us this:
>> https://osgeo-org.atlassian.net/browse/GEOT-4883
>> and we googled some more messages on it.
>
> A backwar
On Thu, Apr 21, 2016 at 2:27 PM, Mark Prins wrote:
> On 19-04-16 20:29, Andrea Aime wrote:
> > Hi Mark,
> > comments inline
> >
> > We've had to revert the upgrading of gt-wfs -> gt-wfs-ng due to the
> > naming convention change, we cache/store the namespace:typename of
> > featuretyp
On 19-04-16 20:29, Andrea Aime wrote:
> Hi Mark,
> comments inline
>
> We've had to revert the upgrading of gt-wfs -> gt-wfs-ng due to the
> naming convention change, we cache/store the namespace:typename of
> featuretypes in our software and our things broke down all over the
> pla
On 17-04-16 04:17, Jody Garnett wrote:
> This proposal (and email thread) should be orthogonal to the RnD
> discussion on setting up a mosaic with multiple projections.
>
> This mosaic is focused on creating/managing the index used. One part I
> cannot wrap my head around is the workflow behind t
