<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Lee, I think I didn’t get the attachment. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Again thank you for facilitating.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Jake<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> forestrytools-bounces@lists.osgeo.org [mailto:forestrytools-bounces@lists.osgeo.org] <b>On Behalf Of </b>Lee<br><b>Sent:</b> Friday, June 14, 2013 10:44 AM<br><b>To:</b> ForestryTools List<br><b>Subject:</b> Re: [ForestryTools] Forestry-Toolkit Structure<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p>Did anyone have a chance to view the attachment? Any thoughts? I'm in no way a software engineer.<o:p></o:p></p><p>Thanks guys, have yourself a great weekend!<o:p></o:p></p><div><p class=MsoNormal>On Jun 6, 2013 6:04 PM, "Lee" <<a href="mailto:muellerl@gmail.com">muellerl@gmail.com</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal>whoops. Wrong version of the map.<o:p></o:p></p></div><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><p class=MsoNormal><br>--<br>All the best,<br>Lee<br>ISA Certified Arborist MI-4148A<br>Registered Forester #46043<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On Thu, Jun 6, 2013 at 5:13 PM, Lee <<a href="mailto:muellerl@gmail.com" target="_blank">muellerl@gmail.com</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal>I'm not sure the list will accept attachments, but let's give this a go.<o:p></o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><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. <o:p></o:p></p></div><div><p class=MsoNormal>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.<o:p></o:p></p></div><div><p class=MsoNormal>Blue - Internal to Forestry Toolkit<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Green - Output<br>No color - Handled completely outside QGIS/Forestry-Toolkit<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>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.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>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.<o:p></o:p></p></div><div><p class=MsoNormal>So, to dissect what's happening:<o:p></o:p></p></div><div><p class=MsoNormal>1. The user takes a forest parcel and uses Forestry-Toolkit to generate inventory plots.<o:p></o:p></p></div><div><p class=MsoNormal>2. The user goes and collects the information in the field.<o:p></o:p></p></div><div><p class=MsoNormal>3. The user enters the data into an excel spreadsheet or other format which will output a CSV.<o:p></o:p></p></div><div><p class=MsoNormal>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). <o:p></o:p></p></div><div><p class=MsoNormal>6. Forestry Toolkit will run inventory data for each stand.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>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?<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Basically, do we want to move forward with this "design" and better assign some tasks?<o:p></o:p></p></div><div><p class=MsoNormal>Let's come to a consensus. I'm trying to facilitate, not lead.<br clear=all><o:p></o:p></p></div><div><div><div><p class=MsoNormal><br>--<br>All the best,<br>Lee<br>ISA Certified Arborist MI-4148A<br>Registered Forester #46043<o:p></o:p></p></div></div></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>