I like this answer.  Behind the gates I tend to tag as private, but giving
one of the barriers access=destination should be enough for that to be the
default answer for going in, if implemented.

Not really something common in Oklahoma, usually gated communities have
only one way in or out that isn't an emergency access, pedestrian or
bicycle only gate.

On Wed, Mar 20, 2019 at 7:24 PM Evan Derickson <derickso...@gmail.com>
wrote:

> What about marking the resident-only gates with access=private and the
> guest gate as access=destination?
>
> On Wed, Mar 20, 2019, 16:03 Eric H. Christensen via Talk-us <
> talk-us@openstreetmap.org> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> On Wednesday, March 20, 2019 6:38 PM, Frederik Ramm <frede...@remote.org>
>> wrote:
>>
>> > Should all roads inside the gated community be access=private?
>>
>> I wouldn't necessarily mark all the roads as private as I think that
>> would hinder the routing engines.
>>
>> > What tags should be applied to (a) the main gate where visitors and
>> > delivery services are expected to report, and (b) resident-only gates?
>>
>> I've mapped a neighborhood like this before and I think I got the routing
>> to work properly by using gates at non-manned areas with access=private and
>> something else at the guard houses with access=designated or something to
>> that affect.  I think that fits the model...
>>
>> Eric "Sparks"
>> -----BEGIN PGP SIGNATURE-----
>> Version: ProtonMail
>> Comment: https://protonmail.com
>>
>> wsFcBAEBCAAGBQJcksYxAAoJEIB2q94CS7PREZoQALxqnyFgf57KuZ8btd9G
>> Rh/ttSnL2ut/P3JBddk++vM3qvxD0N6dAEQDF5X1mMYvYtwkjJ3JUm5WeFSL
>> MTt3teOV1KIJWb7fk8VsysJUatz3Q3Ksty9fevG1t5W2l+9tkXn6eNzMIL5c
>> Ztdabtgrlx/6I04IpQnPcqAjJUh48g5aQYCitfMQf3A/67/CRt0YnsYEa/79
>> 0WmOUmtxLSDdofwOwi3g6CCma6oWiAttnrCfHLQhqbALSlM9e0+VLGICT2ma
>> c3eV0tzE7qvv6Xw3ngos6uVwsnJ5ppnslBax+ZDyRlc5De0ka+XAep/VWJQc
>> oU5Yd6gYj+7xiP+loFRLQoOR2gPSf1C/nPIVBKiD0tWgiEkPK/zHA8jA6C83
>> a+ZR+BNZ5LXQsSbHGn/4R5jyXBmRSRlsQ3UajVfcaDOteRKsvW2zNQUxQJn/
>> uzCPE6H1ZkuMjNzr2qT4/IT8TXc8Qyx+rZB/q0OiJfFa1QofNOmy9rsXkxzm
>> bDdcH+swBAe6eXz1snM/hYW8HDn0aba/TPYCK5+q5B3D9ynrIH9HktPVcIs9
>> wbt4/+qhBe4bxihA5A2vntZyrQJeHqObiMHvN8a4Zs1AiMvzEw70JAth6uYo
>> 0oNrFCnHC3GZrEHZzyyGK/pjKlcevupEn4NIUZvWO1T6ph3rMLiAr241eSSy
>> xykO
>> =y2bt
>> -----END PGP SIGNATURE-----
>>
>>
>> _______________________________________________
>> Talk-us mailing list
>> Talk-us@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-us
>>
> --
>
> --
> Evan Derickson
> (360) 402-6494
> _______________________________________________
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>
_______________________________________________
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Reply via email to