![]() This is literally part of the OSM dataset. > or the roads closed for construction currently. Unfortunately, where I live, bus companies seem to "license" that data only to Google. There are surprisingly good apps for bus navigation using OSM in some parts of the world. > its pulling in data from multiple sources like the gps location of the bus I'm waiting for Text-to-speech is almost always provided by the OS rather than the app. This is a hard one especially for long routes when calculated on a phone rather than on a server. > Have to remember that a maps app is way more than just data. OsmAnd would not be able to tell the difference between the turning lane on an intersection and an entire road that just has no name because the way the data is entered is there is just an unamed path joining the roads so the text to speach would say "bear slightly left" instead of "turn right on to foo street". You would also need a whole bunch of heuristics for the OSM dataset that the current apps don't have. ![]() Its efficient routing, its good text to speach, its pulling in data from multiple sources like the gps location of the bus I'm waiting for or the roads closed for construction currently. Have to remember that a maps app is way more than just data. The data in OSM is pretty good but there are no apps for it that are actually good other than leaflet JS for embedding on sites. Wikipedia is super basic software wise while GIS and everything around it is extremely complex. The problem is drive by contributors are not very good at developing software. Wikipedia shows that average people are pretty good at assembling data. I could ask my father but I don't think he'll remember either. That's most likely where we were that day, but where exactly I can't tell. I don't have the exact route for that stage, but it's described as a hilly stage so I assume it passed through the Vercors Massif on its way to Grenoble. ![]() Sure enough, that passes through the Drôme departement where we were on holiday. I found out that he won stage 14 in the Tour De France of 1984 (which means my earlier estimation of mid to late 80's was not entirely correct), so the stage we observed from a distance must have been stage 15, from Domaine du Rouret in the Ardèche to Grenoble (. I remember we were cheering for Flemish cyclist Fons De Wolf since he had won the stage the day before. I don't know exactly either, but there are some clues I thought of after I posted that story. That wasn't the only time we saw significant differences between French maps and France itself, but it was by far the most memorable one. So we stayed there for a while and saw the Tour pass far below us, much too far to recognize anything except the helicopters but even those looked more like flies than helicopters from our high point of view. The world simply didn't conform to the map. ![]() There simply wasn't one, and the terrain was not exactly suitable for walking down without a path. But when we arrived at the top, there was no path down the other side to be seen. The map clearly showed paths on both sides of the ridge, and sure enough, walking up the ridge went smoothly (if tiring) along that path. In hindsight we could never have made it on time. Watching the Tour was not really the main objective, otherwise we would have driven to a more suitable spot by car, but it was an incentive to keep us kids going. We started in one valley and the plan was to hike up the ridge and then down to the neighboring valley, where we knew the Tour De France was going to pass that day. We did have a paper map though, and I think it was an official topographic map. Must have been somewhere in the mid to late 80's, I think. I remember a hike we did on holiday in the Drôme department of France when I was a little kid, long before OSM or Google Maps or even Microsoft's Terraserver. Nothing is perfect, not even official paper maps.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |