Hey there Chemmike,
There is a great Excel spreadsheet published by the USGS which studies
trace elements in 541 streambed-sediment samples collected from 20
study areas across the United States:
http://co.water.usgs.gov/trace/data/est_v33n15_p2499.xls
I know you need ground water chemistry data on Si, but this is the
only pre-existing spread sheet remotely close to what you had in mind.
Your specific need follows:
Specific national groundwater chemistry data with reference to silica
is available in tab-delimited text tables from the USGS National
Water-Quality Assessment (NAWQA) Program Nutrients National Synthesis
web site. these tables can easily be transferred to a data base if
need be, but the text is searchable in any text editor, like Notepad,
or in MS Word if you create a Word document with the data.
In the tables, Silica is represented by the code P00955, where it is
dissolved, in mg/L as SiO2.
The explanation of the ground water table data can be downloaded here:
http://water.usgs.gov/nawqa/nutrients/datasets/cycle91/gwexp.txt
_____________________________________
Shallow Ground-Water Nutrients Beneath Specific Land Use Areas (267k)
http://water.usgs.gov/nawqa/nutrients/datasets/cycle91/lus_tab.txt
_____________________________________
Deeper Ground-Water (Major Aquifers) Nutrients (186k)
http://water.usgs.gov/nawqa/nutrients/datasets/cycle91/sus_tab.txt
_____________________________________
Ground Water Site Description (120k)
http://water.usgs.gov/nawqa/nutrients/datasets/cycle91/gwsite_tab.txt
The text table data on ground water can be accessed at the USGS site
National Water-Quality Assessment (NAWQA) Program Nutrients National
Synthesis at:
http://water.usgs.gov/nawqa/nutrients/datasets/cycle91/
Im fairly certain that this is the data that you requested. If you
need any clarifications, or even help on converting text tables into a
data base, dont hesitate to contact me back here. If you select the
Request Clarification button, I am notified via e-mail, as opposed
to only leaving a Comment, in which case I am not notified.
Thanks for a fun search!
Kutsavi
SEARCH TERMS:
ground water data
://www.google.com/search?num=100&hl=en&lr=&ie=UTF-8&oe=utf-8&q=ground+water+data&btnG=Google+Search
national ground water data
://www.google.com/search?q=national+ground+water+data&sourceid=opera&num=100&ie=utf-8&oe=utf-8
national ground water silica content
://www.google.com/search?num=100&hl=en&lr=&ie=UTF-8&oe=utf-8&q=national+ground+water+silica+content&btnG=Google+Search
ground water chemistry silica
://www.google.com/search?num=100&hl=en&lr=&ie=UTF-8&oe=utf-8&q=ground+water+chemistry+silica&btnG=Google+Search
groundwater chemistry silica
://www.google.com/search?num=100&hl=en&lr=&ie=UTF-8&oe=utf-8&q=groundwater+chemistry+silica&btnG=Google+Search |
Request for Answer Clarification by
chemmike-ga
on
06 Dec 2002 12:30 PST
I imported all the tables without any problem into MS Access. However
when trying to link the tabel gwsite_tab (the water stations) with
lus_tab (chemistry data), the ID`s did not macth. The Station ID`s are
very long 15 characters. It looks like only the first 6 match, but
then with double countings. I realize that this is more a Database
question, but maybe you have an answer, and also if the Station ID
number has a certain logic or meaning behind it.
|
Clarification of Answer by
kutsavi-ga
on
06 Dec 2002 13:07 PST
I do indeed see the discrepancy. I wrote the following message to the
person responsible for the maintenace of that specific page at the
USGS, and am waiting for his response:
_________________________________
Greetings,
In researching groundwater data, I have come across something that I
can't quite bring together as far as site descriptions are concerned.
I am referring to the Groundwater Data on the page you maintain:
http://water.usgs.gov/nawqa/nutrients/datasets/cycle91/
My specific problem is this:
In looking at the Shallow Ground-Water Nutrients Beneath Specific Land
Use Areas, with the URL of
http://water.usgs.gov/nawqa/nutrients/datasets/cycle91/lus_tab.txt
The site location descriptions seem to have no correlation whatsoever
with those listed in the Ground Water Site Description, with the URL
of
http://water.usgs.gov/nawqa/nutrients/datasets/cycle91/gwsite_tab.txt
I had wanted to merge the two in an Accel data base, however, as I
mentioned above, there doesn't seem to be any way to correlate the
data regarding site location. In the Nutrients table, the sites are
listed under "SUCODE" or "STAID". SUCODE have this format:
"acfblusag1" while STAID have the format "ag". Now, in the Nutrient
studies, site identification is done by latitude and longitude, as
well as by a Station Number in the format "2753470". How do I relate
these data?
Any help would be appreciated.
|
Clarification of Answer by
kutsavi-ga
on
06 Dec 2002 13:50 PST
Hey again Chemmike,
I received an almost immediate response from the USGS that I hope will
answer the problem, which apparently has to do with a simple alignment
problem. I will post his reply in full, and hope that this is what
you need:
_____________________________________________
The two files can be linked using the Station id number (called STAID
in
lus_tab.txt and STATION in gwsite_tab.txt). This is usually a
15-digit
number.
In the data files, the headings look like they are offset from the
columns
of data because the files are tab delimited. Please check the
explanations
to make sure you are clear on what the values of the fields should
look
like.
The station in lus_tab.txt:
SUCODE-- acfblusag1
TYPE---- ag
STAID--- 305021085211401
etc
The corresponding station info in gwsite_tab.txt for that STAID:
STATION---- 305021085211401
LATITUDE--- 305022
LONGITUDE-- 0852114
LATDD------ 30.839
LONDD------ -85.354
etc
_______________________________________________
Make sure to let me know if this solves the problem!
Kutsavi
|
Request for Answer Clarification by
chemmike-ga
on
06 Dec 2002 14:51 PST
Thanks for your reply,
I indeed tried to link through the 15 charachter Station ID. It looks
like only the first 6 characters match, the next 9 characters do not
match wherefore none are linked as we try to link the full 15
characters. An explanation could be that in the table with the
stations and lat., Long. not all the stations with full 15 characters
ID are listed.
|
Clarification of Answer by
kutsavi-ga
on
06 Dec 2002 15:58 PST
Gads, sorry about these problems. I've copied and sent your
description of the issue back to the USGS. I also asked if he
happened to have a database already constructed with this data, which
in hindsight might have been a good idea in the first place.
In order to get you going and to be more efficient, I origininally
posted the URL for the main page the data is on, which was:
http://water.usgs.gov/nawqa/nutrients/datasets/cycle91/
The gentleman's name that takes care of the page and his contacts are
at the bottom of the page. If the problem isn't remedied quickly, you
will at least have his contact information. But as I said, I've
written him, and asked for a completed database already, so if
possible, allow a little time.
While waiting for them to respond, (which now, because it's Friday
afternoon, may not be until Monday), I wonder if the problem might lie
with the transportation of data from the original tab.text into your
database.
What you might try is to go back into the original file and extract
three or four complete entries, then make a file out of them, and then
try to import them into a new "mini database," just to make sure the
numbers line in columns where they are supposed to.
I noticed that some of the columns are uncomfortably close to
eachother, and may need to be separated during the importation
process. If you are using Windows XP, and simply right-clicking to
import into the data base, you might want to acutally open Access
first and use the "Get Data" -> "external file" option from the file
menu. This should allow you to put in a space between columns if one
isn't there that should be. (You would want to do this, of course, to
see if the problem was simply with the importation process.)
I will post the USGS reply here as soon as it comes in, but I would
also advise trying the above experiment.
Again, sorry for the problems.
Kutsavi
|