Geodatabase Point Data

Stations (site specific data)

[kind] O = generic observation

[kind] A = age

[kind] G = graphic data

[kind] R = sample sites

[kind] Y = analytical








Age categories (prefix 1)

a = Argon-Argon

r = radiocarbon

t = tephrochronologic

c = cosmogenic
Graphic data categories

p = photograph

s = sketch
Sample site categories

r = rock


s = sediment

t = tephra

Analytical categories


f = fluvial transport direction

g = fluvial gravel lag

This is the structure of point data that we have built into the geodatabase. It covers all of the ground that I could recall for this project. Please look it over and let me know if you see a problem or an omission. *Note that the category for 'generic observation' very often includes a photograph or a graphic (sketch). This may be parsed too finely. That being said, I just noticed that I need to include a code for osl sample (Ao).

Geodatabase to the nth degree

OK, this is a long one, but I wanted everyone to see the set of line-codes that I am integrating into the geodatabase. The codes are based on terminology in the new digital geologic map standards published by the FGDC. The seemingly overly detailed list is based on degrees of certainty relative to two aspects of lines on a geologic map: 1. What sort of line it is and how certain you are about that; and 2. How well the line's location is known.

Each funny looking code is a combination of the following characters that account for a variety of lines and a variety of degrees of certainty about what and where they are:

Line Types [kind]

  • C Contact
  • X Fault
  • R Rock body (marker bed or key bed)
  • Z Scarp (as feature, not contact)
  • M Morphologic
  • B Boundary
Prefixes [category]
  • g generic
  • l landslide
  • i internal
  • f fluvial
  • v volcanic
  • s sedimentary
  • z scarp
  • d depression
  • m morphologic feature
Suffixes [location]
  • c certain
  • q questionable
  • a accurate
  • x approximate
  • c concealed
  • i inferred
Code followed by Name
  • uB Boundary—undifferentiated
  • mB Boundary—mapsheet
  • pB Boundary—property
  • sB Boundary—scratch
  • wB Boundary—water
  • eB Boundary—exclusion
  • gCca Contact—Identity and existence certain, location accurate
  • gCqa Contact—Identity or existence questionable, location accurate
  • gCcx Contact—Identity and existence certain, location approximate
  • gCqx Contact—Identity or existence questionable, location approximate
  • gCci Contact—Identity and existence certain, location inferred
  • gCqi Contact—Identity or existence questionable, location inferred
  • iCca Internal contact—Identity and existence certain, location accurate
  • iCqa Internal contact—Identity or existence questionable, location accurate
  • iCcx Internal contact—Identity and existence certain, location approximate
  • iCqx Internal contact—Identity or existence questionable, location approximate
  • sCca Incised-scarp sedimentary contact—Identity and existence certain, location accurate.
  • sCqa Incised-scarp sedimentary contact—Identity or existence questionable, location accurate.
  • sCcx Incised-scarp sedimentary contact—Identity and existence certain, location approximate.
  • sCqx Incised-scarp sedimentary contact—Identity or existence questionable, location approx.
  • ldCca Sag-pond or closed depression on landslide (mapped to scale)
  • viCca Contact separating individual lava flows within same map unit—Identity and existence certain, location accurate
  • viCcx Contact separating individual lava flows within same map unit—Identity and existence certain, location approximate
  • viCqx Contact separating individual lava flows within same map unit—Identity or existence questionable, location approximate
  • gXca Fault (generic; vertical, subvertical, or high-angle; or unknown or unspecified orientation or sense of slip)—Identity and existence certain, location accurate
  • gXqa Fault (generic; vertical, subvertical, or high-angle; or unknown or unspecified orientation or sense of slip)—Identity or existence questionable, location accurate
  • gXqx Fault (generic; vertical, subvertical, or high-angle; or unknown or unspecified orientation or sense of slip)—Identity or existence questionable, location approximate
  • gXcc Fault (generic; vertical, subvertical, or high-angle; or unknown or unspecified orientation or sense of slip)—Identity and existence certain, location concealed
  • kRca Key bed—Identity and existence certain, location accurate
  • kRcx Key bed—Identity and existence certain, location approximate
  • fZca Fluvial terrace scarp—Identity and existence certain, location accurate. Hachures point down scarp
  • fZqa Fluvial terrace scarp—Identity or existence questionable, location accurate. Hachures point down scarp
  • fZcx Fluvial terrace scarp—Identity and existence certain, location approximate. Hachures point downscarp
  • lZca Head or main scarp of landslide—Active, sharp, distinct, and accurately located. Hachures point down scarp
  • lZcx Head or main scarp of landslide—Inactive, subdued, indistinct, and (or) approximately located. Hachures point down scarp
  • liZca Internal or minor scarp in landslide—Active, sharp,distinct, and accurately located. Hachures point down scarp
  • liZcx Internal or minor scarp in landslide—Inactive, subdued, indistinct, and (or) approximately located. Hachures point down scarp
  • vMca Flow lobe or lava-flow front—Identity and existence certain, location accurate. Hachures on side of overlying younger flow
  • vMqa Flow lobe or lava-flow front—Identity or existence questionable, location accurate. Hachures on side of overlying younger flow
  • vMcx Flow lobe or lava-flow front—Identity and existence certain, location approximate. Hachures on side of overlying younger flow
  • vMqa Flow lobe or lava-flow front—Identity or existence questionable, location approximate. Hachures onside of overlying younger flow
  • vMm Crest line of pressure ridge or tumulus on lava flow

Digital fold axis data for Oregon?

For some time, I've been wanting to look at the relationship between landslide distribution and structural features of our study region. I'd been thinking I'd look at proximity of landslides to fold axes, because it was fixed in my mind that digital fold axis data exist for Oregon, whereas digital strike and dip data do not. However, when I sat down to start figuring out how to do this analysis, I could find no such data. I plumbed the metadata and coverages associated with the 1991 Walker and MacLeod 1:500,000 map, as well as the info about the latest DOGAMI digital geology compilation. Nothing. Did I just fabricate this idea that fold axis data exist?? Does anyone have or know of digital data for central/eastern Oregon that might give clues about stratigraphic attitudes (there's a bit of info about fault plane dips, but that's all I could find)?

First Draft of Map Units

Label Description
Tbu Undifferentiated basalt flows, Pliocene to Miocene
Tsv Interbedded volcanic and volcaniclastic rocks, Miocene
Tru Undifferentiated rhyolite flows, Miocene
Tro Older rhyolite flows, Miocene
Try Younger rhyolite flows, Miocene
Tsu Undifferentiated sedimentary rocks, Miocene
Trg Fluvial gravel, Pliocene(?)
Tfl Fluvio-lacustrine deposits, Pliocene(?)
QTbu Undifferentiated basalts of Bogus Butte
QTbr Basalts of Bogus Rim, Pleistocene(?) to Pliocene
QTrg Fluvial gravels of Bogus Rim, Pleistocene to Pliocene
QTbb Basalt of Greeley Bar, Pleistocene to Pliocene
Qrgu Undifferentiated fluvial gravel, Pleistocene
QTbg Sub-volcanic fluvial gravel, Pleistocene(?) to Pliocene
Qbg Sub-volcanic fluvial gravel, Pleistocene
Qbu Undifferentiated basalt flows, Pleistocene
Qbc Basalt of Clarks Butte
Qbs Basalt of Saddle Butte
Qbso Older basalt of Saddle Butte
Qbsy Younger basalt of Saddle Butte
Qrgo Older fluvial gravel, Pleistocene
Qflo Older fluvio-lacustrine sediments, Pleistocene
Qbw Basalt of West Crater, Pleistocene
Qrgi Intermediate fluvial gravel, Pleistocene
Qfli Intermediate fluvio-lacustrine sediments, Pleistocene
Qgb Fluvial boulder-gravel, Pleistocene
Qrt Fluvial terrace gravels, Pleistocene
Qry Younger fluvial gravels, Holocene to Pleistocene
Qra Alluvium of the active fluvial system, Holocene
Qlsr Landslide deposits, dominantly rotational
Qlsc Bouldery landslide deposits, dominantly cantilever
Qlsf Landslide deposits, dominantly earthflow
Qls Landslide deposits, undifferentiated
QTf Ancient Alluvial fan deposits, Pleistocene(?) to Pliocene
Qfo Old Alluvial fan deposits, Pleistocene
Qfi Intermediate age alluvial fan deposits, Pleistocene
Qfy Young alluvial fan deposits, Holocene to late Pleistocene
Qc Colluvium, Undivided, Holocene to Pleistocene
Qe Eolian deposits, Holocene to late Pleistocene(?)
Qel Eolian deposits, loess, Pleistocene

Yep, its late, but I had to get this list to the chief cartographer by today in order to get a geodatabase set up as soon as possible. Take a look and provide any comments if any come to mind. The list is somewhat stream of consciousness and may be missing a critical unit or may not reflect your conceptions. Let's work toward a consensus if needed.

Base map update and software of Interest....

The Owyhee River study area base map:

I am formally beginning the process of creating the map and have decided to develop the base map using All Topo Maps v7, a product of iGage software that provides a platform for developing clean and seamless maps using various USGS topographic map products at a range of scales. As soon as the map is generated, I will post a link to it (give me a week or two). The map will be in NAD83, UTM Zone 11 and will have an irregular shape to encompass the relevant map area...actually it will be an inverted 'L' shape given the planform of the river, and may involve two panels. The iGage software also interacts intelligently with GPS units, but doesn't do the handy active downloading of maps, landsat data, and DOQQs that the Topofusion software does.

Goodbye to endnote and procite?

You may also like to know about a very cool Firefox add-on for collecting and managing scientific citations and references of all sorts. This program can quickly and simply extract all relevant bibliographic information from online scientific literature databases (eg., GeoRef, Google Scholar) to store and to generate ref lists for publications. It takes about an hour to figure out. I have already used it in conjunction with UNR library resources to completely research a recent mapping proposal.

Here's a quote from the site (and a link):

'Zotero [zoh-TAIR-oh] is a free, easy-to-use Firefox extension to help you collect, manage, and cite your research sources. It lives right where you do your work — in the web browser itself'