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

3D Connection Maps – Midterm post

June 26th, 2015 @ 08:04 by Adhitya Kamakshidasan
Posted in 3D, GSoC

Introduction

The aim of the WorldViz project is to set up thematic maps showing connections or dependencies between different spatial features. We have had several highly productive and interesting meetings during this first four weeks of this project. Currently, three of us are involved in the project – Professor Dr.Benno Schmidt, Christian Danowski (both Hochschule Bochum) and Adhitya Kamakshidasan (National Institute of Technology, Nagpur).

There are various components to our WorldViz Project and I shall to mention each one of them in detail below. (more…)

3D Connection Maps

May 27th, 2015 @ 08:58 by Adhitya Kamakshidasan
Posted in 3D, 52°North, GSoC

My name is Adhitya Kamakshidasan and I am in my Senior Year at the National Institute of Technology, Nagpur. I will be working on the Google Summer of Code 2015 project “3D Connection Maps” under the able guidance of Professor Benno Schmidt and Christian Danowski (both Hochschule Bochum).

(more…)

Welcome Google Summer of Code 2015 Students!

April 28th, 2015 @ 10:08 by Ann Hitchcock
Posted in 3D, 52°North, enviroCar, Geoprocessing, GSoC, ILWIS, Sensor Web

52°North is pleased to welcome the following students to work closely with us this summer on 6 Google Summer of Code projects!

  1. “SPARQL endpoint and Interoperability for enviroCar data”, Deepak Nair (India)
  2. “enviroCar Light”, Arne DeWall (Germany)
  3. “Social Driving Stats” (enviroCar), Heshitha Hettihewa (Sri Lanka)
  4. “Statistics for OGC Web services”, Csaba Lestar (Hungary)
  5. “WPS-ILWIS Bridge”, Aron Karolyi  (Hungary)
  6. “3D Connection Maps”, Adhitya Kamakshidasan (India)

(more…)

52°North seeks student applications for the Google Summer of Code

52°North is thrilled to announce that it has been chosen to be a mentoring organization for this year’s Google Summer of Code (GSoC)!  GSoC is a global program that offers students stipends to write code for open source projects. Google pays the stipend recipient $ 5.000,- for 3 months of software development for 52°North this summer. A mentor from a 52°North partner organization supervises the student during this period.

As such, we now look for students who are interested in writing code for various 52°North projects. The overall goals are to improve usability of products and to extend the user base to new domains.

If you are interested in writing code for software developed by the 52°North communities, please have a look at https://wiki.52north.org/bin/view/Main/GSoC2012. Student Application opens on March 26, 2012 at 19:00 UTC. The deadline is April 6, 2012 at 19:00 UTC.

This summer, flip bits not burgers with 52°North!

Any questions? Please contact Daniel Nüst (d.nuest@52north.org) or join us at *irc.freenode.net* *#52north*.

ILWIS and 3D

September 26th, 2011 @ 11:04 by Martin Schouwenburg
Posted in 3D, 52°North, ILWIS

In the past ILWIS had limited 3D capabilities. One could make a GeoRef3D which generated a 3D image (with a DTM) but it was cumbersome to use and quite slow. One of the goals of the 3.8 was upgrading these capabilities to something usefull.
In line with the design goals as mentioned in a previous blog, the idea was to create a 3D enviroment that could be helpfull for visual analysis. When one looks at a rendering of a map (2D), basically you explore the relations between the spatial locations and one or more attributes that are related to that spatial location. The most used is of course some color representing the value of an attribute. There are several schemes to enhance this ( number of attributea) in 2D but they often become a bit confusing.
If we use 3D space we can visualize the relation between spatial (X, Y) and two attributes in a simple way. We simply map the Z dimension onto a numerical attribute and still use different color ( or other form of representation) for the other attribute. This was for me the corner stone when designing 3D. So for example, the picture below shows the NDVI for a certain period (color) and the average precipitation (Z dimension) of the same period for the southern half of Africa.

So, how do we do those things? If you look at the Layer view at the left, you may notice two things that are different from the regular situation. First of all, in “global tools”, the 3D mark is checked. If checked the whole view shifts to 3D mode. But as the view has no default Z information, its just a flat map viewed in 3D. To add the Z information we activate the 3D properties tool ( context menu, right mouse button, on “Display tools”). Now we have a new tool in the tree, 3D Properties. To add a “real” Z value, double click on “Data Source”.  We get now a small form with a few options

  • Self. This means the Z information comes from the values of the map it self. Usefull for DTM’s and such
  • Rastermap. Select another value rastermap of the same geographic area. The values of identical coordinates on the source map will be used as Z information on the 3D view.
  • Maplist, only relevant for 3D animations. Every map in the animation is linked to a map in the maplist
  • Attribute column. The Z information comes from an attribute column of the map.
Double clicking on the “Scaling” node will open the scaling form with which you can change the scaling and offset of the Z information.
Moving through 3D space happens with the mouse buttons and mouse wheel while the ctrl key is pressed.  With the left button you rotate around the map, the mouse wheeel changes the distance to the map and the right button changes the point which you are looking at. It is possible that this movement model will change slightly as I am not 100% satisfied with it.
These are the basics of 3D in ILWIS 3.8. One can also combine 3D in several layers. The picture below comes from a combination of a DTM layer and precipitation layer.
Actually it comes from an animation where rain clouds move over a portion of Ethiopia.
 Three D has some limitations with respect to memory. At the moment the size of the rastermaps poses limitations. Beyond a certain size you might get out-of-memory errors and the visualization will not work.
3D isnt limited to raster maps, also vector maps can be used in 3D. Usualy, the Z information comes then from a attribute table but the other datasources are also possible. Below as picture of 2 segment layers that use the Z information of a DTM for the Z information. The contour maps also has extrusion on to better visualize its position in 3D space.
3D will be further developed in ILWIS with new tools ( e.g. space-time cube) but that is for after 3.8.
« Previous Page