<p dir="ltr">Did anyone have a chance to view the attachment? Any thoughts? I'm in no way a software engineer.</p>
<p dir="ltr">Thanks guys, have yourself a great weekend!</p>
<div class="gmail_quote">On Jun 6, 2013 6:04 PM, "Lee" <<a href="mailto:muellerl@gmail.com">muellerl@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">whoops. Wrong version of the map.<br></div><div class="gmail_extra"><br clear="all"><div><br>-<font>-<br>All the best,<br>Lee<br>ISA Certified Arborist MI-4148A<br>Registered Forester #46043</font><br></div>
<br><br><div class="gmail_quote">On Thu, Jun 6, 2013 at 5:13 PM, Lee <span dir="ltr"><<a href="mailto:muellerl@gmail.com" target="_blank">muellerl@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I'm not sure the list will accept attachments, but let's give this a go.<br><div><br>I've put together a simple "project map" on how I see the toolkit's workflow, at least in my head. I'm looking for feedback and consensus moving forward. <br>
<br></div><div>I tried to use colors within the idea map to describe another level of thinking. I'm not sure how much it worked, but here's the descriptor.<br><br>Yellow - User input / handled externally.<br></div>
<div>Blue - Internal to Forestry Toolkit<br></div><div>Green - Output<br>No color - Handled completely outside QGIS/Forestry-Toolkit<br><br></div><div>Essentially, the blue boxes are the operations/utilities we need to build within Forestry-toolkit. I've tried to use brackets to describe where some of these codes or operations might already partially exist.<br>
<br></div><div>For example, in reality, we could just force the user to do their plot generation within F-tools. That said, I find F-tools largely inadequate for generating the appropriate plots. It's just not simple or straight-forward enough to use for most forestry aspects. Which is fine, since it wasn't made for that purpose. So we could probably use the F-tools code, refine it, and put it in Forestry-Toolkit for plot generation.<br>
<br></div><div>So, to dissect what's happening:<br></div><div>1. The user takes a forest parcel and uses Forestry-Toolkit to generate inventory plots.<br></div><div>2. The user goes and collects the information in the field.<br>
</div><div>3. The user enters the data into an excel spreadsheet or other format which will output a CSV.<br></div><div>4. Forestry toolkit will connect Plot ID between the plot shapefile and inventory CSV. The data will inherit a stand ID from the stand shapefile (spatial join). <br>
</div><div>6. Forestry Toolkit will run inventory data for each stand.<br></div><div><br></div><div>Is this making sense? Is this what we want to do? Is there something we should adjust? For you software guys, is this the best way of doing it?<br>
<br></div><div>Basically, do we want to move forward with this "design" and better assign some tasks?<br><br></div><div>Let's come to a consensus. I'm trying to facilitate, not lead.<br clear="all"></div>
<div><div><div><br>-<font>-<br>All the best,<br>Lee<br>ISA Certified Arborist MI-4148A<br>Registered Forester #46043</font><br></div>
</div></div></div>
</blockquote></div><br></div>
</blockquote></div>