Sensor Web, Geoprocessing, Security & GeoRM, Geostatistics, Semantics, 3D, Ilwis, Earth Observation

Intelligent Farming by Applying the Web of Things Paradigm

May 30th, 2012 @ 21:15 by Sidhant Hasija
Posted in GSoC, Sensor Web

Agriculture in India boasts it is the single largest economic activity in the country, employing about 40% of the population and feeding just over a billion people. By 2030 the Indian population will account for 18% of the total world population. In order to provide good quality grains and cereals to their home, farmers need to employ intelligent and cost efficient farming practices which maximize production while minimizing the use of precious resources such as water and nutrients.

This can be achieved by deploying sensors and applying the principles of the Web of Things. The immediate goal is to provide growers with the ability to precisely monitor and control the use of water and nutrients to plants in these production settings, based upon daily plant requirements. An example of such a Web of Things application is AgriSenseBox – an instance of the 52°North SenseBox project.

(more…)

Dynamic Output Formats for the Sensor Observation Service

May 30th, 2012 @ 14:21 by AlexanderKmoch
Posted in GSoC, Sensor Web

[Starting today, our Google Summer of Code students will present their projects. Alexander Kmoch is first. Enjoy!]

As one of the 52°North Google Summer of Code projects, “Exchangeable Encodings for the 52°North Sensor Observation Service (SOS)” aims to implement a customisable result set encoding mechanism. The users would then be able to add their own compiled libraries (like plugins), which contain all the necessary code to provide the requested data in different formats, such as CSV or GeoJSON,  to the SOS. When that mechanism works, we can easily add more encodings, e.g. the planned WaterML2.0 – but for now, where to start?

(more…)

WPS Birds of a Feather Session @ FOSS4G CEE

May 21st, 2012 @ 11:23 by Ann Hitchcock
Posted in 52°North, Geoprocessing

52°North invites all who are interested in WPS, web-based Geoprocessing or similar topics to attend an open session to discuss trends and challenges or exchange experience on these topics. The “WPS Birds of a Feather Session” takes place today – Monday, May 22nd, from 17:30 to 18:30. It is an excellent opportunity for the WPS community to get together and meet in person. Sign up now!

http://foss4g-cee.org/program/bof/

What’s up?

May 14th, 2012 @ 08:14 by Martin Schouwenburg
Posted in ILWIS

So what can we expect for lets say the next month of ILWIS. It’s nice that the 3.8 has been released but that doesn’t mean that the work has suddenly stopped. I have been rather busy the last few weeks with a few developments that I would like to share with you.

  1. Tables. The internal design of tables in ILWIS is quite silly (imo). Echoes from a very distant past of Ilwis that were never properly redesigned. The basic assumption of the ( internal) structure is that everything is based on columns instead of records.  Now basically there is nothing wrong with that. Most operations you do (in Ilwis) are column based not record based. Yet internally there is a big flip-flop continuously happening between column based and record based handling of things. This causes a big performance hit. Furthermore because all columns are owners of their own data (and not the table), data access is often going through many layers before getting at the ‘real’ data.
    I redesigned the table structure to a unified system. In the Ilwis 3.8 this already used for loading the vector maps which are basically tables when stored. But these tables are very isolated and don’t have any interaction with tables in general. I am extending that now to the rest of the tables but have to be very careful not to disrupt existing functionality.
    So what do I gain as end-user? Well, tables still work the same as they used to do. But… They load 20x times as fast(realy) and have an access time that is 2-3x as fast. So , yes. You do gain something.
  2. Openstreemap tile server. For those who don’t know it. Openstreetmap is an Open database  where geographical vector data is stored free for access by the outside world(see http://wiki.openstreetmap.org/wiki/Main_Page). An Openstreetmap tileserver is a renderer of this data onto tiles of many different zoom levels so that others can use it as layers in their application. I need to support this in Ilwis as it is needed for one of sub-projects of Ilwis and is useful in general. Of course this only works if you have a network connection where there is a tile server.
  3. Geonetcast data as OpenDap service. This is work I already started late last year (with success) and I need to polish it up somewhat. Geonetcast is a successful toolbox based on Ilwis, which exposes (see also http://52north.org/communities/earth-observation/ of 52N) loads of RS data in a consistent way. There are whishes from another project I am working with to be able to access this data as a service. The problem is that the data stream is rather large, continuously updating ( from 5 minutes to one day) and in the usual zoo of different raster formats. The toolbox translates this to an Ilwis format to have a consistent and accessible format to use the data in analyses. The data stream is so large though that this can’t be done on a continuous basis. It has to be done per request for a specific dataset(client side). This is the work of the toolbox. For this project I had to do about the same but this time server side(but still per request) and then translate the Ilwis data to netcdf as OpenDap is built around netcdf. What you now basically do is sent a WPS command to an ILWIS or 52N WPS server, it will do the necessary processing server side and then send a OpenDap link back to the client. This seems to work ok; I now included some extra subsetting to reduces the workload for the server.
  4. Debugging. As usual after a release you encounter some issues that should have been addressed ( import shape, grrr). Ah well, such is life. I will not make a new 3.8.1 or something but simply replace the current download. The about box will probably show 3.8.01 I suppose.
  5. Orfeo.  Already for some time I eyed the orfeo toolbox (http://www.orfeo-toolbox.org/otb/) as a possible extension for Ilwis functionality. But during the making of 3.8 I simply didn’t have time for it. I will make an Ilwis shell for it (both on UI level as on command level) and the include it in Ilwis. If all works well Ilwis will be seamlessly be integrated with the Orfeo functionality. Probably this will not be part of the standard Ilwis download but available as separate plug-in from the earth observation community of 52n.
  6. And last but not least Ilwis NG. This is continuous process and progress has been made there.

So what is de planning of all this? Well point 1), 3) and 4) are in the last stages. Have still to do some work there but the bulk is done. I plan the 3.8.01 for end of this month or possibly the first week of June. This will probably not include the table stuff (yet) as I need to do some real testing there if I didn’t mess things up, tables are quite important after all. Orfeo will probably start somewhere mid June. I am unsure at the moment how long this will take but my first guess would be about a month.  And Ilwis NG? Hmm well, difficult question. I suppose that somewhere in 2013 there will be a version but if that already has the same functionality as Ilwis 3.8 I am unsure. Anyway NG will be very modular so I can release it piece by piece. We will see, it is a bit premature to speculate too much about that.