[Mapbuilder-devel] Re: Scaling up WFS queries

[Cameron S. <cam...@gm...>]

Pat,
I've been pretty sick since Sunday and have not been thinking clearly. 
You will get a better response if you ask again when I feel better.

As Mike suggests, model templates solve some of these issues, but they 
also introduced some other issues that we have not resolved.  Off the 
top of my head, I can't remember what they were.

Another solution that might work for you is to merge results of multiple 
WFS queries into one FeatureCollection response.

Adair, Mike wrote:
> Pat,
> 
> That's the problem that model templates is supposed to solve.  The idea is
> it's a template used to create new Model object instances, each with their
> own widget instances, instead of continually replacing the same objects.
> 
> That mostly works now, the main issue remaining is to implement maintaining
> the list and clearing of the template models robustly, and UI issues like
> when should the set of models be deleted?
> 
> Is this what you had in mind?
> 
> Mike
> 
> 
>>-----Original Message-----
>>From: Pat Cappelaere [mailto:pa...@ca...] 
>>Sent: Wednesday, May 24, 2006 9:28 PM
>>To: Adair, Mike; Cameron Shorter
>>Cc: 'map...@li...'
>>Subject: Scaling up WFS queries
>>
>>Mike, Cameron,
>>
>>I have made some good progress with the WebServiceForm, 
>>FeatureCollection,
>>GMLrendererVG and WfsQueryLayer.
>>I can read a FeatureType from an OWSContext document and 
>>render it in Vector
>>Graphics on the map.  I can also generate a custom query and 
>>insert it into
>>a Context document.
>>The shortcoming I see is as follows: A FeatureCollection 
>>seems to be limited
>>to one WFS query.  What about if we have more than one query 
>>in a document
>>that is being sent over to us by mail for instance?
>>Should a FeatureCollection be capable of handling many WFS 
>>query responses?
>>How would this scale up?
>>Thanks,
>>Pat.
>>
>>
> 
> 


-- 
Cameron Shorter
http://cameron.shorter.net