Hi Brett,
I know we've discussed this before, but for the sake of getting a
public pool of information assembled:
We, too, limit the number of fields and thus the amount of redundancy
between bg-base and our ArcMap plants table. In the ArcMap plants
table I have a field for accession# with qualifier; one field for the
genus with species only; a field for 'status'- ie alive, dead,
removed, relocated; a field for bed or area; a field for quadrant
number; a field for the 'type'- cycad, palm, conifer, other; and a few
other fields relevant to using our GPS unit. This way I'm storing only
the information pertaining directly to the map along with our most
common search criteria - by accession, genus, species, or one
individual plant. Due to our specialization, however, our most common
display criteria is the 'type', which is probably not as important at
other gardens. Anything else, including family or ssp or health status
or provenance or project code, etc, can be queried out of bg-base and
joined to the ArcMap table temporarily, which segues neatly into...
We're able to select/display plants in ArcGIS based on bg-base queries
exactly the way Becky Sucher described. We s/list a set of info (eg.
cycads that have reached maturation and are 'male' or 'female'), and
when we export the report we list the info by accession number with
qualifier, which is also a field in Arc. Our reports get exported to a
text file, which I open in xcel, convert to comma-delimited columns,
and save as a dbf IV. I add the table to the map and create a join
with the plants table based on the accession# w/qual. The join is
easily removed. This way I can select plants for display based on
whatever search criteria (eg. all Zamia amblyphyllidia that are male)
without having to store that info permanently in the arcmap plants
table and perpetually update it (eg. I can re-select from bg-base each
month after the cycads are checked for maturation and join the new
table, rather than entering the additional sex info into the arcmap
table). The trick, really, is getting good at the notoriously
persnickety s/list queries in bg-base. I know this is my limiting
factor. If you need to know about creating reports from your s/list
and exporting, call me Monday and Arantza (our database gal) and I
will go through it with you. We can probably email a template if need
be. But basically, if you can get your info into an xcel table with a
field in common with your arcmap table, you can project that info
spatially.
I'd be interested in hearing from other gardens who use BG-Base. What
fields do you maintain in Arc? how do you display your other database
information, if at all? am I doing this in the most straightforward
manner possible? The way I'm doing it now seems to keep the potential
for human error and time-consuming data-entry to a relative minimum,
but how can I be sure without seeing other methods, right?
As an aside, Mike O'Neal, et al, claim to be actively working on
providing direct links between BG-Base and Arc so that this
query/display divide won't be such an issue for us. They've been
saying this for awhile, however.
Cheers, everyone, and happy mapping,
Ericka Witcher
Collections Supervisor
Montgomery Botanical Center
305-667-3800 x.113
eri...@montgomerybotanical.org
www.montgomerybotanical.org