[01:48:11] *** Quits: Horwitz (~mich1@p200300ec9f025300022268fffe64e7c4.dip0.t-ipconnect.de) (Ping timeout: 272 seconds) [02:00:30] *** Joins: Horwitz (~mich1@p200300ec9f0cd100022268fffe64e7c4.dip0.t-ipconnect.de) [02:00:31] *** ChanServ sets mode: +o Horwitz [05:07:54] More ore less. The possibility is a database based Format which could help to keep the plugin simple. But on rhale other hand could result in larger files (which I definitely want to avoid) or on the other hand we could just improve the binfile plugins. I know they have a version field, but this would force users to update navit [05:12:08] Another cool thing with a database based Format could be the possibility to update "on the fly" and selecting which objects to get. For example we could do a map extractor which only exports streets and nothing else for device where Space is a real concern. [05:40:34] @ilovekiruna there is a open standard for transit: GTFS which could be useful for navit to do multi stage routing [05:43:50] This is not related to the map format you asked fore, but it's interesting that this exist and has a standard format (mostly zip and csv) [05:47:09] This would probably be another map driver which should add it's data to navit. We would only need to optimise the display of such informations, the configuration which possibilitys to chose from (don't want to take the plane for example) and find a way how navit could handle the waiting between own arrival and the arrival of for example a train [20:03:04] *** Quits: genesis (~genesis@unaffiliated/genesis) (Remote host closed the connection) [20:03:19] *** Joins: genesis (~genesis@unaffiliated/genesis) [20:03:19] *** ChanServ sets mode: +v genesis [21:26:41] *** Quits: ChanServ (ChanServ@services.) (shutting down) [21:32:21] *** Joins: ChanServ (ChanServ@services.) [21:32:21] *** barjavel.freenode.net sets mode: +o ChanServ