too many barrier=gate related error logs from the log report

[maning]

2011/03/29 20:12:32 WARNING (StyledConverter): philippines.osm: Motorway exit Gate 3 (http://www.openstreetmap.org/?mlat=14.60062&mlon=121.07191&zoom=17) has no motorway! (either make the exit share a node with the motorway or specify the motorway ref with a exit:road_ref tag)

The giveaway is that it's called "Gate 3." If you look at it in JOSM you'll see it's a gate on a residential street.

Many barrier gates are not part of a motorway exits.

[maning]

@ralleon, maybe we can change the style '0x2001 and others` are for Motorway exits / services

[ralleon]

ok. in which case we should differentiate barrier (for motorway exits), and regular gates?

what will be our additional 'distinguishing tag' for:

1. expressway toll exits
2. expressway toll barrier (toll plazas)
3. gated subdivision gate
4. building entrances for mall complex / hospital /hotel etc

only 1 & 2 are exits (as far as garmin hex codes are concerned)

3 & 4 are not exits (no hex available for garmin) --- we can just assign a none-search-able gate icon (but we need to add additional tag), else they are interpreted in style filter as motorway-exit

On Thu, Mar 31, 2011 at 7:50 PM, maning < reply@reply.github.com>wrote:

@ralleon, maybe we can change the style '0x2001 and others` are for Motorway exits / services

Reply to this email directly or view it on GitHub: https://github.com/maning/osmphgps/issues/12#comment_940652

[maning]

+1 on the non-searchable hex for items 3 & 4

[ralleon]

initial proposal for style: maintain the following valid motorway exit/barrier tags

Expressway Toll Booth

barrier=toll_booth [0x2500 resolution 23 default_name 'Toll'] highway=toll_booth [0x2501 resolution 19 default_name 'Toll']

Motorway Exit Point (junction)

highway=motorway_junction { name '${ref} ${name}' | '${ref}' | '${name}' } highway=motorway_junction [0x2701 resolution 19 default_name 'Exit Point']

Sevice Exit Point (StopOver) for Fuel / Restroom / Shops

highway=services { name '${ref} ${name}' | '${ref}' | '${name}' } highway=services [0x2702 resolution 19]

---

make all barrier=gate and all none-"barrier=toll-booth" will become none searchable eg:

barrier=gate & access=private [0x2002 resolution 24] barrier=gate & access=permissive [0x2003 resolution 24] barrier=gate & access=pedestrian [0x2004 resolution 24] barrier=gate & access=closed [0x2005 resolution 24] highway=gate [0x2001 resolution 24] barrier=gate [0x2001 resolution 24] barrier=sally_port [0x2001 resolution 24] barrier=bollard | barrier=bus_trap {add access = no; add bicycle = yes; add foot = yes} [0x660f resolution 21] barrier=block | barrier=cycle_barier | barrier=stile | barrier=kissing_gate {add access = no; add foot = yes} [0x660f resolution 21]

On Thu, Mar 31, 2011 at 8:50 PM, maning < reply@reply.github.com>wrote:

+1 on the non-searcheable hex for items 3 & 4

Reply to this email directly or view it on GitHub: https://github.com/maning/osmphgps/issues/12#comment_940823