currently we access only the OSM raster data. OSM comes in two flavours:
- raster data (the rendered map tiles)
- vector data (the definition of paths and streets)
This may be an option for a later release, but is very difficult and CPU time consuming. Basically you have to compute the normal vector to all close by paths and see where the closest intersection is. This means you'd have to additionally download the vector data for the area and do complicated calculations on the data - this might be too much for hardware we currently have.
Congratulations guys for developing such an helpful and interesting tool. I am using it now for almost a week and its really motivating and alot of fun. There is just one thing I like to propose for improvement. Maybe the settings already exist and I just didnt find them ;-)
I am running in an area where the gps quality is sometimes very low, caused by trees and houses. As a consequence the the logged track doesn't match with my real position, which means the calculated distance differs pretty much from the distance the routeplaner estimated in advance.
Would it be possible to to use the Openstreetmap-data to compensate theses variations? For example if a postions given by gps is lying close to a street, it should be possible to calculate the next position on the street. This position could be taken for the logged track. Using only positions of existing streets and tracks would improve the quality of the results alot. Of course there should be possibilty to activate or deactivate this function.