Stupidity at Work
Today I was going through a bunch of new jobs (mostly new developments) to be inputted into GIS. As I was going through them, I found two sewer pump stations that were way too advanced, a couple of water main renewals that had already been done and some other random bits and pieces. And then there were three more that I had to put on hold because the prerequisite data are not on the system yet. Two hours later, I managed to find something that I could input. So I was happily importing files until I encountered an error in the GIS software, which I didn’t know how to solve. I sought help from the person who sat next to me and he inspected the raw data which was in ascii format. Thirty minutes later, we discovered some coding for the pipes were incorrect and we fixed it. Then we ran the importing process again and it worked. We opened up the development area in GIS and found the sewer features had been duplicated. And guess what? The job has already been put it but it hasn’t been marked as done in the job recording database.
This was stupid. But I did learn another lesson: It was to check the area before importing and adding new features into the system. As simple as that.