Netcdf export engine and GUI finally done

I finally managed to finish the export wizard for netcdf files. The problem for the first time for me was that I had to limit very carefully what could be done during export... if you are interested in a tour through the export process, I

wrote down some docu on the JGrass soc page.

Enhancements in the print editor of udig

During the udig code sprint I worked a lot on the printing module, that needed some love. I made screenshots to give a description. But now I am really done from preparing the release for tomorrow, that I don't feel like... hope you will enjoy those quite selfexplanatory screens:

And the resulting A1 landscape pdf...

Meet your team!

Wanna see who is working on making udig 1.2 great right now?

Meet your team!

http://udig-news.blogspot.com/2009/07/udig-code-grind-team.html

The udig code grind, day 2

The udig code sprint is at its second day.

We are posting info on the udig news blog: http://udig-news.blogspot.com/

Fun, fun, fun!!!

Exporting sets of GRASS rasters to netcdf

If you wonder how to export a GRASS raster map like this



to a netcdf dataset, then go to this page.

And this is how it looks like when you visualize it again in JGrass.

bluetooth gps on linux - short howto

Once you paired the gps with your pc, scan for the device to gather the hardware address:

> hcitool scan

Scanning ...
00:0B:0D:6F:F9:C5 SJA GPS

Once the hardware address is found, you can use it to find the channel through which they chat:

> sdptool browse 00:0B:0D:6F:F9:C5

Browsing 00:0B:0D:6F:F9:C5 ...
Service Name: SPP slave
Service Description: Bluetooth SPP V1.01
Service RecHandle: 0x10000
Service Class ID List:
"Serial Port" (0x1101)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100


In this case channel seems to be 1. Create a virtual serial port through which to bind the gps through its hardware address and channel to the device rfcomm0:

> rfcomm bind /dev/rfcomm0 00:0B:0D:6F:F9:C5 1

See if it works:

> cat /dev/rfcomm0

If everything went right, now you should see a stream of NMEA sentences coming along your console.

To be able to see it for example by java programs, you need to link it to a virtual port ttySxxxxx:

> sudo ln -s /dev/rfcomm0 /dev/ttyS0007

jai & tail: cannot open `+215' for reading: No such file or directory

tail: cannot open `+215' for reading: No such file or director

I already had this once and I was able to forget. When installing jai_imageio in your jdk you might get this.
For example it happend me with jai_imageio-1_1-lib-linux-amd64-jdk.bin but I remember last time it was on a 32 bit.

The fix is really easy with sed (do not use a text editor to change, else the binary content of the installer will get corrupted). You just have to change the tail command syntax to work:

sed s/+215/-n+215/ jai_imageio-1_1-lib-linux-amd64-jdk.bin > jai_imageio-1_1-lib-linux-amd64-jdk-fixed.bin

Then run sh jai_imageio-1_1-lib-linux-amd64-jdk-fixed.bin


--------------
Update:
as a gentle anonymous hacker stated:

export _POSIX2_VERSION=199209

also works and is nicer than the idea to change the installation file. Thanks!