|Geological Survey of Victoria|
|Earth Resources Policy and Programs : dbMap DATABASE DUMP|
To Search the dbMap database for a well, survey, or other keyword:- type the keyword into the search box, and then press the Search button. Usually, the fewer search words used, the better.
Please note that searches for data associated with a specific well should use the well name, and that the spaces, case, and hyphens are ignored in the database search. Each of the words in the text is logically AND-ed to create the result (For example, if the text search was "SNAPPER FIELD" then the word SNAPPER and also the word FIELD must both appear for the item to be considered a match).
Data associated with a specific survey should try to use the DEPARTMENT NAME for that survey in order to maximise the accuracy and completeness of results (for example, it would be best to use the department name "G01A" rather than the longer name of the survey "Northern Fields 3D"). In general text searches, you may have to use several synonyms in separate searches in order to get a complete listing of all of the data. This is because the data has been catalogued with the department name, but may not have been so rigourously catalogued with other names for the survey.
Examples of WELL text searches are (1) well name; (2) well alias; (3) geological formation name; (4) basin; (5) operator; (6) year of rig release; (7) onshore/offshore (for example, to find onshore Otway basin wells, select "WELL" and then type "otway onshore") (for example, to find Otway basin wells, select "WELL" and then type "otway") (for example, to find the Barracouta wells, select "WELL" and then type "BARracouta") (for example, to find the Barracouta-1 well, select "WELL" and then type "barracouta-1")
Examples of SRVY text searches are (1) department survey name; (2) survey alias; (3) basin; (4) operator; (5) oshore/offshore (for example, to find offshore Gippsland surveys, type "GIPPSLAND OFFSHORE") (for example, to find the G01A survey, type "G01A")
Examples of ASSETS (tapes, reports, maps, sections, logs etc) text searches are anything derived from the asset catalogue, including the barcode, name, type, subtype, description, remarks, media type, basin, well name, survey name, line name, borehole name, field name, keyword, and title name if these elements were populated for that item. (for example, to search for assets for the Snapper-5 well, type in "Snapper-5" as the search text) (for example, to search for assets (e.g cross sections) that have both Perch and Snapper, type "Perch Snapper" as the search text) (for example, to search for assets for the G01A Northern Fields 3D survey, type in "G01A" as the search text) (for example, to search for assets with the word "temperature" in their description, type in "temperature" as the search text) (for example, to find hardcopy WELL_LOGs that have GR, type in the two words "WELL_LOG GR") (for example, to find digital processed SEG-Y seismic trace data, type in the words "SEISMIC PROCESSED SEG-Y") (for example, to find digital processed SEG-Y seismic trace data for a given survey, type in the words "SEISMIC PROCESSED SEG-Y G03A" where G03A is the department name of that survey) (for example, to search for geochemistry related material, type in "geochem" as the search text) (for example, to search for biostratigraphic related material, type in "biostrat" as the search text) (for example, to search for palynology slides, type in "paly slide" as the search text) (for example, to search for palynology slides for Barracouta-1, type in "Barracouta-1 paly slide" as the search text)
Care should be taken to re-assure yourself that the database has been populated sufficiently well enough for your specific search purposes. This data entry effort has varied according to the type of data and the person entering it to some extent. The behaviour of this search mechanism is NOT THE SAME as a normal search engine! The words in the search text must ALL BE PRESENT to result in a match. Never forget that this is a very dumb and simple search mechanism! Because of the nature of the word search, usually more items will be reported than what strictly you might want to match your search string. For example, the search string "Angler-1" will match all of the following: "Angler-1", "Angler-1A", "ANGLER 1", "ANGLER1", "Angler 1A". The text matched will not necessarily be a word since much of the punctuation is ignored in the search. The use of search words such as "BREAM FIELD", which will create a list of things with both of the words "bream" and "field" will not necessary create a list of all of the data for that field, since many of the well information for the bream field wells will not have those specific two words. You may be better off trying just the word "Bream". Some search words will result in larger than expected number of results. For example, certain searchwords such as "Halibut" are the names of wells, but also the names of formations. Thus, a well search using the word "halibut" will bring up many wells. The number of results you get may be quite enormous. To limit the number of results, use the maximum number of lines to print parameter. This is defaulted at 1000. Doing searches on survey data, you should try to use the department name for that survey. If you do not know the department name of the survey, then first do an initial search according to the name that you know, then use the department name that you find. The Maximum Lines to print out in the result determines if all matching records are printed, or just a subset. The Search Type parameter determines whether to search ALL of the modules, or just one at a time. The search logic between words should normally be that the item matches both word1 AND word2. If you wish to change this search logic to match either word1 OR word2, then the Search logic type can be changed from AND to OR.
These HTML files can be copied onto a hard disk and accessed directly. For the image file linkages to work, the correct symbolic linkages may have to be created. For the text search to work, the correct Perl scripts and database text files must be copied into the correct CGI-BIN directory, and appropriate Apache web server software used.