Proposal for improving ImagePyramid support (and other small developments)

Ciao a tutti,

Supporting a project such as GeoServer requires a great investment of time and resources. Organizations that support it are faced with the problem of finding funding. As founder of my own company, I often find myself in the position to seek funding for supporting GeoServer and I obviously tend to prefer large contracts to small ones. This seems perfectly reasonable, however I do recognize that in the long run this approach may cause some missed opportunities. Large funding usually focuses on large developments, but they leave aside common glitches and bugs, i.e. isolated features that are not working properly or could be improved relatively easily. To counter this, supporting organizations must invest surplus money and resources from other contracts into tackling these problems, since it is difficult or inefficient to chase money to address each small issue separately.

As a specific example, I have lately seen people struggling to get the ImagePyramid extension working, and I know it would be relatively easy to improve things (in that it would not need a lot of funding) but none of our current clients needs this functionality, so the work never gets done.

With this in mind, I have come up with the following idea: once someone, be it a user or a support organization, recognizes an issue/missing feature that no one else wants or has funding to fix, we should try to describe the problem/feature somewhere (such as on this blog), provide a Point of Contact (POC) for the work and then ask the community for an Expression of Interest (EOI) to check whether there is enough momentum/desire to fix/implement. Perhaps the POC should write the proposal having already scoped out the work or maybe the scope should wait until we know that there is enough interest. Another topic where I would see some interest is in whether the process should be completely transparent or not regarding who gives the funding as well as who spends the funding gathered. I would be interested in feedback on all of these suggestions.

To test his idea, I would like to invite anyone who might be interested in providing a bit of funding to improve the support for the ImagePyramid extension in GeoServer to express your interest to me. Specifically, I am talking about automagic import from GDAL retile, improved stability and performance, and/or automagic pyramiding as a GeoServer/GeoTools utility.

If you are interested you can drop me an email at

Ciao, Simone.


  1. Jody Garnett
    Posted November 19, 2009 at 5:05 am | Permalink

    We already have the “long term roadmap” which is supposed to service this purpose – it meets all the requirements you mentioned (including a contact person). Chris and myself updated it a couple of months ago – but I would like to make it more attractive with pictures and or diagrams.

    There is no lower limit on the size of work described; only a list of features or fixes that we are enthusiastic about and need resources in order to address

  2. Frank Warmerdam
    Posted November 20, 2009 at 11:26 pm | Permalink

    I’m not clear on what is supported now or what exactly is proposed with regard to retile. But I would like to see GeoServer and GeoTools image access to support GDAL “TIFF” overviews in an associated .ovr file. I think that would be very convenient for people working with imagery in a variety of environments.

  3. Phil Scadden
    Posted December 6, 2009 at 8:40 pm | Permalink

    Well I am not particularly interested in imagePyramid but the problem of geometry extending across the 180 deg line certainly is an issue. Anyone looking in bids for that? (We are also looking at trying to fix ourselves but ArcGIS GISserver might be best bet).

Download GeoServer