NOTICE: help.openstreetmap.org is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum

Normally the answer is "taginfo", but (as you'd expect) that does explicit processing of semicolons. If I search for http://taginfo.openstreetmap.org.uk/search?q=bar%3Bcafe%3Btoilets#values I get the one expected value back, but I'm not aware of a way of searching for any values (or keys for that matter) containing multiple semicolons.

In postgres (with a "normal" rendering database) I can do:

gis=# SELECT amenity FROM planet_osm_polygon WHERE (amenity LIKE '%;%;%');
                  amenity
-------------------------------------------
 bar;cafe;toilets
 private_hire_cars;coach_hire;minibus_hire
(2 rows)

but obviously that requires a local database and doesn't search for semicolons in keys - presumably there's a way to search the "tags" array in "planet_osm_ways"? Obviously for "planet_osm_polygon" I'd also need to look at "planet_osm_point" and "planet_osm_line", and for "planet_osm_ways" I'd need to look at "planet_osm_nodes" too (ignoring relations for now).

Maybe there's a way of doing it with Overpass?

EDIT: This was prompted by this taginfo discussion, as well as the related iD issue and someone "correcting" name_X tags in Ireland (the link to which I've lost).

asked 21 Jan '16, 14:32

SomeoneElse's gravatar image

SomeoneElse ♦
36.9k71370866
accept rate: 16%

edited 21 Jan '16, 14:38

1

This is probably the name_X correction you had in mind.

(21 Jan '16, 15:17) Vincent de P... ♦

If you have an osm2pgsql/hstore database and want to operate on the keys, you have to explode the hstore into regular rows with the each operator before then applying a normal query, like so:

gis=# SELECT osm_id, key
FROM
  (SELECT osm_id,(each(tags)).key as key FROM planet_osm_point) sub 
WHERE key like '%;%;%';
permanent link

answered 21 Jan '16, 15:25

Frederik%20Ramm's gravatar image

Frederik Ramm ♦
82.5k927201273
accept rate: 23%

No hstore here currently (and no "tags" column on planet_osm_point, though there is one on e.g. planet_osm_nodes) - will have to try it after reload.

(21 Jan '16, 19:13) SomeoneElse ♦

Overpass does indeed have regex search for keys: http://overpass-turbo.eu/s/dTS

way[~";"~"."];
out geom;

(~"." will match any value, some value match is required when matching a key)

In a similar way, you can also query for nodes or relations with at least one semicolon.

Edit: To check for values with at least 2 semicolons, the following regular expression might come in handy: ".+;(.+;)+.+" - use it either for keys or values.

[bbox:{{bbox}}];
way[~"."~".+;(.+;)+.+"];
out geom;

In any case it is recommended to also specify a suitable key like e.g. amenity, otherwise tags like opening_hours will produce quite a lot of hits.

permanent link

answered 21 Jan '16, 21:33

maxerickson's gravatar image

maxerickson
12.7k1083176
accept rate: 32%

edited 22 Jan '16, 08:50

mmd's gravatar image

mmd
5.7k15388

Taginfo doesn't have a way to do searches like that (mostly for performance reasons), but you can download the taginfo database and do the query yourself. The database is in Sqlite format and quite big, but once you have it, usage is simple and reasonably fast if you know SQL:

sqlite> select count(*) from tags where value like '%;%;%';
205966
permanent link

answered 22 Jan '16, 07:09

Jochen%20Topf's gravatar image

Jochen Topf
5.2k55074
accept rate: 31%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×483
×165
×12

question asked: 21 Jan '16, 14:32

question was seen: 2,922 times

last updated: 22 Jan '16, 08:50

NOTICE: help.openstreetmap.org is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum