{"action":"created","issue":{"url":"https://api.github.com/repos/nationalparkservice/places-data/issues/266","labels_url":"https://api.github.com/repos/nationalparkservice/places-data/issues/266/labels{/name}","comments_url":"https://api.github.com/repos/nationalparkservice/places-data/issues/266/comments","events_url":"https://api.github.com/repos/nationalparkservice/places-data/issues/266/events","html_url":"https://github.com/nationalparkservice/places-data/issues/266","id":118834861,"number":266,"title":"Boundary clipping truncates surrounding features in PT 3.0","user":{"login":"tpcolson","id":5861784,"avatar_url":"https://avatars.githubusercontent.com/u/5861784?v=3","gravatar_id":"","url":"https://api.github.com/users/tpcolson","html_url":"https://github.com/tpcolson","followers_url":"https://api.github.com/users/tpcolson/followers","following_url":"https://api.github.com/users/tpcolson/following{/other_user}","gists_url":"https://api.github.com/users/tpcolson/gists{/gist_id}","starred_url":"https://api.github.com/users/tpcolson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tpcolson/subscriptions","organizations_url":"https://api.github.com/users/tpcolson/orgs","repos_url":"https://api.github.com/users/tpcolson/repos","events_url":"https://api.github.com/users/tpcolson/events{/privacy}","received_events_url":"https://api.github.com/users/tpcolson/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/nationalparkservice/places-data/labels/park-tiles-3","name":"park-tiles-3","color":"748851"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-11-25T13:17:48Z","updated_at":"2015-11-25T15:48:03Z","closed_at":null,"body":"Boundary clipping truncates surrounding features which are necessary for visitor navigation experience. \r\nhttp://insidemaps.nps.gov/park-tiles-3/#17/35.71454/-83.52488 \r\n![image](https://cloud.githubusercontent.com/assets/5861784/11398120/9dfc19d0-934c-11e5-8e73-968007483cb5.png)\r\nhttp://insidemaps.nps.gov/park-tiles-3/#17/35.72037/-83.64175\r\n![image](https://cloud.githubusercontent.com/assets/5861784/11398132/b9d7bd4e-934c-11e5-9a40-196e14707a97.png)\r\nhttp://insidemaps.nps.gov/park-tiles-3/#16/35.7161/-83.6699\r\n![image](https://cloud.githubusercontent.com/assets/5861784/11398151/ce91db98-934c-11e5-9e19-92885c5c52b8.png)\r\nhttp://insidemaps.nps.gov/park-tiles-3/#16/35.7174/-83.8224\r\n![image](https://cloud.githubusercontent.com/assets/5861784/11398159/dc003b6c-934c-11e5-9b7e-6665ca228b0f.png)\r\nhttp://insidemaps.nps.gov/park-tiles-3/#17/35.77794/-83.11546\r\n![image](https://cloud.githubusercontent.com/assets/5861784/11398177/f8b55008-934c-11e5-8bf9-7c4f366b1752.png)\r\n"},"comment":{"url":"https://api.github.com/repos/nationalparkservice/places-data/issues/comments/159646637","html_url":"https://github.com/nationalparkservice/places-data/issues/266#issuecomment-159646637","issue_url":"https://api.github.com/repos/nationalparkservice/places-data/issues/266","id":159646637,"user":{"login":"cwlawlis802","id":1238636,"avatar_url":"https://avatars.githubusercontent.com/u/1238636?v=3","gravatar_id":"","url":"https://api.github.com/users/cwlawlis802","html_url":"https://github.com/cwlawlis802","followers_url":"https://api.github.com/users/cwlawlis802/followers","following_url":"https://api.github.com/users/cwlawlis802/following{/other_user}","gists_url":"https://api.github.com/users/cwlawlis802/gists{/gist_id}","starred_url":"https://api.github.com/users/cwlawlis802/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cwlawlis802/subscriptions","organizations_url":"https://api.github.com/users/cwlawlis802/orgs","repos_url":"https://api.github.com/users/cwlawlis802/repos","events_url":"https://api.github.com/users/cwlawlis802/events{/privacy}","received_events_url":"https://api.github.com/users/cwlawlis802/received_events","type":"User","site_admin":false},"created_at":"2015-11-25T15:48:02Z","updated_at":"2015-11-25T15:48:02Z","body":"Yes, any road segments outside a unit boundary will be available for download given they are associated with a unit code. The boundary issue in general is a political one, while I am not familiar with the need for a MOU for publishing data outside a given unit boundary. Parks and regions have been requesting this directly, given some visitor centers and other important park-owned/associated features fall outside the \"official\" management boundaries in some cases, so this should have us covered. cc @nateirwin \r\n\r\nThe concern with referencing OSM data in any way is the licensing, which prohibits us from aligning our Places data inside the park with the intersecting OSM data outside the park. The idea you propose doesn't seem to violate that, but something to keep in mind. "}}