On Tue, Jun 21, 2011 at 7:53 AM, Andrea Aime
<andrea.a...@geo-solutions.it>wrote:
> On Tue, Jun 21, 2011 at 3:33 PM, Justin Deoliveira
> <jdeol...@opengeo.org>wrote:
>
>> Hi guys,
>>
>> Yes, the ability to join on custom filters was done intentionally, mostly
>> to support spatial joins. If app-schema were to move to this api for joining
>> for the time being maybe it would be possible just to throw an exception.
>>
>> If you look at the join class it has a Type property which is an
>> enumeration, INNER, OUTER, etc... so allows you to specify the type of join
>> you wish to do.
>>
>> It is probably best to think about this specific proposal as "joining for
>> simple features" (I can see the look of disdain now). In the proposal
>> document I propose what the schema of "joined feature" should look like, but
>> don't mention any restriction about how actual features are returned which
>> was sort of intentional. In my case indeed i intent to return the same
>> feature multiple times, as would happen in an SQL query. I realize this is
>> not the app-schema / complex feature way but perhaps we can keep that an
>> implementation detail? Maybe we assume that any DataStore (DataStore here
>> meaning simple features) follows the SQL semantics, and anything not
>> implementing DataStore (DataAccess) will return complex features. Or perhaps
>> we declare the behaviour somewhere in QueryCapabilities. Not sure. Anywho,
>> if possible I would like to keep this proposal with just the api... and
>> again hopefully keep how the features are returned to be an implementation
>> detail.
>>
>
> Justin, as far as I understand repeating the same feature multiple times in
> the output is actually what the WFS joining requires, no?
> The output is made of tuple of features, it's not a new feature type (which
> would not have a schema in DescribeFeatureType)
> with multiple children and the like.
>
> Ha, right of course... a small detail i neglected to mention :)
> That said, app-schema could build on top of these results pretty much like
> as on top of a sql result, unless I'm missing something.
>
> Am I missing something?
>
> 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
>
> -------------------------------------------------------
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
