
I could say i literally spent tens of kilometers after kilometers assembling detailed maps and from the experience, I made many observations that I made posts of. For many months, everyday I had to devote about four hours piecing together up close snapshots of many topographical maps and later google maps to create this blog. However, truth to tell, creating the maps was so nerve-wracking and I could not have done it all if I weren’t a bit of obsessive-compulsive in me. It was an epiphany! Since then i knew what i had to do, and God brought everything to pass easily and smoothly. What were the chances that i assemble a fault line map as a weird activity and suddenly find myself and my family at risk and unaware that a silent, deadly fault line ran directly under our house. Lo and behold, even after checking the work several times, i got the jolt of my life when i discovered my rented house was actually sitting on top of a fault line! Not long after, i evacuated and resided far from any faultline.Īt the time, i was probably one of the few (not that i know anyone else) who assembled a map of the fault line. Fancying what i could accomplish with technology and a 15 year old map, i put my competency at work and scanned images and assembled them on my desktop computer.

Instantly, sirens went off inside my head and took stock of the situation on what i had: Windows in my computer (DOS ruled PCs 15 years earlier), Adobe Photoshop, a powerful image scanner and, most of all, a coffee table book of tiled large maps of Metro Manila. i put away the map inside a cannister and rediscovered it 15 years later when i was going through my old stuff. In 1990, i got ahold of a photocopy of a tabloid size, black and white map when the former Phivolcs head, the late Ricardo Punongbayan gave an earthquake awareness seminar after the July 16 earthquake. But it was in 2005 when i assembled my first map.

Prior to 2010, i was emailing people Google maps with the fault trace. This blog was started in 2013 however, it actually began in 2010 but got corrupted and backups of the original helped to restart the present blog.
