rants

The Shapefile 2.0 manifesto

Geographic Information Systems (GIS) are by their nature data driven. The data comes in a wide variety of raster and vector formats. Rasters hold raw, continuous data recorded striaght from the real world. An example is Satellite/aerial imagery, this is a commonly held in an open format with broad support, such as GeoTIFF or GeoJPEG.

Vector formats hold refined, discrete data, which has been manually traced or otherwise derived other data sources. Examples include building outlines, contours, road routes, pipe networks land land parcels and locations. Vector data is usually traced or derived, at great expense from raster data, to encode business information – as a result it’s usually highly valuable.

Unfortunately, there are many GIS vector file formats,  and most are proprietary. They can only be used to their full in their native software. Three of the biggest are AutoCAD DXF, MapInfo TAB and ArcGIS Personal Geodatabase. One vector format is unique – both an open standard, and in wide use: Shapefile

Shapefile is publicly documented in ESRI Shapefile Technical Description by ESRI Inc., it’s creator. Any GIS software worth it’s salt can read and write to the format, so it’s become the least common denominator. It is the format for storing and exchanging vector data between teams, departments, businesses and government. In my opinion this makes Shapefile the best thing ever to happen to GIS, without it the GIS market would be a fraction of it’s current size. More >

Pidgin chat with padding

Fitts’ Law and Minimalism vs GTK+ and Qt

It all started with the Pidgin chat window, which is surrounded by several pixels of padding. To my eyes the padding doesn’t achieve anything, it just wastes space and detracts from the clean, minimalist lines of the Buddy List. After much fumbling, I managed to change it in the Pidgin source code . Bug 6987 with patch was duly filed.

Now I’ve become obsessed, I’m spotting extra borders and pixels in nearly every application on my desktop.

Pidgin chat with padding
More >

@Programmers of web forum/blog software

Dear web 2.0 coolios,

Please stop writing comment systems with half-assed threading. I understand you had to replace all those icky newsgroups on usenet, but you could have done a better job.

Take a look at Google Groups, Gmane. See how all those conversations are nicely grouped together? See how nobody is writing @previous_author? Please sort it out, because the status quo doesn’t work.

Sincerely, Alex Willmer

P.S. To anyone commenting here: I know I’m not eating my own dog food. I am ashamed.