Add an imagery blacklist to capabilities #806
Conversation
This blacklist is for imagery which is of an incompatible license or ToS but is incorrectly used with some frequency. This adds a <policy> element to the capabilities XML which contains the blacklist information within it
|
Do the google ones not serve as tests? I don't think we should be blocking things just as a test... Should there actually be any defaults committed though? or is that a deployment issue for our instance that should be done by chef? |
I mean on errol for testing. Google isn't a good test, since JOSM is supposed to block it already, and they have painful URLs. I kind of like the defaults, provided they're not OSM specific, which, for the case of Google, they're not. I'm not tied to the idea, but we'd probably want to then add them not just to api.osm.org, but to the test APIs |
|
Well I don't have any way to add something on errol that isn't on the live site... Or are you saying you want me to do a special test site or this? Seems a bit OTT for such a simple patch... |
|
Merged. |
This blacklist is for imagery which is of an incompatible license or ToS but is incorrectly used with some frequency.
This adds a element to the capabilities XML which contains the blacklist information within it.
@tomhughes, could you deploy this branch on errol for testing?
Also, when doing so could you add
- ".*\\.stamen\\.com/.*"to application.yml? We need something blocked to test with, and stamen has layers that are unlikely to be in any presets or used.Fixes trac 5024