Author Archive

GeoMondrian 1.0 is available for download

| September 8th, 2011 | No Comments »

After the release of the stable version 2.0 of its Spatial ETL tool GeoKettle yesterday and in preparation for the FOSS4G 2011 conference, next week in Denver, Spatialytics is proud to announce today the release of GeoMondrian 1.0.

GeoMondrian is an open source Spatial OnLine Analytical Processing (Spatial OLAP or SOLAP) server, a spatially-enabled version of Pentaho Analysis Services (aka. Mondrian). As far as we know, it is the first implementation of such a server and it is open source! Read More

Immediate release of stable version 2.0 of GeoKettle

| September 7th, 2011 | 1 Comment »

After several months since the last stable version of GeoKettle, many hours of development and testing work, a release candidate, Spatialytics is happy to announce the release of GeoKettle 2.0. This stable version is now available for download.

This release brings some bug fixes and enhancements to some capabilities already provided in the 2.0-RC1 version of GeoKettle. In no particular order: Read More

How to create and use a job/transformation repository in GeoKettle?

| August 4th, 2011 | No Comments »

With the release of GeoKettle 2.0-RC1, various tools (wiki, trac, forum, …) have been set up and made available for supporting the community interested in open source projects hosted on and developed by Spatialytics.

This blog post initiates a series of documentation posts that should help users and developers in better mastering GeoKettle. It will be followed week after week by different tutorials, how-to, tips and tricks that will detail some specific and interesting capabilities offered by this open source spatial ETL tool.

This first post deals with the creation and usage of a job/transformation repository. It is a very powerful and exclusive but not so known feature of GeoKettle. A repository in GeoKettle lets you create a common workspace where to share jobs and transformations between different users across your organization. It is a practical way for some users to collaboratively work on a data integration process and to keep track of changes on the jobs and transformations during time. As it allows the centralisation of jobs and transformations in a shared repository, it avoids having different versions of a same transformation on various computers, which often results in the users finally do not know anymore what is the right and up-to-date version of the transformation.

To know more and especially how to create and use such a job/transformation repository in GeoKettle, please visit the associated documentation page on the wiki.

Hope it helps and do not hesitate to provide us with feedbacks or ask questions on the forum.