Re: [Talk-us] gunnison national forest not being rendered

2019-03-02 Thread Mateusz Konieczny
Have you tried loading affected relation in JOSM and running validator? It often spots important problems. If you want to do it but gave no idea how to do it, let us know and I will explain it in detail. Mar 3, 2019, 12:15 AM by bradha...@fastmail.com: > Help me understand why Gunnison NF is

Re: [Talk-us] gunnison national forest not being rendered

2019-03-02 Thread Clifford Snow
I'm not sure it's tagged correctly. boundary:type=protected_area, should be boundary=protected_area. Although I do see boundary:type in use. See https://wiki.openstreetmap.org/wiki/Tag:boundary%3Dprotected_area See https://www.openstreetmap.org/relation/1399218#map=9/47.9660/-121.5472 for a

Re: [Talk-us] Road name update challenges

2019-03-02 Thread Clifford Snow
On Sat, Mar 2, 2019 at 5:27 AM Mike N wrote: > On 3/1/2019 12:49 PM, Clifford Snow wrote: > > > > One caution - when doing a building/address import a few years ago, we > > discovered errors in the counties address database. They had different > > street names from address street names. The

Re: [Talk-us] Road name update challenges

2019-03-02 Thread Mike N
On 3/1/2019 12:49 PM, Clifford Snow wrote: One caution - when doing a building/address import a few years ago, we discovered errors in the counties address database. They had different street names from address street names. The street names matched the street signs but the addresses had a

Re: [Talk-us] Road name update challenges

2019-03-02 Thread Mike N
On 3/1/2019 10:09 AM, Aaron Forsythe wrote: >> 1. Original TIGER had Ruppe Dr at a nearby but incorrect location. This seems a common enough occurrence that a TIGER data should not be used as permanent source.  It's only there to get the map started and adjustments from TIGER are required.