Hi there
How can I dealing complex FeatureTypes with GeoServer 1.5.x? Perhaps I use
the description "complex FeatureTypes" in a false context therefore I will
show my question in an example. I have a simple datastore (only for
demonstration reason, this is a dummy example) like this (pseudo code):
<code>
Table1 contains:
ID INTEGER (primary key)
Name TEXT
Position GEOMETRY
Table2 contains
ID INTEGER (foreign key, reference to Table1.ID)
Note TEXT
</code>
Now I will receive with a WMS GetFeatureInfo request the ID, Name, Position
and each available Note. If there already a solution?
Thank you.
Regards, Thomas
--
View this message in context: http://www.nabble.com/Complex-FeatureTypes-datastore--tf3402012.html#a9473960
Sent from the GeoServer - User mailing list archive at Nabble.com.
Thomas Zuberbühler ha scritto:
Hi there
How can I dealing complex FeatureTypes with GeoServer 1.5.x? Perhaps I use
the description "complex FeatureTypes" in a false context therefore I will
show my question in an example. I have a simple datastore (only for
demonstration reason, this is a dummy example) like this (pseudo code):
<code>
Table1 contains:
ID INTEGER (primary key)
Name TEXT
Position GEOMETRY
Table2 contains
ID INTEGER (foreign key, reference to Table1.ID)
Note TEXT
</code>
Now I will receive with a WMS GetFeatureInfo request the ID, Name, Position
and each available Note. If there already a solution?
Not in 1.5.x. There is one group of developers trying to attack
the problem in Geoserver trunk (with a separate set of modules)
but it's definitely not going to be shipped with Geoserver 1.6.x neither.
The changes needed to support complex features are very extensive,
we'll need to rewrite big parts of both geotools and geoserver
to support them in a general way.
I think developers working against complex features will
get out a demo sometimes this or next week, but it will be just
a technology preview afaik.
Gabriel may be able to provide more details.
Cheers
Andrea
Andrea, many thanks to you for your response.
Regards, Thomas
aaime wrote:
Thomas Zuberbühler ha scritto:
Hi there
How can I dealing complex FeatureTypes with GeoServer 1.5.x? Perhaps I
use
the description "complex FeatureTypes" in a false context therefore I
will
show my question in an example. I have a simple datastore (only for
demonstration reason, this is a dummy example) like this (pseudo code):
<code>
Table1 contains:
ID INTEGER (primary key)
Name TEXT
Position GEOMETRY
Table2 contains
ID INTEGER (foreign key, reference to Table1.ID)
Note TEXT
</code>
Now I will receive with a WMS GetFeatureInfo request the ID, Name,
Position
and each available Note. If there already a solution?
Not in 1.5.x. There is one group of developers trying to attack
the problem in Geoserver trunk (with a separate set of modules)
but it's definitely not going to be shipped with Geoserver 1.6.x neither.
The changes needed to support complex features are very extensive,
we'll need to rewrite big parts of both geotools and geoserver
to support them in a general way.
I think developers working against complex features will
get out a demo sometimes this or next week, but it will be just
a technology preview afaik.
Gabriel may be able to provide more details.
Cheers
Andrea
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
View this message in context: http://www.nabble.com/Complex-FeatureTypes-datastore--tf3402012.html#a9494428
Sent from the GeoServer - User mailing list archive at Nabble.com.