Thanks for pointing this out. I've just found the definition of the Garmin file format here: http://sourceforge.net/project/showfiles.php?group_id=125392
Well, I think that it would be unwise to use a proprietary file format for OSM, but let's see what we can learn from it ;) > -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] [mailto:routing- > [EMAIL PROTECTED] Im Auftrag von Andreas Brauchli > Gesendet: Montag, 10. Dezember 2007 23:02 > An: [email protected] > Betreff: Re: [Routing] Binary file format > > > On Mon, 2007-12-10 at 22:50 +0100, Adrian Stabiszewski wrote: > > > Yes, a binary-format would be a great thing to have. I don't quite see > > > what you mean with junction-node but maybe you could do a first > outline > > > of a format or a list of reqirements that you see for it. > > > We could start from there. > > garmin uses a binary format that makes sense for saving all kind of POIs > and streets and it also uses this for routing, not sure if it's > optimized for routing though. it can save several layer of precisions > (you don't want footways to appear on global scale) but you'd need this > for routing your walk from Canada to Mexico. > would this format be for routing only or also for map-display? (maybe > with pre-computed paths (pathtrees) on highways or frequently used roads > for every region) > > i think mkgmap's creator would be the most useful resource on this. > > andreas > > > > _______________________________________________ > Routing mailing list > [email protected] > http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/routing _______________________________________________ Routing mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/routing
