[OSM-dev] Multiple XAPI parameters...

[Jukka Rahkonen]

John Smith wrote:


> On 9 July 2010 13:56, Alan Mintz <Alan_Mintz+OSM at earthlink.net> wrote:
>> Are they ORd or ANDed? Is there a way to have a partial wildcard on the
>
> As far as I'm aware you can only do simply ORs, eg:
>
> [highway=residential|unclassified]
>
> And you can't do add more than one key value.


I had a fast try and Mapserver WMS and WFS services seem to support layers
with data selected with queries like:

DATA "way from (select (way),osm_id,tags from osm_point where (tags
@>'amenity=>pub') or (tags @>'amenity=>restaurant') and ((tags->'name')is 
null)) as foo using unique osm_id using srid=3067"

Thus however many keys/values are supported, as well as both AND and OR,
even in the same select. With a Mapserver variable substitution system
user can send the keys and values with the request.

I do not believe that standard WFS filters would work against hstote
column. Naturally WFS filters are supported for the normal attribute
fields created when the data is imported with osm2pgsql and for those
attributes then also wildcards can be used, as well as these spatial
operators:
<ogc:Equals/>
<ogc:Disjoint/>
<ogc:Touches/>
<ogc:Within/>
<ogc:Overlaps/>
<ogc:Crosses/>
<ogc:Intersect/>
<ogc:Contains/>
<ogc:DWithin/>
<ogc:BBOX/>

Caveat is that the output from WFS service is either GML2 or GML3 instead
of osm-xml and unusable for routing and updates.

-Jukka Rahkonen-