Hi Andrea,
I just want to check something over with you quickly. And don't answer this email until you are back from vacation!! 
Recently you somewhat changed the semantics of the "featureid" parameter no? For instance to allow requests like:
layer=states&featureid=states.1,states.2
which is unlike other filters (ogc+cql) in which the relationship between filters and layers is one to one?
I have no problem with this... just want to make sure i have the semantics right. The reason i ask is that i need to get the kml reflector to support filters. The reflector works by taking a single request and splitting it up into multiple requests... one for each layer requested.
So for the ogc + cql filters the code needs to separate out the individual filters. But for featureid the code needs to replicate the entire value for each new requst. Does that make sense? Or am I just crazy?
-Justin
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Justin Deoliveira-4 wrote:
Hi Andrea,
I just want to check something over with you quickly. And don't answer
this email until you are back from vacation!!
Too late
Justin Deoliveira-4 wrote:
Recently you somewhat changed the semantics of the "featureid" parameter
no? For instance to allow requests like:
layer=states&featureid=states.1,states.2
which is unlike other filters (ogc+cql) in which the relationship
between filters and layers is one to one?
I have no problem with this... just want to make sure i have the
semantics right. The reason i ask is that i need to get the kml
reflector to support filters. The reflector works by taking a single
request and splitting it up into multiple requests... one for each layer
requested.
So for the ogc + cql filters the code needs to separate out the
individual filters. But for featureid the code needs to replicate the
entire value for each new requst. Does that make sense? Or am I just
crazy?
Yeah, build a single fid filter with all of the fids and the apply
it to each layer requested. If there are no layers, it's up to you
to guess the layer names....
Cheers
Andrea
--
View this message in context: http://www.nabble.com/featureid-semantics-tf4142930.html#a11818649
Sent from the GeoServer - Dev mailing list archive at Nabble.com.