This is a data interchange content model for a subsurface temperature measurement made in a borehole. Header content that characterizes the borehole sampling feature is included with each observation to assist users finding measurements based on location, depth, particular borehole, etc. This information will be provided through a borehole temperature observation service. The HeaderURI for a particular borehole (well for simple wells) is the cross-referencing link (foreign key) used to associate the header record, well logs, temperature measurements, and other information from a particular borehole.
The idea is that each record (feature) in an interchange document represents an individual observation. Thus there are multiple records if there are multiple observations in a single borehole, indexed by depth, procedure, time of observation properties. It’s a data access format, so this results in lots of duplication of the header/indexing information, but keeps life simpler for the client application. This becomes problematic in the continuum from single temperature measurements to a discrete log with measures every 100’ to a continuous temperature log; it’s sort of arbitrary when one switches from the individual temperature measure as being the observation to the ‘log view’ in which the series of measures is the observation result (currently represented as an excel spreadsheet or LAS file)—based mostly on what we think will be most useful to our customers.
The legend for the Borehole Temperatures model is a point-feature color ramp which ranges from green (=95F) to red (= 212F) for each feature.