<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>As you’ve rightly pointed out, the frustrating part is getting the actual data - particularly the imagery. As far as we’ve discovered, there isn’t a solution which sits nicely between what is currently described in the Preparing Data chapter (foreword) and a fully automated system. The main complication being to find a solution which suits anyone anywhere in the world (different data sources suit different regions). A fully automated system can be designed to handle regional requirements, but a half-automated solution can’t (not satisfactorily anyway). </div><div><br></div><div>So in essence, I don’t think there’s much more I can suggest beyond the Preparing Data chapter. </div><div><br></div><br><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><b>George Irwin</b><br>Project and Client Manager<br>Linfiniti Consulting</div><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><a href="http://www.linfiniti.com">http://www.linfiniti.com</a><br>+27 (0)76 013 6355<br>Skype: georgeirwin22<br><br></div></div>
</div>
<br><div><div>On 14 Apr 2014, at 15:10, Paolo Cavallini <<a href="mailto:cavallini@faunalia.it">cavallini@faunalia.it</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Il 14/04/2014 14:59, George Irwin ha scritto:<br><br><blockquote type="cite">Having said that, in my (very humble) opinion, a localised dataset for a<br>training manual is a “nice-to-have” and that anyone who might want<br>localised data is also likely to be a trainer (or at least someone who<br>is very familiar with QGIS). It’s also likely that they would be putting<br>together a training package for a group of people/students and would<br>probably re-use their localised manual. With those very broad<br>assumptions in mind, the not-so-straightforward process of localising<br>the training manual becomes a bit less of a concern?<br></blockquote><br>Thanks for the reply.<br>My case is: I have to run courses in many different locations, and I<br>think having local data, although not an absolute necessity, is a nice<br>feature. I do not need a fully automated process, but a straightforward<br>solution would be important, not having to fight with different issues<br>every time.<br>Can you suggest me the best approach to this?<br>Thanks.<br>-- <br>Paolo Cavallini - <a href="http://www.faunalia.eu">www.faunalia.eu</a><br>QGIS & PostGIS courses: <a href="http://www.faunalia.eu/training.html">http://www.faunalia.eu/training.html</a><br></blockquote></div><br></body></html>