Changes

==The database==

==The database==

Data to the development geologist means many things. First, it means well data, including, but not limited to, well locations, header information (such as operator, year, total depth, status, elevation, and API gravity), deviation surveys, formation tops, fault cuts, results of drill stem tests and production tests, core data, and a host of calculated values such as isochore, true vertical depth, true stratigraphic thickness, and so on. Equal in importance is log information, including curves or traces, logging parameters such as mud type and resistivity, and analysis parameters such as formation water resistivity or cementation and saturation exponents. In some projects, surface geology is of great importance, consisting of bed attitudes and surface expression of contacts and faults. Seismic data can be critical, including time cross sections with interpreted horizons that need to be tied to the well control using an accurate interval velocity model. The geologist may also deal with periodic or cumulative production data by well, lease, or field. Also, the interpretation process generates new data elements, including zone average [[porosity]], net pay, and hydrocarbon pore feet.

Data to the development geologist means many things. First, it means well data, including, but not limited to, well locations, header information (such as operator, year, total depth, status, elevation, and API gravity), deviation surveys, formation tops, fault cuts, results of drill stem tests and production tests, core data, and a host of calculated values such as isochore, true vertical depth, true stratigraphic thickness, and so on. Equal in importance is log information, including curves or traces, logging parameters such as mud type and resistivity, and analysis parameters such as formation water resistivity or cementation and saturation exponents. In some projects, surface geology is of great importance, consisting of bed attitudes and surface expression of contacts and faults. Seismic data can be critical, including time cross sections with interpreted horizons that need to be tied to the well control using an accurate interval velocity model. The geologist may also deal with periodic or cumulative production data by well, lease, or field. Also, the interpretation process generates new data elements, including zone average [[porosity]], net pay, and [[hydrocarbon]] pore feet.

These data types are stored in some form of a database, which can range from a simple spreadsheet or application-specific custom files to powerful relational database management systems. The data are entered into the database by one of four methods: (1) direct keyboard entry of text or numerical values; (2) digitizing from a map, seismic section, or log print; (3) extracting or downloading from another computer system followed by reformatting (if necessary) and direct entry as digital data; or (4) as derived or computed data stored back into the database by an application program. The more powerful databases provide utilities for search and retrieval, sorting, reporting and statistical analysis, and interfaces into applications.

These data types are stored in some form of a database, which can range from a simple spreadsheet or application-specific custom files to powerful relational database management systems. The data are entered into the database by one of four methods: (1) direct keyboard entry of text or numerical values; (2) digitizing from a map, seismic section, or log print; (3) extracting or downloading from another computer system followed by reformatting (if necessary) and direct entry as digital data; or (4) as derived or computed data stored back into the database by an application program. The more powerful databases provide utilities for search and retrieval, sorting, reporting and statistical analysis, and interfaces into applications.

A ''menu-driven system'' presents the user with a series of menus containing choices that can be made at that step and often have “context-sensitive” help available to further define each choice if needed. Menu systems are much easier to learn, but they can become cumbersome as the user becomes more proficient. Sometimes the best of both systems is available by the provision for native commands that can bypass wordy menus and add flexibility for the experienced user.

A ''menu-driven system'' presents the user with a series of menus containing choices that can be made at that step and often have “context-sensitive” help available to further define each choice if needed. Menu systems are much easier to learn, but they can become cumbersome as the user becomes more proficient. Sometimes the best of both systems is available by the provision for native commands that can bypass wordy menus and add flexibility for the experienced user.

An enhancement to the menu approach is the graphical user interface, which combines text menus with graphical objects or icons to represent choices. Inherent with this method is consistency of design, so that the same type of function, such as editing, is always presented in the same place and the same way in all applications using the interface. These applications are also designed to share data, both text and graphics, among themselves. Also featured are standard methods for moving about within the data using scroll bars and consistent keyboard commands. Because of the graphical approach, even text-oriented applications such word processing present a what-you-see-is-what-you-get (WYSIWYG) display, incorporating font selections, character sizes, and even integrated graphics such as symbols and pictures.

An enhancement to the menu approach is the graphical user interface, which combines text menus with graphical objects or icons to represent choices. Inherent with this method is consistency of design, so that the same type of function, such as editing, is always presented in the same place and the same way in all applications using the interface. These applications are also designed to share data, both text and graphics, among themselves. Also featured are standard methods for moving about within the data using scroll bars and consistent keyboard commands. Because of the graphical approach, even text-oriented applications such word processing present a [[what-you-see-is-what-you-get]] (WYSIWYG) display, incorporating font selections, character sizes, and even integrated graphics such as symbols and pictures.

The previous discussion has essentially described the evolution of user interfaces from primitive to modern, and it appears that all applications are moving toward incorporation of a standard graphical user interface in the future. Another desirable feature usually provided by these systems is ''multitasking'', which is the ability to do more than one thing at one time, with each process resident in its own window that can be arranged on the screen like papers on a desktop. Coupled with standardized data sharing, these systems go a long way toward achieving the integration goals described previously.

The previous discussion has essentially described the evolution of user interfaces from primitive to modern, and it appears that all applications are moving toward incorporation of a standard graphical user interface in the future. Another desirable feature usually provided by these systems is ''multitasking'', which is the ability to do more than one thing at one time, with each process resident in its own window that can be arranged on the screen like papers on a desktop. Coupled with standardized data sharing, these systems go a long way toward achieving the integration goals described previously.

|}

|}

The AAPG Computer Applications Committee has proposed the AAPG-B data exchange format for general purpose data transfers among computer systems, applications software, and companies.<ref name=pt08r24>Waller, H. O., Guinn, D., Nerkommer, M., Shaw, B., 1990, AAPG-B—committee offers revised exchange format for transferring geologic and petroleum data: Geobyte, v. 5, n. 2, p. 11–21.</ref> For log curves, the Schlumberger LIS (log information standard) has become a de facto standard, and extensions to it have been proposed.<ref name=pt08r8>Froman, N. L., 1989, DLIS—API Digital Log Interchange Standard: The Log Analyst, v. 30, n. 5, p. 390–394.</ref> Another log data format called LAS, for log ASCII standard, has been proposed by the Canadian Well Logging Society,<ref name=pt08r20>Struyk, C., Bishop, R., Fortune, D., Foster, E., Gordon, D., d'Haene, T., Joyce, D., Kenny, S., Kowalchuk, H., Stadnyk, M., 1990, LAS—a floppy disk standard for log data: Geobyte, v. 5, n. 2, p. 23–29.</ref> which may supplant LIS. The Society of Exploration Geophysicists oversees several standards for seismic data formats, the most common being SEGY for seismic trace data and SEGP1 for location data. A de facto standard for offshore shotpoint location (also called navigation) data is the UKOOA format, from the United Kingdom Offshore Operators Association. A format for transferring wellsite data called WITS, for wellsite information transfer standard, has been proposed by the International Association of Drilling Contractors (IADC).<ref name=pt08r18>Rose, R. J., Taylor, M. R., Jantzen, R. E., 1989, Information transfer standards for well-site data: Geobyte, v. 4, n. 2, p. 9–13.</ref>

The AAPG Computer Applications Committee has proposed the AAPG-B data exchange format for general purpose data transfers among computer systems, applications software, and companies.<ref name=pt08r24>Waller, H. O., Guinn, D., Nerkommer, M., Shaw, B., 1990, AAPG-B—committee offers revised exchange format for transferring geologic and petroleum data: Geobyte, v. 5, n. 2, p. 11–21.</ref> For log curves, the Schlumberger LIS (log information standard) has become a de facto standard, and extensions to it have been proposed.<ref name=pt08r8>Froman, N. L., 1989, DLIS—API Digital Log Interchange Standard: The Log Analyst, v. 30, n. 5, p. 390–394.</ref> Another log data format called LAS, for log ASCII standard, has been proposed by the Canadian Well Logging Society,<ref name=pt08r20>Struyk, C., Bishop, R., Fortune, D., Foster, E., Gordon, D., d'Haene, T., Joyce, D., Kenny, S., Kowalchuk, H., Stadnyk, M., 1990, LAS—a floppy disk standard for log data: Geobyte, v. 5, n. 2, p. 23–29.</ref> which may supplant LIS. The [[seg.org|Society of Exploration Geophysicists]] oversees several standards for seismic data formats, the most common being SEGY for seismic trace data and SEGP1 for location data. A de facto standard for offshore shotpoint location (also called navigation) data is the UKOOA format, from the United Kingdom Offshore Operators Association. A format for transferring wellsite data called WITS, for wellsite information transfer standard, has been proposed by the International Association of Drilling Contractors (IADC).<ref name=pt08r18>Rose, R. J., Taylor, M. R., Jantzen, R. E., 1989, Information transfer standards for well-site data: Geobyte, v. 4, n. 2, p. 9–13.</ref>

While database standards are still evolving, most users prefer a full function relational database management system (RDBMS). A standard query language, called SQL for Structured Query Language, is receiving acceptance from all quarters. Several commercial database products are available that support SQL. It thus becomes unimportant which product is used since applications can interact with the database via this standard interface. Direct retrievals from the database are available to users who learn SQL, but because many users do not wish to learn a command language, other products are available that build SQL statements from “fill-in-the-blanks” forms or example prompts. Some of these operate within a graphical user interface, letting users point and click their selections with a mouse. Most of the commercial databases offer or plan to offer a distributed database method, in which the actual database spans numerous computers in a network. The user will be able to store and access local data locally, yet still access other needed data from halfway around the world and not be concerned with the difference.

While database standards are still evolving, most users prefer a full function relational database management system (RDBMS). A standard query language, called SQL for Structured Query Language, is receiving acceptance from all quarters. Several commercial database products are available that support SQL. It thus becomes unimportant which product is used since applications can interact with the database via this standard interface. Direct retrievals from the database are available to users who learn SQL, but because many users do not wish to learn a command language, other products are available that build SQL statements from “fill-in-the-blanks” forms or example prompts. Some of these operate within a graphical user interface, letting users point and click their selections with a mouse. Most of the commercial databases offer or plan to offer a distributed database method, in which the actual database spans numerous computers in a network. The user will be able to store and access local data locally, yet still access other needed data from halfway around the world and not be concerned with the difference.