Posts by: Tim Waters

Some of you were noticing that the Intersection analysis was a bit slow and we noticed that it was using quite a lot of memory – the larger the dataset, the worse it performed. We tackled this head on and have rolled out a much better algorithm, which, I’ve measured as being between 7 [...]Continue Reading

Leaflet & GeoCommons JSON

On October 31, 2011 By Tim Waters

Hi, in this quick tutorial we will have a look at a new JavaScript mapping library, Leaflet using it to help load JSON features from a GeoCommons dataset. We will add our Acetate tile layer to the map, and use the cool API feature filtering functionalities to get just the features we [...]Continue Reading

We use GEOS here in GeoIQ Towers, and love how powerful it is. If you are into your geospatial applications and you’ve never heard of it, you may well have heard of other applications that use it – such as PostGIS,  Mapserver, GRASS, GeoDjango and FME. We use it [...]

Continue Reading

GeoIQ Ruby Gem

On March 24, 2011 By Tim Waters

Developing with GeoCommons and GeoIQ just got easier in Ruby with the GeoIQ Ruby Gem – a wrapper around the REST API.

We have fuller, detailed documentation about the REST API, but using this open source gem, it’s possible for Ruby developers to get quickly started interacting with the system.

What it does [...]

Continue Reading

WMS and Tiles Goodness

On February 1, 2011 By Tim Waters

This week has seen the unveiling of a new feature from within GeoCommons.com - support for adding WMS and Tile layers
WMS So, you may be asking “What on earth is WMS?” well, it stands for Web Map Service and put simply is a service through which people can publish and serve out [...]

Continue Reading