Web Clients Are Getting Thick
Remembering days when client-server rules the world, then days when everybody praised light web clients where all user interface (UI) was prepared on web server and any user action was communicated back to server (this could lead to heavy network traffic - I've seen one mainstream ERP program, where a change in one input, say line item quantity, lead to several megabytes being sent over network). I'm quite amused to see how we're returning back to thick clients and passing more and more UI tasks back to user devices. This probably make sense, taking into account the computing power available in user devices now (my mobile has approximately same computing power (dual core 1.2 GHz ARM CPU) as a reasonable server ten years back(Sun V240 for instance)) and improvement of web browsers and especially their Javascript engines. Normally utilization on an average client machine would be very low, unless client is dealing with digital media, so using available computing power there is an obvious step. Network bandwidth could be now more precious resource then client computing cycles.
I do like maps. Recently I was looking at some digital maps and got into more details and found several nice open source tools about which I'd like to write in this article. As in any area open source provides interesting alternatives to work with digital maps and geographical data and what is also very interesting there are now free sources of good quality geographical data, which can be used freely by everybody to create their own maps. In this article I'm explaining how use data from Open Street Maps (OSM) project for creating maps in QGIS and how to use PostGIS to store geographic informations and have fun playing around with their different features of map data and tools. This tutorial is focused on linux (debian based - ubuntu 12.04 resp. mint in my case) desktop and assumes some basic knowledge of your linux desktop administration.