On Sep 24, 2017 8:33 AM, "Greg Troxel" <[email protected]> wrote:
Adam Franco <[email protected]> writes: > One additional note is that at least in my area, the TIGER import > incorrectly added access=private to many driveways and privately maintained > residential roads. Upon surveying these I've found that they are signed > "Private" or "PVT" on the street-name sign to indicate > private-maintenance/ownership (don't complain to the town about a lack of > snow-plowing/grading), but do not in reality have an access restriction. https://www.mapillary.com/app/?focus=photo&pKey=oyEdoFPUg3yayTv1deHZUQ&lat=33.567826&lng=-112.016051&z=17 I initially marked a street like this as access=private. Then I found out that this definition of private is more like Adam's experience. However, I did not experience the issue with the TIGER import. I am not sure that an HOA is a good thing. I stay away from them for a number of reasons including the leftovers of the subprime rate debacle. http://www.azcentral.com/story/news/local/arizona-investigations/2017/09/14/phoenix-area-homeowners-associations-foreclosing-record-number-homeowners/595816001/ For a "private way" (legal term in my state for what I think you refer to as "privately maintained residential road"), I agree that there shouldn't be access=private. For a driveway to someone's house, access=private seems right, in that it's generally at least impolite to use that road other than as visitor/delivery/etc. ... But, that tends to lead to pink blobs in rendering, and I'm not sure that's the right thing, as service roads having the status "you should use these only when dealing with the adjacent entities" seems to be the default/normal case. We should adjust rendering, not access, to make this pleasing. The rendering has been changed to a gray dashed center line. Regards, Greg
_______________________________________________ Talk-us mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-us
