Thanks, Alex.
Clarity is exactly what is needed. Ambiguity = IRB Death. I'm going to be going
through the OSM Licensing/Copyright Guidelines more closely over the next week
and will comment outside this thread, if I have comments.
For the record, I hardly think solving things like diarrhoeal
dress level geocoding?
Because either way I’m having trouble understanding why OSM is in the way to
achieving what you’re trying to do?
Best
Steve
On Oct 12, 2015, at 2:08 PM, Mr. Stace D Maples
<stacemap...@stanford.edu<mailto:stacemap...@stanford.edu>> wrote:
Thanks, Alex.
Clarity
Hello all, I’m new to this list, but wanted to chime in that I am happy to see
this thread of discussion, here. I’ve been supporting research and teaching
with geospatial tools for about 15 years (first, at Yale, now at Stanford) and
I’d like to chime in from that perspective, since the
Anyone else noticed this? Pretty hefty fine, and the article specifically
references the OSM depiction of disputed boundaries as problematic.
https://www.washingtonpost.com/news/worldviews/wp/2016/05/06/cartographers-beware-india-warns-of-15-million-fine-for-maps-it-doesnt-like/
In F,L,
Stace
