14k.be

Lot's of functionality is still missing from the OsmSharp library:

- Support for turn restrictions

http://wiki.openstreetmap.org/wiki/Relation:restriction

- Support for turn weights

In short this means that in europe for example (except for the UK) turning right is more convienient than turning left. This can make a big difference when calculating shortest, or should I say efficient, routes.

This requires converting nodes that have the weights into extra ways. In the algorithm(s) I use only the ways can have weights. More on this later.

- Better overall support

This means supporting different OSM data sources; PostgreSQL, OSM API, XML.

I also needed to implement a mechanism that synchronizes a local PostgreSQL-db with the main OSM servers (by downloading the changesets) BUT only for a given bounding box. Something that is not supported by osmosis. I think because of the need to query the target database to determine where the changesets are located.

Missing features can be turned into upcoming features. I can say that support for turn restrictions is present, support for the turn weights should be supported by adding the turn restriction functionality but remains untested. I first need some good heuristics to test with.

Better overall support is something that get's implemented purely because I need it myself.

A few more weeks and everything should be tested and veryfied. I will consider this version 1.0 of the library.