--- Log opened Tue Aug 22 00:00:52 2017 00:02 -!- Horwitz [~mich1@p200300800E02BD00022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 00:02 -!- mode/#navit [+o Horwitz] by ChanServ 00:06 -!- pmckinley1 [~Peter_McK@88-110-204-124.dynamic.dsl.as9105.com] has joined #navit 00:24 -!- pmckinley1 [~Peter_McK@88-110-204-124.dynamic.dsl.as9105.com] has left #navit [] 00:55 -!- ilovekiruna [~ilovekiru@ip2505a0ef.dynamic.kabel-deutschland.de] has quit [Remote host closed the connection] 00:55 -!- ilovekiruna [~ilovekiru@ip2505a0ef.dynamic.kabel-deutschland.de] has joined #navit 02:48 -!- noradtux [~noradtux@2a02:2028:644:f801:593:a6af:83ec:21a5] has quit [Ping timeout: 240 seconds] 02:53 -!- noradtux [~noradtux@2a02:2028:54e:e401:593:a6af:83ec:21a5] has joined #navit 05:06 -!- noradtux [~noradtux@2a02:2028:54e:e401:593:a6af:83ec:21a5] has quit [Ping timeout: 255 seconds] 05:10 -!- noradtux [~noradtux@2a02:2028:54e:e401:593:a6af:83ec:21a5] has joined #navit 05:52 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit 06:32 #navit: < jkoan> Hi Kazer and all others, I did some research on tmc, probably we get it managed to include tmc support into navit. Even if its a lot of work, I found out that there is a standardized format for the location and event tables. In the future I try to get the tmc raw data out of fm Radio and try to parse the RDS :D 06:32 #navit: < jkoan> Then we can extract the tmc out of the RDS signal and be able to parse this. 06:32 #navit: < jkoan> For some country's I have the location and event tables. And one interesting thing is that osm has the location table for Germany imported at least partially. 06:32 #navit: < jkoan> So if we have some luck we must not write a matching between the location table and the osm data. 06:32 #navit: < jkoan> When we have the data stream from tmc and the data in maps and the lists my idea would be some kind of kind of storage (probably in ram) to store all tmc data. Then the routing could access it and be able to take care of the warnings. But in following we need some interrupt that is thrown if new tmc informations are available. Then the navigation should check if each information is relevant and in case of relevance calculate two new routes, 06:32 #navit: < jkoan> …hrough the traffic jam (or what ever) and around it. Probably the software could self decide which one is better, probably the user should be asked. 06:32 #navit: < jkoan> The rerouting must also take care of things like blocked roads, then a route through is not possible... 06:32 #navit: < jkoan> But therefore we have the event table and the standardized format :) 06:32 #navit: < jkoan> So the conclusion is that it is a lot of work, but at least now i think it's possible to manage it. 06:32 #navit: < jkoan> Kazer we should probably document as much about tmc as we are able to found. Also circuits to extract the signal and so on. Because the informations about tmc are really rare :D 06:47 #navit: < ilovekiruna> jkoan: sounds really cool 09:23 #navit: < jkoan> ilovekiruna: thanks 14:01 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.] 15:03 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 16:01 #navit: <@KaZeR> jkoan: nice. You might be interested in http://trac.navit-project.org/ticket/570 and https://github.com/motokokusanagi/tnav 16:03 #navit: <@KaZeR> https://github.com/Nimrod007/waze-api looked promising too, although there was a grey area with licensing 17:57 -!- noradtux [~noradtux@2a02:2028:54e:e401:593:a6af:83ec:21a5] has quit [Quit: Bye] 18:04 -!- noradtux [~noradtux@port-53961.pppoe.wtnet.de] has joined #navit 18:09 #navit: < ilovekiruna> Kazer: what happened with the voice interface? 18:09 #navit: < ilovekiruna> any news? 18:11 #navit: <@KaZeR> the voice interface? 18:17 #navit: < ilovekiruna> wasnt there somebody discussing recently, to control navit by voice? 18:19 #navit: <@KaZeR> ha! i'm not aware of anyone actively working on it. But then, i don't know everything :) 18:19 #navit: < ilovekiruna> but u remember what I talk about, right? 18:24 #navit: <@KaZeR> i might be missing a recent discussion.. but from your question it would be using voice to text to send commands to navit, right? 18:25 #navit: < ilovekiruna> yes 18:25 #navit: < ilovekiruna> i remember you worked with someone on it 18:39 #navit: <@KaZeR> ha, that person probably gave up then :) but if you're interested i can help you with it 18:40 #navit: < ilovekiruna> i c, no problem 18:41 #navit: < ilovekiruna> but i guess, i am already filled with the screencast and the task about droid testing ;-) 18:46 #navit: < ilovekiruna> for the pull-request: Do you need any detailed comments? 18:46 #navit: < ilovekiruna> also would like to ask if we could make the switch of limits by another button 18:54 -!- pmckinley [~peter@88-110-193-108.dynamic.dsl.as9105.com] has quit [Remote host closed the connection] 19:22 #navit: <@KaZeR> for the PR it's always good to provide comments and screenshots. Makes the review easier for everybody 19:23 #navit: <@KaZeR> we can probably make the switch work using another button, by using the cmd function 19:25 #navit: < ilovekiruna> cool 19:37 #navit: < ilovekiruna> so far when reading about robotium, it seems interesting, but not so well documented 19:37 #navit: < ilovekiruna> will dig further 19:43 #navit: <@KaZeR> awesome thanks. That would be super helpful 19:44 #navit: <@KaZeR> from my tests it was a matter of installing the robotium plugin in android studio, then we should be able to start recording some interactions 20:58 #navit: < ilovekiruna> was rather curious about how to write test cases directly 20:59 #navit: < ilovekiruna> would be also important to know which test cases are interesting for u 21:17 #navit: <@KaZeR> for now detecting app crash at startup would already be useful. So. start the app, pick a destination, compute the route 22:05 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] 23:48 -!- Horwitz [~mich1@p200300800E02BD00022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] --- Log closed Wed Aug 23 00:00:54 2017