That's excellent! Works a treat!

Many thanks,
David

2009/12/6 80n <[email protected]>

> On Sun, Dec 6, 2009 at 6:21 PM, David Calder <[email protected]>wrote:
>
>> Hi,
>> I was wondering if you could help me. I'm using Tagwatch to find and tidy
>> up the route_ref=* values where a pipe symbol or vbar (i.e. Unicode
>> character U+007C) has been used as a delimeter. See this page for example:
>> http://tagwatch.stoecker.eu/Great_britain/En/ignored_route_ref.html
>>
>> The query for a semicolon delimited value is (for example):
>> http://tagwatch.stoecker.eu/osmxapi/*[route_ref=171;172;178]<http://tagwatch.stoecker.eu/osmxapi/*%5Broute_ref=171;172;178%5D>
>> which works fine.
>>
>> However, the query for a pipe delimited value is (for example):
>> http://tagwatch.stoecker.eu/osmxapi/*[route_ref=46|46A]<http://tagwatch.stoecker.eu/osmxapi/*%5Broute_ref=46%7C46A%5D>
>> which returns the data for values that match 46 OR 46A but not "46|46A". I
>> know that this is the correct functionality as defined in the API spec but
>> how do I write the query so that it finds "46|46A". Do I need to escape the
>> character (and if so, how?) or do I need to encode it somehow (and if so,
>> how?)
>>
>
> I've just added escaping for this this and other characters.  To treat | as
> a literal value escape it as \| so your query would be:
>
>
> http://tagwatch.stoecker.eu/osmxapi/*[route_ref=46<http://tagwatch.stoecker.eu/osmxapi/*%5Broute_ref=46>
> \|46A]
>
> You can escape other characters [ ] = / etc in the same way.
>
> Spaces normally don't need to be escaped but this depends to some extent on
> the client you are using.  If you do need to escape space then it's URL
> encoding that you need, so use %20 in place of a space.
>
> 80n
>
>
>
>
>
>>
>> Many thanks,
>> David
>>
>>
>>
>> _______________________________________________
>> dev mailing list
>> [email protected]
>> http://lists.openstreetmap.org/listinfo/dev
>>
>>
>
_______________________________________________
dev mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/dev

Reply via email to