Reporting Potholes

I've noticed on the news here in the UK lately that potholes in roads will have expanded due to the recent cold weather conditions - the old "freeze-thaw" effect.

In some areas people are being encouraged to report potholes to their local council offices - which got me to thinking, how about setting up a website linked to Google maps to allow members of the public to locate potholes in their neighbourhood?

A quick Google search suggests that I'm not the first to think of applying technology to achieve something like this, in no particular order:

• http://www.pwmag.com/industry-news.asp?sectionID=770&articleID=502140
• http://www.daventrytoday.co.uk/news/Mapping-the-potholes.3798730.jp
• http://www.surreycc.gov.uk/env/hews/hews.nsf/LERTF?OpenForm&CCode=POT~1&Subject=Pothole&faultID=58536393386
• http://www.echo-news.co.uk/news/3944037.New_technology_will_get_rid_of_potholes_and_save_us___1_5m__says_council/
• http://www.showusabetterway.co.uk/call/2008/07/the-pothole-rew.html
• http://survey.coventry.gov.uk/forms/pothole/index.html
• http://www.journalofmaps.com/cgi-bin/blosxom.cgi/GIS/potholes.html
• https://www1.walthamforest.gov.uk/webforms/pavement/

Then I came across something that looks like it already does the job:
http://www.fillthathole.org.uk/report

Relational Databases - PostgreSQL

Is it just me, or are there a lot more free and open source database systems out there than there were 3 or 4 years ago?

I was following a thread on a Hibernate forum the other day and they mentioned a couple of options that I've used in the past - PostgreSQL and MySQL, a couple I'd heard a little about (e.g. SQLite and Firebird) as well as something called H2.

Of these options, I prefer PostgreSQL. I've been using it on and off for almost a decade, but I don't think that necessarily makes me biased as I could just as easily have been frustrated by it if it wasn't such a flexible and reliable system.

The extensive feature set really saved me some embarassment with a project that had a very tight schedule a few years back.

My team had developed some Java code based around the Geotools APIs to manipulate some GIS data in a shape file. That all appeared to be working fine - until I attempted to deploy it onto our in-house test server which was a Linux system and had the same setup as the server that we intended to host the web-based application on when it went live!

I did some digging around and established that Shapefile manipulation was just for demonstration purposes (so would not have suited our needs anyway), then found that there was also the option of accessing the data via a PostGIS data source. So, I spent my Saturday afternoon building a new PostgreSQL system from source code, with the GIS extensions and the optimal geometry packages available compiled in .... and did a bit of tweaking of the PostGIS access code in Java and had the project right back on schedule for Monday morning's, "So, what did you get up to on the weekend?" coffee break.

I subsequent got the chance to pick up the same set of technologies and have them in place from day 1 in another project, so got to spend some time looking for decent tools for visually verifying the data - uDig was the best nice free system I could find - it connects to PostGIS fairly easily and exists within an Eclipse framework.