Batch Geotagging STRATER PDF Log Files

In the STRATER Log Batch Production HOWTO I described how to produce a large number of PDF and JPG files as output of STRATER, and I vaguely promised to post a script that automates geo-tagging of the resulting JPG files.

With a combination of Adobe Acrobat and ARCInfo GIS it may be possible to convert technical drawings or PDF files to JPG files and georeference them. However, my intention was to achieve this with with low-cost software tools and utilities. Here it is.

Let us assume that STRATER has produced a folder full of log files in PDF format, and all files were named using A-PDF Rename according to the borehole names. It is highly likely that somewhere on your system there is a spreadsheet file that contains the borehole names and the coordinates. If they are already in decimal latitude/longitude format: great! If not, you should convert them.

To be able to use this script, you will need to install the following software packages:

At the time of writing of this script, all software except IrfanView (for professional purposes) was free of charge.

All directories of the executables mentioned above need to be in the PATH variable of your Windows system.

The script runs successfully on my Windows XP system, I have not checked for others. Please let me know if you got them to work on other systems as well, I will post it here.

The script expects a coordinate file with the name “coord.txt” in the working directory, which is a tab-delimited table with the colums

Name | Latitude | Longitude

The “Name” can be any format (I think), but I am not sure if it may contain spaces, so that part needs to be tested still. The script expects latitude and longitude to be provided in decimal degrees. There should be *no* header row in this file, it will be generated automatically during the batch process.

The script also expects all pdf files that are to be transformed in the same directory as the coordinate file.

The script itself should be in the same directory as the coordinate.txt and pdf files.

All else should run automatically.

Should there be any problems, send me a mail or comment in the blog.

This script is provided for free, as I have profited a lot of the GNU community, and I am happy to return something. Nevertheless, please be aware that I cannot spend too much effort with support as long as I am providing it for free.

I think some of the code may be less than optimal, so I am thankful for any optimisation of the script. Please feel free to comment.

Simply copy and paste the text below into a text editor and save as bgt.bat (bgt is for Batch Geo-Tagging) in the directory where the PDF files and the coordinate file  are stored.

To produce the Google Earth kml file, exiftool will need a kml.fmt file to define the kml output format. You can find an example here. You may need or want to edit it to adapt it to your needs. It needs to live in the same directory as the other files.

Then open the directory and double-click the bgt.bat file. A command prompt window will open and comment what is happening.

This script is under GNU General Public License or GPL (http://www.gnu.org/copyleft/gpl.html). However, any software used in this script is under its own and separate license, which may or may not be different from the GPL. Please make sure to comply with the respective licenses. I do not ask for a fee, and as it comes along under the GNU GPL, there is no warranty for this script, neither assuring that it is fit for your purpose, nor that it does not interfere with anything on your computer. The script is provided for free as in “free beer”, and may be modified and shared as long as the original source (i.e. this web site) and its copyright is mentioned.

—— Start of batch script ——

cls

echo off

echo This batch file was developed by Thorsten Kallnischkies and is under GNU General Public License or GPL (http://www.gnu.org/copyleft/gpl.html). However, any software used in this script is under its own and separate license, which may or may not be different from the GPL. Please make sure to comply with the respective licenses. There is no warranty for this script, neither assuring that it is fit for your purpose, nor that it does not interfere with anything on your computer, and if something breaks you can keep the pieces.

rem START /min mplay32 /play /close %windir%\media\ding.wav

pause

echo CONVERTING ORIGINAL PDF FILES TO JPG FILES

i_view32 .\*.pdf /invert /invert /convert=*.jpg /one /killmesoftly

echo SETTING UP JPG FILES FOR GEOTAGGING…

exiftool “-FileModifyDate>CreateDate” -overwrite_original .\*.jpg

exiftool “-CreateDate>DateTimeOriginal” -overwrite_original .\*.jpg

exiftool “-CreateDate>ModifyDate” -overwrite_original .\*.jpg

echo JPG FILE DATES ARE UPDATED, NOW PRODUCING A FILE WITH FILENAMES AND TIME STAMPS

exiftool .\*.jpg -FileName -CreateDate -T > borehole_date.txt

echo REMOVING “.JPG” FROM THE FILE NAMES IN THE FILE

gawk {gsub(/.jpg/,\”\”,$1);print} borehole_date.txt > borehole_date1.txt

echo REMOVING LEADING “+” AND “-” FROM UTC RELATED TIME STAMPS

gawk {gsub(/+/,\”,+\”,$5);print} borehole_date1.txt > borehole_date_2a.txt

gawk {gsub(/-/,\”,-\”,$5);print} borehole_date_2a.txt > borehole_date_2b.txt

echo REPLACING COLONS FOR SLASHES IN DATES

gawk {sub(/:/,\”/\”);print} borehole_date_2b.txt > borehole_date_3.txt

gawk {sub(/:/,\”/\”);print} borehole_date_3.txt > borehole_date_4.txt

echo PRODUCING GPX RAW DATA FILE

join coord.txt borehole_date_4.txt > gpx_raw_data.txt

gawk {print”$1″\”,\”"$2″\”,\”"$3″\”,\”"$4″\”,\”"$5″} gpx_raw_data.txt > gpx_raw_data.csv

rem echo CLEANING UP…

rem gmkdir .\config

rem mv coord.txt .\config

rem rm .\*.txt

echo CREATING HEADER FILE

echo name,lat,lon,date,time,utc > gpx_raw_file.csv

echo ADDING THE GPX RAW DATA

cat gpx_raw_data.csv >> gpx_raw_file.csv

echo GPX RAW DATA FILE PRODUCED

echo NOW CONVERTING RAW DATA TO GPX TRACK FILES…

gpsbabel -i unicsv -f gpx_raw_file.csv -o gdb -x transform,trk=wpt -F coord.gdb

gpsbabel -i gdb -f coord.gdb -o gpx -F coord.gpx

echo GPX TRACK FILES ARE PRODUCED, NOW GEOTAGGING THE JPG FILES…

exiftool -geotag coord.gpx  -overwrite_original .\*.jpg

exiftool “-CreateDate>FileModifyDate” -overwrite_original .\*.jpg

echo JPG FILES ARE GEOTAGGED

echo NOW PRODUCING SMALLER VERSIONS OF JPG FILES…

gmkdir .\jpg_small

gmkdir .\pdf

i_view32 .\*.jpg /resize=(800,800) /aspectratio /convert=.\jpg_small\*.jpg

rem THIS NEEDS TO BE EDITED MANUALLY IF THE “RESIZE” PARAMETER IS TO BE CHANGED.

echo SMALLER JPGS ARE SAVED

echo NOW PREPARING THE KML FILE IN DIRECTORY JPG_SMALL …

cp .\kml.fmt .\jpg_small

cd .\jpg_small

echo NOW PREPARING THE KML FILE FOR GOOGLE EARTH

exiftool -p .\kml.fmt .\*.jpg  > .\out.kml

cd ..

echo ALL DONE, NOW CLEANING UP, PLEASE BE PATIENT…

gmkdir .\jpg_original

gmkdir .\config

mv .\*.jpg .\jpg_original

mv .\*.pdf .\pdf

mv .\*.g** .\config

mv .\coord.txt .\config

mv .\kml.fmt .\config

rm .\*.csv

rm .\*.txt

echo CLEANING UP IS COMPLETE, NOW SAVING README.TXT FILE WITH FILE INFORMATION…

echo All pdf files formerly in this directory should have been converted into jpg format and georeferenced, reduced in size and transformed into a Google Earth readable kml file. Please check the results: >> .\readme.txt

echo ———————————– >> .\readme.txt

echo These files are the original PDF files, which have been moved to the subdirectory PDF: >> .\readme.txt

ls -al .\pdf >> .\readme.txt

echo ———————————– >> .\readme.txt

echo These files have been produced, georeferenced and moved to the subdirectory JPG_ORIGINAL: >> .\readme.txt

echo – >> .\readme.txt

ls -al .\jpg_original >> .\readme.txt

echo ———————————– >> .\readme.txt

echo These files have been reduced in size, georeferenced, converted into a Google Earth kml file, >> .\readme.txt

echo and moved to the subdirectory JPEG_SMALL: >> .\readme.txt

echo – >> .\readme.txt

ls -al .\jpg_small >> .\readme.txt

echo ———————————– >> .\readme.txt

echo The GPS files and the original coordinate file have been moved to the CONFIG directory. >> .\readme.txt

echo – >> .\readme.txt

ls -al .\config >> .\readme.txt

rem START /min mplay32 /play /close %windir%\media\tada.wav

echo DONE!

echo

echo PLEASE READ THE README.TXT FILE AND CHECK YOUR FILE DATA

echo HIT ANY KEY TO EXIT.

pause

—— End of batch script ——

You can now check the coordinates in the EXIF data with Exiftool GUI, simply load all JPGs into it and flick through the files to check. If something is not working, let me know and I will try to assist you.

This batch file should run on any PDF/JPG files with an associated coordinate file, such as technical drawings of all kinds from a CAD system, etc.

I am looking at translating the script to Linux, but as IRFANView is used for PDF to JPG conversion here and does not run under Linux, I need to look deeper into the GhostScript parameters to get that done first. May take a while and does not look that urgent, as STRATER runs under Windows as well, which was the starting point of it all…

Enjoy!

Posted in Contamination Mapping, Geology, GIS, Google Earth, Google Maps, Software | Leave a comment

STRATER 2 Log Batch PDF Production HOWTO (updated)

This Howto was written when  Golden Software’s STRATER 2 was still around, a very clever software to transform raw borehole data into customised borehole and well construction logs. It describes how to produce a large number of STRATER logs as separate PDF files, and rename them according to fields (e.g. borehole ID) in the PDF file.

As STRATER runs under Microsoft Windows, the whole procedure is designed for application under MS Windows. The process is designed using free or low-cost software to enable small businesses to follow the steps with little financial effort. STRATER is able to batch print hundreds of logs as hard-copies. And yet, if you want to produce single PDF files instead of paper prints, you run into two walls.

In STRATER 2, you used to have the option to save one log at a time in PDF format and you need to name it individually. STRATER 2 insisted in issuing one hard copy print job per log, and in the same way it insisted in saving logs as single PDFs. The ‘File –> Export’ menu option also only exports single logs as PDF files, as each PDF is saved with the same name insthe but will end up with the last log being the only file saved.

UPDATE: According to Kari Dickenson from Golden Software on their STRATER blog page “Print Multiple Logs to PDF with Hole ID as filename” dating February 14, 2012, STRATER 3 now is now able to export multiple logs to a single PDF file, i.e. all pages of all logs will go into one PDF. This is great news for the user community. On the other hand I understand that there is still need for the workaround if you need single PDF files and want the borehole name as the file name. Maybe we should ask Kari to put this on the wish list for future releases of STRATER.

Anyway, this is all not a problem if you are coping with five or ten borehole logs. In this case it will take you ten or fifteen minutes to save the single PDFs and rename them according to the borehole IDs and you are done. I had quite a different challenge, as during the UNEP Ogoniland Environmental Assessment our eight drilling teams had drilled some 800 boreholes for soil sampling and another three teams had drilled 180 groundwater monitoring wells.

Now if that would have been all, I would have sorted it in a few hours. But I wanted more: What if we had JPG files of the logs, named accordingly? And what if you wanted to import them into a GIS system, or into Google Earth? But then you would like to see the logs in their correct position, wouldn’t you? Yes, then we need to geo-tag the logs’ JPG files.

So the process was clear:

  1. Batch print 980 logs from STRATER 2 as single and separate PDF files,
  2. Rename 980 PDF files according to their Borehole ID,
  3. Convert 980 PDF files into JPG files,
  4. Geo-tag 980 JPG files,
  5. Create a KML file for import into Google Earth, showing previews and large images of the 980 logs.

This process was impossible to handle manually for 980 logs. Calculating eight minutes for the manual process, it would have taken more than three weeks of uninterrupted log processing to complete the task.

It took me a few hours to figure out how STRATER handles the batch print, how the PDF printer installed by Adobe Acrobat 9 handles the printing process, and how to find a workaround.

Golden Software say that STRATER is working flawlessly, it is not their problem what the installed printer does with STRATER’s output and batch ‘printing’ of PDF logs does not result in what I and others might need, and I have no reason to doubt that.

Adobe say that their Acrobat 9 installed PDF ‘printer’ is working flawlessly, and that it is not their problem that the software piping data into the printer produces one ‘print’ command for 980 logs but does not manage to change the name of the file 979 times. And I do not doubt that, either.

If you batch print 980 logs consecutively into separate PDF files, and the file name does not change, you will end up with one PDF file showing only the last log, because the same file has been overwritten 979 times if you suppress the overwrite error of the PDF printer. Or a window pops up and wants you to accept the overwrite process or save as new file 979 times. I found both options unacceptable and looked for a PDF printer that was able to save the PDF file produced automatically and with an individual file name.

I ended up testing various products such as CutePDF, FreePDF, dopdf, Bullzip PDF, amongst others. I personally found Bullzip PDF Printer most convenient, as it enables the user to set a flexible file name with a few mouse-clicks, and print hundreds of logs without any further action. FreePDF appears to be as configurable with FreePDF_Multidoc, although I was unable to check this application in depth. Both FreePDF and FreePDF_Multidoc are in German.

Bullzip is in English, and I ended up using it. When I looked last, the license said ‘free for personal and commercial use up to 10 users’.

Bullzip PDF Printer will produce 3-5 logs per minute, and when configured with <date>-<time> in the file name, each STRATER log will be printed separately. You should not configure it to overwrite or append the PDF to existing files if you want to process the PDFs further, e.g. rename them with the borehole ID or convert them to JPG for georeferencing.

Also, the Bullzip options ‘Open destination folder after creation’ and ‘Open document after creation’ should be deactivated, otherwise Bullzip will open one file manager and/or one Acrobat Reader (or Adobe Acrobat Standard) window after creation of each file, which will clutter up your screen if you have to print a few hundred files.

After printing, you will have a folder full of files which are named something like 2011-01-19_16-41-51.pdf, the filename being in YYYY-MM-DD_hh-mm-ss.pdf format. We are already half-way there.

Now to rename 980 PDF files manually is a challenge, and quite boring. I had done that after the first batch run, which took me more than ten hours, and in doing so I noticed that my basic STRATER data were flawed. Mainly because of misspellings of the borehole IDs in the STRATER database, there were about 120 named log sheets without lithology and/or well construction logs, and there were about the same number of unnamed lithology and/or well construction log sheets.

So, check and correct the database, PDF print again, and: think again: rename again??? Yes, rename again, but definitely not by hand this time! I had asked an IT programmer if he were willing to write me a piece of software to extract the borehole ID, but he found it too boring and refused. After some searching on the net I found what I was looking for: A-PDF Rename. A-PDF Rename was an epiphany for me, as it provides exactly what I was looking for: rename a PDF document by a text read from the actual PDF document. In this case: the borehole ID.

The renaming process is as follows:

  1. Start A-PDF Rename
  2. Go to (1) Add PDF Documents. Add PDF logs by hitting the “Add File” or “Add Folder” button. It may take a while if you have several hundred log files.
  3. Go to (2) Rename Method. Hit the “Macro” button –> click “Content Tag! at the bottom of the context menu.
  4. The window will show you one of your PDF documents.
  5. Find the position of the borehole name.
  6. Click it, and from the context menu chose “get content by position” or “get content by keyword”, as applicable to your borehole names. I chose mine by position.
  7. Change Tag Name, Position Deviation etc. to your requirements, e.g. “borehole_name”.
  8. Hit the “save” button, which returns you to the first window.
  9. Hit the “Macro” butto again, and “%Content_borehole_name%” has been added to the bottom of the context menu.
  10. Click it, and “%Content_borehole_name%” will be added to the “Rename Filename” slot.
  11. Do not (!) select the ‘Modify Metadata’ option, as the metadata are essential for PDF to JPG conversion and JPG geo-tagging.
  12. It will be added to the file name, not overwrite it, so you need to delete the “%filename%” bit at the beginning of the line.
  13. Go to (3) and chose “Preview” or “Preview and Rename”.
  14. Depending on the number of PDF logs you have, you can now get yourself a cup of coffee now, go for lunch, or even go home for the night and return to work next morning.

If you have several hundred PDF files, even renaming with A-PDF Rename may take several hours and depending on processor(s) and RAM also may slow down your computer significantly. In any case, a lot better than manual renaming.

Initially it had taken me a 10-hour day to manually rename (open PDF document, select borehole ID, hit Ctrl-C (copy), Ctrl-W (close PDF document), rename file in file manager, open next file) 1,100 PDF files with Adobe Acrobat 9. A-PDF Rename needs five minutes of batch process configuration, and does the rest by itself. For me, A-PDF Rename achieved a recognition rate of about 98%, so I had to rename a few files manually. I am not sure whether the 2% of unrecognised borehole IDs were caused by the BullZip printing software, or the A-PDF Rename software, or if it was a flaw in my STRATER setup. In any case, the gap between STRATER 2 and 980 neatly named PDF files was now closed by 98%, and I was really happy with the results.

 

The A-PDF Rename trial version is restricted, if you are going to use the software permanently, make sure you buy a license (27 US$ at the time of writing). A-PDF’s service is very good: I had a slight problem with installing it, and they helped me fix it within two hours. Thank you very much to Alice, and keep up the good work, lasses and lads!

In the end, the whole directory will be full of files that are now named something like 001-002-03.pdf, or whatever the borehole ID is. If your client is happy with named borehole logs in PDF format, compress the folder and send him a mail where he can download it and this is the end of the production chain.

Or is it? Or do we want our client to have some goodies?

How about integrating the odd borehole log in the final project report? We will need images in JPG format to achieve that, as our word processing software does not import PDFs.

Enter IrfanView. I am sure there are more programmes around that do the same as IrfanView does, but I happened to have it on my computer anyway, and I was always happy so never looked again. IrfanView batch converts PDF to JPG if you have the addons installed. When searching for the PDF import format, you will find the PDF file type in the

‘Files –> Open –> Files of Type –> EPS/PS/PDF/AI-PostScript’

menu. When converting JPG, make sure to have a good look at the Options and the Advanced Options. It takes less than five minutes to configure the batch process, and the computer works on several hundred files in a few hours without user intervention.

IrfanView is a really clever piece of software, and it is critical for this process. IrfanView is free as in ‚free beer‘, and in addition Irfan is very quick and competent if you have a question. Good guy, well done! I think it would be really fair to honour his achievement and contribution to this process by paying him the 10 Euros he is asking for professional use. He actually should be selling IrfanView for 100 Euros per license. Yes, it is that good.

If you need to install IrfanView on your computer, make sure you have the 32 bit Ghostscript version installed for Irfanview to use, as IrfanView itself cannot handle 64 bit Ghostscript and comes up with an error message when converting PDF to JPG.

Now the client can put the logs on his web page, in his report, etc.

Our GIS expert had developed a web mapping application for the project, and I was curious enough to get the last step done to upload the logs to the GIS and have them show up in the correct place.

The process of getting the coordinates from a spreadsheet into the EXIF part of the log files JPG images is rather technical, and if you don’t know what EXIF means, the details would bore you into oblivion anyway. Just this much: to achieve the last steps, you will need to install exiftool, GNU Win Tools for MS Windows, and GNU gawk. Thanks to Martin Buitelaar, for turning me in the right direction with exiftool!

The next steps involve entering manual commands with cryptic options on the command line. I managed to condense the command line input into a batch script that handles the whole part from the conversion of PDF files into JPEG to geo-tagging the images and putting them into a Google Earth kml file. The best thing about it is that once started it does not require any manual input or other human intervention, and it can run overnight and unattended.

In the end I reduced a process that would have taken more than 130 person working hours (or more than 16 working days) if done manually, to one printing process, one renaming process, and one computerised overnight batch run, all of this requiring a total of one hour of human attention and maybe 12 hours of computer time, using software for less than 40US$.

You can now find the Howto and script here.

During the whole process, I have learnt a lot about the software, and would like to thank all the software developers involved. You all did a brilliant job, without your work this would not have been possible. I am a dwarf standing on the shoulders of giants.

Example for a STRATER Borehole and Well Construction Log

 

Posted in Contamination Mapping, Geology, GIS, Google Maps, Ogoniland, Software | 1 Comment

Niger Delta and Oil Contamination in Ogoniland (1)

During the past days, several news articles have covered the case of the community of Ogale in Eleme community, Eleme LGA in Rivers State, Nigeria. The community filed their case to a US District Court in Detroit on Tuesday, October 18, demanding to sentence Shell to a payment of 1 billion US$ in damages for years of environmental pollution, gross negligence and emotional distress.

The allegations are based on benzene concentrations in drinking water wells in the community, and in groundwater monitoring wells installed during the 2010 UNEP investigations. During the UNEP investigations, benzene concentrations in a private drinking water well exceeded international standards by a factor of 900.

What strikes me is that apparently no one cares to actually read the UNEP report on the investigations in Ogoniland. Pages 127 ff. describe the spill in Nsisioken Agbi Ogale community. The source that was identified is a pipeline transporting refined product (gasoline, diesel, kerosene), operated by the Nigerian National Petroleum Corporation (NNPC) and not Shell.

Irrespectively of the role of Shell in the Niger Delta and especially in Ogoniland, it looks to me as if like everyone is flogging the wrong horse. It remains to be seen if anyone involved in the court case is actually interested to take notice of the data and resulting facts, which are freely available from UNEP.

Recommended reading (external link, opens in new window)

Addendum from November 22, 2011: Someone actually has read the UNEP report and has drawn consequences.

Posted in Assessment, Contamination, Groundwater, Niger Delta, Ogoniland | Leave a comment

Project Phases

Ideally, projects follow the five phases of the Project Management Body of Knowledge (PMBOK):

  1. Initiation
  2. Planning
  3. Execution
  4. Monitoring
  5. Closing

But now and then, projects go wrong. Then something is created which I call The Notorious Project Cycle of Death. And in this case, the nine project phases are:

  1. Birth of a Brilliant Project Idea
  2. Meetings to formulate Project Policies
  3. Acceleration to Maximum Enthusiastic Momentum
  4. Creative Disorientation and Random Activism
  5. Reality Shock and Last Minute Leadership
  6. Determination of the Guilty and Punishment of the Innocent
  7. Promotion of the Idle and Uninvolved
  8. Final Workshop on Self-Praise and Avoidance of Lessons Learnt
  9. Donning of the Cloak of Silence and Merciful Oblivion

View an example for project implementation.

Posted in Project Management | Leave a comment

Hydrogeological Triangles

Especially in industrial demolition or decontamination projects it is sometimes necessary to assess the groundwater situation, especially when neighbouring housing estates or critical infrastructure such as water works might be affected by groundwater contamination. It is common knowledge that monitoring wells are being drilled to take groundwater samples. But frequently the necessity to determine the groundwater flow direction properly is underestimated. In the past I have seen colleagues work out monitoring plans that were not suitable to determine the groundwater flow direction, which is critical when assessing the exposure of receptors to a contamination source.

The potential impact of a contamination is determined by figuring out the source (S) – pathway (P) – receptor (R) constellation. The hazard (H) can be determined in simplified terms as

S * P * R = H

Like in a simple multiplication, if one factor is zero, the result (hazard) is zero. If there is no contamination, there is no hazard. If a contamination is detected but no pathway (e.g. aquifer protected by an impermeable clay layer) to a receptor (e.g. waterworks or private wells), no hazard can be stated. If there is a contamination source and the groundwater is affected, but no receptor (e.g. groundwater wells) present, again there is no hazard.

Of course, this is the simplified explanation. There are always several potential transfer pathways, and potential receptors, so for each possible pathway and receptor the hazard potential needs to be assessed separately. If I find the time, I will write something more detailed about the source – pathway – receptor approach later.

This article is about the basic method to determine groundwater flow directions, and the following examples are from projects I have come across during my work in groundwater assessments in the past years:

Case 1: For a groundwater assessment five wells were properly drilled and documented with drilling and well construction logs. The height of the wells above ground surface was also determined, as was the depth of the water table below the well pipes’ upper end, and the water table below ground surface was calculated. What was omitted.was to determine the height of the well pipes above mean sea level (msl), or at least the relative heights of the monitoring wells to each other.

Without knowledge of the wells’ (relative) heights, the groundwater flow direction cannot be determined, the groundwater isoheight lines (or hydroisohypses) will form a completely random pattern, especially in areas with distinct morphology, or shallow groundwater dip.

If groundwater wells are drilled, it is paramount to call in a surveyor team to determine the wells’ heights. These teams usually cause additional costs of a few hundred US$, but for a scientifically sound analysis their data are critical.

Case 2: For a groundwater monitoring in a contaminated area, three monitoring wells were drilled, upon completion the groundwater level was determined, and a few days later the survey team determined the wells heights and coordinates.

Nevertheless, the hydroisohypses did not make any sense, as the groundwater seemed to disappear in a plug hole like in a bathtub. After checking the water levels that were measured during the groundwater sampling campaign a week after well drilling, it turned out that the data used for the groundwater table depth did not represent the real groundwater table.

Due to high silt and clay content in the soil, the water permeability was very low, and the water table in some of the wells had reached equilibrium only several days after well installation.

Case 3: For the investigation of a waste dump site, three wells were drilled in a row between the waste dump site and a housing estate, to determine the potential impact of the waste dump on the household water wells as shown in Example A. The height of the wells was determined by a surveyor team.

Three monitoring wells in a row

Three monitoring wells in a row

The groundwater flow direction can be determined easily, as the groundwater flow is always perpendicular to the hydroisohypses, which are calculated by interpolation between the groundwater levels in the wells and the distance between the wells.

As can be seen in Example A (from real life), e.g. the 12.00 m isohypse crosses the imaginary line between Monitoring Well 2 (11.95 m msl) and Monitoring Well 3 (12.05 m msl) at half their distance.

Example A shows that with the wells in one row, it is not possible to determine the hydroisohypses and flow direction, as there is an infinite number of possible ways to position them. For the same reason, the groundwater flow direction cannot be determined, it may be directed away from the housing estate (blue arrow) or towards the housing estate (red arrow). A proper assessment of the source – pathway – receptor situation in this case was not possible.

Hydrogeological triangle

Example B shows the same situation, but in a theoretical setup  with the three monitoring wells positioned in a so-called hydrogeological triangle. Now the hydroisohypses can be interpolated unambiguously, as can the groundwater flow direction (blue arrow).

It is suitable to install three or four groundwater wells for a first assessment in a first step. If contamination can be verified, (a) further drilling campaign(s) can be necessary to determine the contaminant distribution in the groundwater. In areas with seasonal rainfall, it is also necessary to carry out a monitoring, i.e. repeated sampling campaigns during the dryer season and during the wet season. Seasonal changes of the groundwater table may cause variations in groundwater flow and contaminant transport directions, which may impact on receptors previously unaffected.

Isohypse interpolation with three or four groundwater wells can be accomplished manually with a CAD system. For larger arrays of wells and in monitoring campaigns usually specialised plugins of geo-information systems or dedicated software such as SURFER is used. This method, although computerised, does not just consist of importing spreadsheets and pushing buttons, but requires some experience to ensure the maps actually make sense. At some later time, I may write some more about QA/QC of contamination maps.

Posted in Contamination Mapping, Groundwater, Hydrogeology | Leave a comment

Ship Breaking

Hardly anybody working in the international decontamination industry has not heard or read about the ship breaking industry of India, Bangladesh and Pakistan, but also Turkey and China. The latest issues hitting the news were

Roughly at the same time, the Tenth Meeting of the Conference of the Parties to the Basel Convention (COP10) was held in Cartagena, Colombia (October 17-21, 2011). One of the issues to be discussed was the Global Programme for Sustainable Ship Recycling, with the objective to improve environmental and occupational health and safety (OHS) standards in ship breaking yards in South Asia.

While in Europe ISO Standards (ISO 30000 ff.) define sound environmental procedures for the recycling of end-of-life ships, ship breaking has become a major source of hazardous wastes in southern Asian countries. At the same time it has become increasingly attractive for ship owners, as environmental standards and their enforcement are poor, and labour costs are low.
Hazardous wastes present in end-of-life ships consist of

  • used oil and waste oil, oily sludge;
  • asbestos, mineral wool, and other insulating materials;
  • coatings and paints containing tributyltin;
  • batteries (lead and sulphuric acid);
  • electronic waste;
  • PVC-coated cables;
  • CFC refrigerants;
  • etc.

A study financed by the EU, which was published in 2007, estimates that between 2007and 2020 a total of >100 million LDT (Light Displacement Tonnage) will be scrapped. Taking into account that the average selling price for a ship varies between 100 and 200 US$/LDT, and can be as high as 500 US$/LDT, we are talking about a market of something north of 10,000,000,000 US$ at current minimum prices. A ship scrapped in Europe will cost upwards of 150 US$/LDT, plus the cost of hazardous waste removal.

Even if we were talking about costs of only 5 US$/LDT for the proper removal, treatment and disposal of hazardous waste, the difference in costs between scrapping in the EU and ship breaking in India or Pakistan would make a difference of 500 million US$. Nowadays, it is still easy to flag out a ship to avoid the costly recycling in Europe. On the other hand, the price of today’s ship breaking in southern Asia is massive environmental degradation as well as workers’ deaths and injuries due to lack in occupational health and safety.

http://www.youtube.com/watch?v=fxUGONR9pQw

Where Ships and Workers Go to Die by Institute for Global Labour and Human Rights

Posted in Contamination, Hazardous Waste, Shipbreaking | Leave a comment

On Geologists

Some people think that geologists are weird hammer-wielding scientists smashing rocks in strange places. They are actually wrong, because not all geologists smash rocks for a living . Which also often leads to the question “So what does a geologist do in a soil remediation / demolition / waste removal project?”. The answer is that for a geologist it does not matter if

  • oil in the soil is millions of years old and found in 5 km depth, or if kerosene from a former Red Army airfield storage tank site is sitting on the groundwater 5 m below ground surface;
  • a pile of rubble results from bombing, or from the impact of a demolition ball, or comes rushing down the face of a mountain, or is produced in a quarry as construction material;
  • copper is quarried from a vein in a mountain, or is separated from a pile of electronic waste.

A geology student at university will be trained to evaluate ore deposits, by doing the field work, sampling, documentation, calculations, mapping etc. As not any two ore deposits are identical, a geologist will have learnt to be flexible in his approach, and will have a sound understanding of the general environmental setup.

One of the prejudices about geologists frequently expressed is that geologists are not good with numbers. That is actually not true. The truth is that it is hard to impress a geologist with large figures. 4.5 billion years? Yes, fine. Oldest fossil? Dunno, maybe 2.8 billion years, give or take a few hundred million. Remediation of oil spills in Ogoniland will cost 100 million US$? Well, maybe ten or fifty million more, but not likely less.

Geologists who decide to work in project management and project controlling (like me) need to go into the small figures, to check if items on invoices are identical with services delivered or units deposited. For example: a two-day detailed check of 600 weighing cards of a waste contractor may reveal that 120,000 Euros are disputable, and in the end saves the client 50,000 Euros.

Nevertheless, I do love the scientific part of my work, sometimes it even feels like Crime Scene Investigation (CSI) work.

I have talked to an analytical chemist some years ago, and she told me that although she knew all the chemical reactions I was writing about in my report, but for her any given chemical reaction would take place under controlled conditions in laboratory test tubes with exact knowledge of temperature, pH etc. so she could calculate the reactions and products exactly. It remained unclear to her how I worked out the hazard potential in the great outdoors.

Discussing contaminant pathways and impacts on mangroves with a marine biologist, he was surprised that I had a good understanding of the impact of crude oil on the brackish and marine ecosystems. Although I was never a big fan of palaeontology lectures at university, I felt that my palaeontology professor was right by insisting we learn everything about the dead animals we were studying. Which included not only the name in German and Latin but also what the juvenile and adult forms look like, their habitats, diet, predators, ancestors and descendants, worldwide and from the primordial soup some billion years ago till the end of the last ice age.

Now that my job brings me round the world and puts me in contact with nice and interesting people, as well as challenging projects, I must admit I am really happy I am a geologist.

Posted in Contamination, Geology | Leave a comment