Welcome to Fluther.
I have only the vaguest notion of the survey that you’re trying to accomplish, but I do understand data.
What will serve you very well for this is a Microsoft Access (or equivalent, or better) database.
The first thing that you’ll want is a table for Species. Let’s call it tbl_Species.
The table should consist of the following minimum fields:
Species_ID – Autonumber – Primary Key
Species – Text – Indexed, Unique (no duplicates)
ConsVal – Integer (apparently) – “Conservation Value”
Save the table design, and start to enter your species (in any order) and associated conservation values.
Now you have a table of unique species, identified by also unique “Species_ID” numbers (meaningless to you, but important to the database) and associated Conservation Values that can be used in later computation.
Make another table of Quadrats, called tbl_Quad, consisting of:
Quad_ID – Autonumber
Quadrat – Text (Can be a name or number)
[You may eventually want to add another table to the database for “Survey” to identify each new survey that you want to record, and that would enable you to add another field for “Survey” to the Quadrat table in order to help make each Quadrat unique. By that I mean you may do a survey for Boston – and even “surveys for Boston” may not be unique; you may want to do one in the spring, one in the fall, and additional ones in succeeding years, and you’ll obviously want to differentiate each from the other – and you do not want to have to set up separate tables or databases for each survey. But that’s getting into more complexity than I’m going to deal with in a single response here.]
With those tables built, you are now ready to create the final (minimum) table required, which we can call tbl_Survey. The first field will be another Autonumber / Primary Key field which we’ll call “Obs_ID” (for Observation ID).
Next you’ll create a field called “Quadrat”, which will be a “Lookup” value into tbl_Quads so that data entries in tbl_Survey will be restricted to Quadrats which have already been included in the proper Quadrat table.
Following that field you’ll have a “Species” table which pulls only species you have already entered into tbl_Species.
Save the table and enter some “observations” such as the ones you have listed above.
Now you can build a Query of the database.
The Query will link tbl_Survey with tbl_Species on the Species_ID field (common to both tables) and pull the related “Conservation Value” field from tbl_Species. See how that works? Since you have a unique ID in tbl_Species every value of “Species” in tbl_Survey corresponds to one and only one Species_ID in tbl_Species, and can bring over whatever data is related to that Species_ID. It never gets lost, misplaced, mistyped, forgotten, etc.
Your query can also store the math equation you want to store (any number of them, in fact). Different queries can perform in different ways. What you want, apparently, is a type of “Summary” query which will perform the averages you want to record, quadrat by quadrat.
That just gets you started. So far, this seems to be a simple enough exercise, which will only get more complex as your understanding improves and your needs increase.