A couple of months ago I opened a branch named »ui-ng« in MoNav‘s repository to develop a new user interface. Meanwhile this branch became a playground for several hacks, and some of them are just spikes to check out whether some ideas work or not.

I denied to work on speech output this spring, as I knew this would become a rather lengthy task. But it was obvious that I won’t resist the temptation during the cold and dark winter months. So I added the first code to generate spoken turn instructions recently. It is an ugly hack, just to determine what was possible. The code as found in the »ui-ng« repo works, well, at least a bit. The instructions are far away from being useful, except for lonesome crossings or roundabouts without other crossings nearby.

I’m using prerecorded samples for now, as the current open source speech synthesis systems did not show the results I desired. OTOH, this means I cannot generate instructions with dynamic contents like distances or street names. Additionally, those samples currently are included in the application binary, which will pollute the memory of handset devices as soon I’ll add further localized samples (currently speech is available in german and english language only).

The main issue is that MoNav recalculates the route each time a GPS position update is received – which means each second on the N900. As the GPS position always is a bit inaccurate, MoNav will speak »Please turn right« when you pass, for example, a gas station and the GPS position is off the road by a couple of meters.

As a consequence, I’ve just written some code that detects whether the vehicle is still “on track”. The route only gets recalculated in case the vehicle left it for more than x meters. This makes the route much more persistent and will cause far less headache than the previous approach. As this happened just a couple of minutes ago, the code is not in the repo yet.

There’s still a lot of work to do, and I’m curious whether I’ll stay motivated enough to do all of the work ahead. On the other hand it’s just plain fun to explore the secrets of a usable routing application.

So stay tuned. The next week(s) will show whether I’ll »head straightforward« :) .

MoNav Street Name Rendering in Kandel

Thanks to the work of James Hollingshead, MoNav now provides street name rendering at high zoom levels. This required a change in the map file format, though, so the currently available maps (which admittedly are rather dated) won’t work with binaries built from the current tip of revision control.

The new code is already available for two months now, but I hadn’t had the time to check it out. Today I got the client to compile on Max OS X 10.7.2 (aka Lion). I did not get the map preprocessor compiled, neither on Lion nor on the server, due to missing mapnik dependencies, but I got it compiled on my local Linux box.

The above screenshot shows the inner city of Kandel in Rhineland-Palatinate. I usually use this state for test runs for creating maps, as its file size is acceptable for my desktop machine.

I’m quite grateful that James did the work of creating the first vector renderer for MoNav, and that he now also added street name rendering. The next step is to get the preprocessor compiled on the server, though this might take a little while as the map processing script needs adjustments too. For Maemo on the N900, an updated binary is already available via the repo. Before you install it, ensure you have updated map data available. Otherwise you will end with an updated binary which cannot load the map data present on the device – a rather useless constellation from a user’s point of view.

Thanks a bunch, James.

I didn’t use it much. It mainly served me to create binaries of some cross platform applications I was working on. However, it’s CPU speed and amount of RAM are a bit limited for nowadays requirements. Additionally some contemporary applications denied to run on Tiger, and updating the OS on the feeble machine was not an option. Thus I bought a more recent machine powered by Lion s/h:

Its base size is more than the one of its predecessor:

I’m glad that Apple dropped the optical drive – I didn’t use one for years, and even if, only to convert some of my audio discs to ogg files. As a consequence, the new Mini is a bit thinner than the older model. Here’s its connectivity:

The user can easily access the RAM slots just by turning and removing the bottom of the device:

The overall operation feels much smoother now, and it operates quite well on the recently purchased Dell display. I already ported all of my data from my Dell Notebook to the Mini, as it will serve me as my primary desktop machine. I’m pretty curious whether I will find a replacement for any application I was used to on the Linux notebook. Of course I will :) .

I was still using a CRT connected to my Mac Mini, as I’m rarely using it. As this will change soon, I needed a replacement. Unfortunately the usual consumer devices as found in typical shops are often glossy – if not the panel itself, at least the cabinet. The closest to an acceptable compromise were some of the LG Flatrons (e.g. the E2441V), but a small stripe around the display and the stand still are as glossy as a grand piano.

I left the consumer displays alone and read the reviews of two Dell devices. The U2412M 24″ display provides an aspect ratio of 16:10 and a resolution of 1.920 x 1.200 pixels (in-depth german language review), whereas the U2312HM 23″ display provides a ratio of 16:9 and 1.920 x 1.080 pixels (in-depth german language review) respectively.

I wanted to buy the U2412M, but I found an U2312HM s/h at a very attractive price tag so I could not resist buying it. It arrived two days ago.

Package Content

The package contains an optical disc with drivers and the like, a quick setup guide, a USB cable, a power chord, and video cables, both VGA and DVI:

The add-ons

Panel and Stand

The main content is the panel and its stand, of course. The stand just snaps into the back of the panel, while no tooling is required. The stand also contains a cutout to bundle the cables. A simple but useful detail:

The panel and the stand

Connectivity

The panel provides two power inputs, DisplayPort in, a DVI input, a VGA input (but no HDMI input). The panel can act as a USB hub also, thus it provides one USB-Upstream and two USB-Downstream jacks:

The Connectivity

Two further USB inputs are placed on the left hand side of the panel and are very handy to connect USB thumb drives or handsets.

Operation

The device can be adjusted to the desired position in a number of ways. The user can rotate the stand and turn the display in an upright position. It can be moved up and down, and tilted. With its completely matte and unobtrusive surface, it’s a perfect display for my needs:

Connected

Conclusion

I’m glad I bought it – it’s just a great device. As the resolution addict I am, only one wish came up since I set it up – even more pixels, please :) .

I’m not a fan of the 16:9 ratio often found on computer displays nowadays. My previous notebook had a 4:3 resolution of 1400:1050 pixels, and my current notebook provides a 16:10 resolution of 1680:1050 pixels. Now I have even more pixels in width, but still only 1080 pixels in height. Heck, a 4:3 display of 1920:1440 pixels in an upright position would be great :) .

Since my 40th birthday passed by recently, I invited a couple of friends for a 20 kilometers black forest hiking trip. It led us from Forbach over the Rote Lache pass to Baden-Baden/Oberbeuern, where we took the bus to the station to get back to Karlsruhe.

The weather was warm and sunny, reminding us of the indian summer. Between Forbach and Bermersbach we followed the Ziegenpfad (Goat’s path), which is often used by families with children:

Obviously the inhabitants of the black forest take hunting very serious:

The Holzschuhrank is a locality and a shelter with a fountain and sleeping facilities, sited at a crossing:

Fortunately there were lots of details along our way which were missing in the OSM database, so all kinds of gadgets (such as Garmins, N900s etc.) came to play:

That’s deer ragout with croquettes and brussels sprouts. No, I didn’t take a picture of everyone’s dishes :) :

As we were late and the daylight saving time ended last sunday, it got dark while descending to Oberbeuern. At least the male participants appreciated the displays of the bus booting Linux 2.x :) :

Here’s the trip:

Scott Trail Boa

We intend to completely map a cycleway of about 160 kilometers for openstreetmap.org as a single day trip. That’s quite a distance, as the usual trips are no longer than 80 kilometers. Since a german magazine reviewed a couple of cycling shoes (available online as a portable document format download), I’m lurking around. Finally I found the Scott Trail Boa online at the Amazon marketplace. I had good luck, as the dealer offered the size I needed for 90€ “only”.

This shoe is available with traditional laces, or with a innovative locking system by Boa Technologies. As the abovementioned review states, the Scott Trail with traditional laces is a bit fiddly to handle. The same shoe with the boa lock, however, is really convenient – just turn the dial to tighten and pull the dial to untighten the laces. That’s it.

I got the shoes today, but left the office late, so I had no chance for a comprehensive test. I just mounted the cleats and tried to get comfortable with Shimano’s SPD system abusing a nearby parking lot. Frankly, I should have tried biking shoes earlier, especially before my recent trip to the baltic sea. Anyway, I’m eagerly and couriously awaiting the next sunday and hope the weather conditions will be fine for a first test ride.

Das N810 hatte ich mir fast ausschließlich für Mappingaktivitäten geholt. Einerseits steht mit Maemo Mapper eine wirklich gute App zur Verfügung, um mit Karten von OSM (und anderen Quellen) auf Wander- und Radtouren zu gehen, andererseits steht mit osm2go ein Programm zur Verfügung, mittels dessen man live vor Ort Daten für Openstreetmap erfassen kann. Das Hochladen erfolgt anschießend direkt vom Gerät aus, sobald man ein Funknetz (WLAN) zur Verfügung hat. Somit entfällt das Nachbearbeiten der Daten am heimischen Rechner. Ich habe mit dem Gerät Wald- und Wanderwege genauso erfasst wie Hausnummern und halbe Ortschaften wie Oberkaufungen. Sehr schön ist das hochauflösende Display, das man auch im Freien gut ablesen kann – um Kartenmaterial anzusehen, kann man gar nicht genug Pixel zur Verfügung haben.

Allerdings ist der eingebaute GPS-Empfänger ziemlich schwachbrüstig. Ich habe daher einen externen Blumax-Bluetooth-Empfünger mit einem Sirf III-Chipsatz genutzt:

Hier noch eine KFZ-Halterung, die entweder an der Windschutzscheibe oder am Armaturenbrett befestigt werden kann und in alle Richtungen verstellbar ist. Die OPenStreetMug gehört allerdings nicht dazu :) :

Leider liegt das Gerät schon eine Weile ungenutzt herum, weil ich inzwischen ein Nokia N900-Smartphone nutze. Ich würde das Gerät daher gerne an Mapper abgeben, die vielleicht gerne Hausnummern erfassen oder komplizierte Kreuzungen vor Ort modellieren möchten.

Das Gerät zeigt Gebrauchsspuren, ist aber voll funktionsfähig. Insbesondere die ausschiebbare Tastatur hat ein paar Kratzer abbekommen:

Das Gerät ist aus Edelstahl und dementsprechend robust. Das Betriebssystem ist frisch aufgespielt, so dass sich die Software im Originalzustand befindet. Wer sich für das N810 oder den Komplettsatz inklusive KFZ-Halterung und externem GPS-Empfänger interessiert, schreibt am besten SlowRider eine Nachricht. Eine Einlage für eine Otterbox 2000 kann ich auch noch beilegen.

The last two days I’ve worked on a first translation system for MoNav. Thanks to Qt4 it was just simple, and admittedly I copied over some lines of code from one of my other projects, Gebabbel.

MoNav checks the user’s system for a locale string, searches for a matching translation file, and if available, it gets loaded. Currently, the translation files are included in the binary, so we do not need to care about install paths and the like. As soon we have some translations available, they will be removed from the binary and installed as separate files to save some memory.

This also means we are in desparate need of translators for the upcoming releases. Do you want MoNav to appear in your mother tongue, maybe Russian, Chinese, or Bamanankan? As no programming skills are required to create a translation, do not hesitate to contact us.

The minster of Strasbourg, with its unfinished right tower

What a great april, at least concerning the weather! I decided to visit Strasbourg, the great medieval city where I haven’t been for over a year or so.

I let MoNav do all the routing, and it led me a really great way. So what about the initial question? Of course it can, that’s out of the question. There’s a grain of salt, though. As you can see in the tracklog rendering below, huge portions of the route led over cycleways along major roads – which is not exactly what you want during a sunday afternoon trip. I need to experiment with an additional routing set, which pays more attention to additional tags for convenient biking routes.

I crossed Rastatt and reached Schwarzach, where a great romanesque minster is sited:

The minster of Schwarzach

This is the interior and its organ. At least the carcase shows the traditional baroque design. It would be interesting to know what instrument it hosts inside:

The organ of Schwarzach minster

Here’s a shrine, hosting a skull and other remains. Frankly, I never understood this weird catholic tradition of exposing parts of dead people:

A shrine of Schwarzach minster

And just another object, a sculpture on one of the walls:

A sculpture of Schwarzach minster

I left late, and so I arrived late. Most tourists had left before my arrival – I’ve never enjoyed Strasbourg more. The street restaurants were populated mainly by local inhabitants. A great chance to have a nice supper in a nice atmosphere. Here’s as gratin of asparagus with ham and salad:

Gratin of asparagus with ham and salad

On my way back to the station, MoNav showed some weird route every now and then. Sometimes this happens due to an offset GPS location. Additionally MoNav currently ignores pedestrian streets for bike routing, which needs to be changed. But anyway I guess it needs some tweaking of either the openstreetmap data or MoNav’s code for better bike routing in inner cities.

A really great trip. I enjoyed each of the 88 kilometers. I predict I’ll repeat it this summer:

I’m just back from a family meeting in Heiligenstadt (Upper Franconia), the region where parts of my family originate from. It’s a nice town with some restaurants providing very good traditional food at a reasonable price. It’s sited in a valley which provides nice surroundings, and the interior of the medieval protestant church was rather surprising.

Of course I used MoNav for navigating there. The route it calculated was “just the right one”, and the track logging I recently hacked clearly raises its value.

What I’m missing most is speech output. Actually I already know how to do audio output on the N900, which is quite simple thanks to Qt. But a lot of backend work is required to create usable output. As CEST started today and I can smell the spring, it is unlikely that I will add this feature during the next weeks. Except we get some cold and rainy days, of course :) .