On 8/21/19 5:17 PM, Joseph Eisenberg wrote:
> I agree with Martin. It's not good practice to use semicolons in the
> value of the main feature tag, like amenity=bbq;bear_box, because this
> is hard for database users to interpret with a simple algorithm.

  Actually I've found the opposite. Importing into Postgresql doesn't
support multiple tags of the same name. At least not when importing
using ogr. I do produce maps from Postgresql, and have no problem with
semi-colons. Course I'm using my own software for SQL queries. I'd be
curious what OsmAnd does when displaying 'tourism' POIs.

> At the proposal
> (https://wiki.openstreetmap.org/wiki/Proposed_features/Campsite_properties)
> there are a list of property tags which are already approved or "de
> facto" in common use on camp_site (and camp_pitch) features, like
> this:

  I saw that, but they're proposed, so I've been trying to stick to
what's approved. I already do use many of the existing properties.

> Note that there are also feature tags for almost all of these, like:
> amenity=drinking_water
> amenity=recycling
> amenity=sanitary_dump_station
> amenity=toilets

  Using properties works fine for my purpose, and if it's ok to create a
new property 'bear_box=(yes,no)', I can do it that way. I'm not in a
hurry, so can also wait for the proposal to hopefully get approved.

> Hence: amenity=bear_box on it's own node, right at the location of the
> box. Or if you don't have that info or just want to say that "there is
> a bear box at this campground", you can add bear_box=yes/no to the
> tourism=camp_site

  So now it seems it'd be "bbq=yes', 'picnic_table=yes', 'bear_box'yes'.

        - rob -

Tagging mailing list

Reply via email to