InfoVeg: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362010-07-28T17:36:55ZEcoinformatics Redmine
Redmine Bug #5105 (In Progress): have x- specimens maphttps://projects.ecoinformatics.org/ecoinfo/issues/51052010-07-28T17:36:55ZMichael Leemlee@nceas.ucsb.edu
<p>example X-UNCC, X-WNC, etc.</p>
<p>reported by Carol Ann</p> Bug #3611 (In Progress): Newell R module = supersample?https://projects.ecoinformatics.org/ecoinfo/issues/36112008-11-08T05:54:33ZMichael Leemlee@nceas.ucsb.edu
<blockquote>
<p>I have discovered a rather surprising anomaly in our database. I am<br />working on making sure that the calculation of R module size is<br />correct for tree stems, which is necessary for getting basal area<br />correct, at least at that modular level. This is relatively<br />straightforward, because the tree size of the plot is known, and so<br />are the number of intensive tree modules (generally- sometimes if no<br />trees are in a module, it doesn't get recorded and so it's not clear<br />if the empty module is really empty or part of R. This email is not<br />addressing that minor issue).</p>
<p>There are 30 plots in the database that have the same number of<br />intensive modules as tree plot size (e.g. plot size of 2 and intensive<br />modules are 1 and 2) that ALSO have tree module R. So it begs the<br />question, what is the R module representing. Claire Newell's plots<br />(project 10 and 11) are the only ones this way, and all of them are<br />supersampled. It seems clear to me that the R module is where she<br />parked the extra stems from supersampling, which is to say that the<br />intensive module numbers are NOT supersampled. The R module, when<br />added to the 1 or more intensive modules, would accurately represent<br />the super sample.</p>
<p>So I'm not exactly sure what to do about these. Her data do make<br />sense if only analyzed at the plot level, ignoring the modules. That<br />would be option A for these plots: remove all module information and<br />call all rows module R. I briefly thought about creating R modules<br />and increasing the plot size to match them, but the difficulty there<br />is that not all species are supersampled always, thus module R is not<br />really a complete module. That would be option B, which I no longer<br />consider hopeful. Option C would be to split up the R modules's stems<br />and distribute them amongst the various intensively sampled modules,<br />of which there are 4 times only 1 (that's easy enough), 19 times 2<br />modules, 3 times 3 modules, and 4 times 4 modules.</p>
<p>I like option A: to remove all intensive module information from these<br />30 plots and then the supersampling is accurate. Please let me know<br />(soon) what you would like me to do.</p>
<p>To see the raw data, see text files:<br />\\Bioark\peetlab\CVS\CVS_Projects\10_Linville\10_trees.arc<br />\\Bioark\peetlab\CVS\CVS_Projects\11_Shining\11_trees.arc<br />plots:<br />010-0C-0013<br />010-0C-0020<br />010-0C-0025<br />010-0C-0027<br />010-0C-0029<br />010-0C-0053<br />010-0C-0056<br />010-0C-0057<br />010-0C-0059<br />010-0C-0062<br />010-0C-0082<br />010-0C-0085<br />010-0C-0087<br />010-0C-0091<br />010-0C-0096<br />010-0C-0097<br />010-0C-0101<br />010-0C-0112<br />010-0C-0176<br />011-0C-0302<br />011-0C-0309<br />011-0C-0314<br />011-0C-0350<br />011-0C-0396<br />011-0C-0400<br />011-0C-0405<br />011-0C-0410<br />011-0C-0416<br />011-0C-0434<br />011-0C-0441</p>
</blockquote> Bug #3532 (In Progress): Revise elevation based on NASA datahttps://projects.ecoinformatics.org/ecoinfo/issues/35322008-10-16T16:58:36ZMichael Leemlee@nceas.ucsb.edu
<p>five things:<br />1) get elevation data from Jenn for our plots (Forbes)<br />2) check elevations and flag any that are significantly different (raw difference + percent different, i.e. 0-50 is flagged differently than 1000-1050).<br />3) check flagged elevations and decide on a value<br />4) apply new elevation values to database<br />5) provide Lee Anne with a copy of new elevation data.</p> Bug #3432 (New): Upgrade patching systemhttps://projects.ecoinformatics.org/ecoinfo/issues/34322008-06-26T00:22:18ZMichael Leemlee@nceas.ucsb.edu
<p>We need a better patching system, which is very basic at best. Currently you have to know about a patch (via the listserv) and download it from there. Would be a lot better if you asked it to check for updates, and it would download the list of available updates from CVS. Each update would have SQL that it would use to determine if the entry tool needed/could use the patch. If so, it would prompt you to download and apply it, but backup your database first.</p> Bug #3010 (In Progress): Should encode strings in URL requesting mapping of plotshttps://projects.ecoinformatics.org/ecoinfo/issues/30102007-11-23T18:38:33ZMichael Leemlee@nceas.ucsb.edu
<p>Here's some help for characters that need encoding:<br /><a class="external" href="http://www.blooberry.com/indexdot/html/topics/urlencoding.htm">http://www.blooberry.com/indexdot/html/topics/urlencoding.htm</a></p> Bug #2924 (New): Add "use defaults on this plot" for parties and place namehttps://projects.ecoinformatics.org/ecoinfo/issues/29242007-09-01T19:11:58ZMichael Leemlee@nceas.ucsb.edu
<p>There is an option to use default for parties and place names, but a message appears saying you can't do that yet.</p> Bug #2906 (New): DBA: reports could be improvedhttps://projects.ecoinformatics.org/ecoinfo/issues/29062007-08-17T18:32:47ZMichael Leemlee@nceas.ucsb.edu
<p>Would be nice to allow printing of full plots for plots that have some issue (a check box somewhere on the DBA form, perhaps) which would then change criteria to plotID in (select plotID from [somewhere] WHERE (the criteria));</p>
<p>ordering by plotID in the reports is problematic: this is order they were entered, not logical order. Should be switched to PTP.</p>
<p>duplText is not highlighted any colour on the report, which is odd. Should be yellowish and errors pink to draw attention to these locations when there are errors or duplicate messages.</p> Bug #2868 (In Progress): upgrade taxonomy using TaxonOccurence Spreadsheet (aka Cover_ver4_withCBS)https://projects.ecoinformatics.org/ecoinfo/issues/28682007-06-07T18:44:51ZMichael Leemlee@nceas.ucsb.edu
<p>Could be Weakley 06 or 07.</p> Bug #2760 (New): add Quick fix for common errorshttps://projects.ecoinformatics.org/ecoinfo/issues/27602007-02-05T23:50:35ZMichael Leemlee@nceas.ucsb.edu
<p>need a quick fix for longitude is positive<br />also for filling in default of 10cm for minimum stem size.</p> Bug #2666 (New): ready for DBA: Project 76 (Elizabeth City, NC): 52 plotshttps://projects.ecoinformatics.org/ecoinfo/issues/26662006-11-13T17:48:11ZMichael Leemlee@nceas.ucsb.edu
<p>this data needs to be processed and added to the (v2006) central archive<br />(Forbes writing:)</p>
<blockquote>
<p>For now, I would suggest that you use plots from Project 75 and 76 for error<br />checking. These plots have been "hand-checked" as precisely as possible<br />last week to avoid any major hang ups on your end.<br />They can be found at:</p>
<p>\\Bioark\peetlab\CVS\CVS_Projects\76_2006B-ElizabethCity\CVS_EEP_DataEntry_v<br />20_Project76</p>
</blockquote> Bug #2665 (New): Ready for DBA process: Project 75 (Singletary Lake, NC): 52 plotshttps://projects.ecoinformatics.org/ecoinfo/issues/26652006-11-13T17:47:21ZMichael Leemlee@nceas.ucsb.edu
<p>this data needs to be processed and added to the (v2006) central archive<br />(Forbes writing:)</p>
<blockquote>
<p>For now, I would suggest that you use plots from Project 75 and 76 for error<br />checking. These plots have been "hand-checked" as precisely as possible<br />last week to avoid any major hang ups on your end.<br />They can be found, respectively at:</p>
<p>\\Bioark\peetlab\CVS\CVS_Projects\75_2006A-SingletaryLake\CVS_EEP_DataEntry_<br />v20_Proj75</p>
</blockquote> Bug #2663 (New): 2 errs left: + duplicates flagged: Project 73 (Mountain Bogs): 64 plotshttps://projects.ecoinformatics.org/ecoinfo/issues/26632006-11-13T17:46:29ZMichael Leemlee@nceas.ucsb.edu
<p>this data needs to be processed and added to the (v2006) central archive</p> Bug #2662 (New): Unfolding: Project 64 (Brunswick Co. NC): 88 plotshttps://projects.ecoinformatics.org/ecoinfo/issues/26622006-11-13T17:46:10ZMichael Leemlee@nceas.ucsb.edu
<p>this data needs to be processed and added to the (v2006) central archive</p> Bug #2661 (New): comments in XLS resolve: Project 63 (Francis Marion NF): 54 plotshttps://projects.ecoinformatics.org/ecoinfo/issues/26612006-11-13T17:45:48ZMichael Leemlee@nceas.ucsb.edu
<p>this data needs to be processed and added to the (v2006) central archive</p> Bug #2640 (New): Identify USDA species without county distribution where other spp in genus have ...https://projects.ecoinformatics.org/ecoinfo/issues/26402006-11-02T19:09:58ZRobert Peetpeet@unc.edu
<p>Look at PERSBOR s.s. with all those records for NC, SC, GA, AL that are<br />actually P. palustris. We need a solution.</p>
<p>1. Create a list of all the taxa that PLANTS reports for NC&SC with no county records but for which they do report county records for other taxa in the genus. Mike Lee should do this based on USDA data I have in hand. Once this is done, the process should be repeated for each of the states in the region.</p>
<p>2. Once we have the lists, Alan should examine the taxa and the USDA maps, and should create a list of taxa with too many records and a list of taxa with too few records. The final lists should be shared with USDA and BONAP. Highest priority should be to complete the NC&SC list.</p>
<p>3. These lists contain sets of taxa that should be treated as nominals rather than USDA/JK99 concepts. We should break the USDA taxa in our database into two groups with one = USDA concepts, and the second = nominal concepts. We can assign this step to Mike Lee. I will need to explain to Michael now to access the database in which the county occurrence data are stored.</p>
<p>4. As a separate and contingent bug, Xianhua should split USDA in the legend into into two labels and make any code changes necessary to support this split</p>