3 ms·
OpenStreetMap's definition of Beaverton is quite complicated: https://www.openstreetmap.org/relation/423111 https://www.openstreetmap.org/relation/423111 It inc
by jmkb 7y ago
OpenStreetMap's definition of Beaverton is quite complicated: https://www.openstreetmap.org/relation/423111 https://www.openstreetmap.org/relation/423111
It includes several cut-outs for neighborhoods (including Cedar Hills) and other features. I'd guess that the OSM mappers were trying to represent a particular legal definition of the Beaverton city limits. How accurate it is, I wouldn't know.
Perhaps in situations like this, "City Roads" might consider ignoring the cut-out enclaves and just using the mulipolygon's outer boundaries.
The power line showing up as a road is a mystery. If you can locate the corresponding feature on OSM you might want to investigate it. (There may in fact be a road or trail of some sort, though -- it's common for powerlines to have a track for maintenance vehicles.)
- maxerickson 7y agoThe boundary was initially imported from US Census Bureau data, which frequently does attempt to follow actual administrative boundaries. The source data tends to not be incredibly accurate.
- Sohcahtoa82 7y agoThere's definitely a little bit of fuckery regarding Beaverton's borders. My mailing address is in Beaverton, but OSM thinks it's Aloha. My zip code according to the post office is 97003, but some map software rejects it as non-existent, or forces a change to 97006. OSM's Portland borders also definitely don't match what mailing addresses are there. I used to live in apartments off of NW 185th near US-26, which most people would call Beaverton, but my mailing address was Portland, but I was at least 4 miles from anywhere people would actually call Portland. I wonder how common these confusing city limits are in other metro areas.