Category: opensource

Categories
opensource Thoughts

OpenStreetMap and the Rabbit Phone problem..

This week the innovative guys as Nestroia have launched an experimental version of their great real estate aggregation site using OpenStreetMap mapping as an alternative to the usual Google Map Tiles. This is great vote of confidence for OpenstreetMap, but it also highlights some of the problems creating geodata from the cloud.

Where OSM data is comprehenive the map tiles are often more detailed than those Google supply which are based on commerical available datasets. For example this section of tiles covering my childhood neighbourhood in London is truely beatiful, in many ways a better map than the commerical websites.

Chelsea

However the problem is that the coverage for OSM data is not yet complete, and where there is incomplete coverage, for this type of application, its use is a problem. Look at these examples from Wokingham, West of London and part of the UK’s silicon valley.

The Google maps tiles using Tele Atlas data are pretty much complete..

teleatlas

However the OSM version has a lot of missing detail..

OSM

Mapping data really does need to offer complete coverage for it to be really useful, some may remember in the UK in the early days of mobile phones there was an alterative system based on local hotspots called Rabbit. This failed becasue you had to be within 100m or so of a hot spot, unlike the wider coverage of the early analogue mobile systems.

Mapping data needs to be as comprehensive, with no coverage gaps, what is great about Nestoria’s early exposure of the data in a real application is to highlight where more volunteer work needs to be done to complete the work.. If this is achieved by the OSM community, the critic’s of open source geodata will be silenced.

Written and submitted from home, using my home 802.11 network.

Categories
Data Policy opensource

OpenAerialMap – Think Open Street Map for imagery..

Open Aerial Map

As happens in this world of constant communications, I heard of the new OpenAerialMap site via an IM chat with Jeff Johnson of PictEarth on Sunday lunchtime !

The idea behind OAM is for it to become an online repository for community generated aerial photography, sourced from Kites, Low cost UAV’s , etc. I’m sure many still see the creation of Open Source imagery captured by amateurs as a Joke, but then people were not serious about OSM !

It’s true that OAM cannot really replace the global systematic cover offered by satellite imagery or the professional aerial photography producers, but for applications where discrete imagery is required of a particular location at high resolution, or to cover a specific event or activity (high temporal resolution) there is a niche which can be filled by this imagery, and the services like OAM which distribute it.

As with OSM, OAM can work because the tools to both capture and distribute this type of Geodata have become democratised to the extent where it is possible for the amateur to respond to events faster than the professional,and to make that data available without the restrictions of conventional licensing. Although the distribution of large amounts of imagery represents all sorts of new challenges in developing a robust operational system.

As with traditional mapping, we are not looking at a replacement to the traditional top-down centralist approach to the creation of Geodata, however there is now at least an alternative, that may become more significant over time.

I wonder if there are plans to use include Geobase SPOT data set of Canada ?

Written and submitted from home, using my home 802.11 network.

Categories
Android LBS Mobile opensource

Android and LBS – in the stack at last…

So maybe now Mr Balmer is reconsidering his comments of last week..

For me and my interest in geographic information the key detail about the Android SDK is the LBS component, and where is appears in the whole android stack. I have often argued that LBS would only really make sense as an underlining infrastructure that is available to all applications, therefore allowing much higher levels of integration.

One of the key factors to the success of the iPhone is the great integration between its applications, it’s just a shame these are currently restricted in number, to the Apple supplied applications.

Android

With Android the Location Manager component is part of the core application framework, meaning that all user applications have access to the devices location. At a simple level this means that applications like the address book as access to the device location, so your contacts rather than sorted alphabetically could be sorted based on distance from your locations.

Or slightly more “left field” how about a security application which locks the device waiting on the user to enter a PIN if the devices location does not match the scheduled location from the calendar application.

For really the first time, the innovation which always comes from Open Source development can be focused on building LBS.. at last !!

Written and submitted from home, using my home 802.11 network.