52°North Spatial Information Research GmbH

Last week I wrote about the high level design and structure of the next generation of Ilwis. This week I will focus on one of the most important parts of it, the connectors. In the picture of last week (part of it below), they made up the whole lower part of the second diagram

more >

Last week I wrote a bit about the high level ideas that form the foundation of the next generation of Ilwis. Though the piece was a bit (very) general I still felt it was necessary to write that down as it is the starting point of everything else. The core design of the framework is connectivity and not functionality. The assumption is that once you can connect to anything, functionality (done by ‘others’) is easy to add.

more >

Last week I wrote about the ‘why’ of a next generation Ilwis. This week I will talk a bit more about the foundation of the framework. We have a number of explicit goals we want to reach with.

1. Connectivity. The physical format or location of data is irrelevant. It is about the information contained in the data. So independence of format and location is a primary goal
2. Interoperability. Integration of different providers of functionality in a transparent way. Not limited to the access protocol they use.
3. Accessibility at programming level. Ilwis is and will be written in C++ which can be a technical challenging language. To ease the threshold for external programmers we will
   – Use an external C++ interface that is very simple to use for those who want/need to program in C++
   – Provide bindings to other languages. Python and Java are the primary candidate
   – Ease the threshold for desktop – UI programming
4. Flexibility. The framework must be deployable in multiple roles. From the traditional fat-desktop-client to lean mobile clients and client/server configurations. There will not be one Ilwis, but many (in different roles).

more >