-users] gml:TimePeriod, app-schema and PostgreSQL
Hi Florence.
> Try this mapping :
> Extract from
> http://docs.geoserver.org/trunk/en/user/data/app-schema/mapping-file.html:
>
> targetAttributeNode is required wherever a property type contains an abstract
> element and
Hi Florence.
> Try this mapping :
> Extract from
> http://docs.geoserver.org/trunk/en/user/data/app-schema/mapping-file.html:
>
> targetAttributeNode is required wherever a property type contains an abstract
> element and app-schema cannot determine the type of the enclosed attribute.
> This m
[mailto:m.p...@m-click.de]
Sent: Thursday, 2 September 2010 5:58 PM
To: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] gml:TimePeriod, app-schema and PostgreSQL
Hello,
this is some additional information about the issue: The PostgreSQL
database contains a column
Hello,
this is some additional information about the issue: The PostgreSQL
database contains a column
validtime_beginposition TIMESTAMP NOT NULL
which is mapped via the app-schema plugin as follows:
gml:validTime
validtime_beginposition
Note that gml:validTime may be one of g
Hello all,
we're trying to provide gml:TimePeriod elements in a WFS reply.
The mapping rules for the app-schema plugin are quite clear, but
what column type is required in the PostgreSQL database?
There is no native "TimePeriod" type in PostgreSQL, so the
time range is currently stored in two TI
