--- Log opened Tue Nov 21 00:00:38 2017 00:03 #navit: <@KaZeR> let me check 00:05 #navit: <@KaZeR> sounds about right 00:10 -!- Horwitz [~mich1@2003:80:e4b:2000:222:68ff:fe64:e7c4] has quit [Ping timeout: 250 seconds] 00:24 -!- Horwitz [~mich1@2003:80:e6c:e900:222:68ff:fe64:e7c4] has joined #navit 00:24 -!- mode/#navit [+o Horwitz] by ChanServ 00:39 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/osm-exp/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/n 00:39 #navit: < Navit> oad.navit-project.org/logs/navit/android_armv4t/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-.failed 00:39 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html 01:20 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 268 seconds] 01:22 -!- j_f-f [~quassel@62.138.18.44] has joined #navit 01:46 -!- j_f-f [~quassel@62.138.18.44] has quit [Ping timeout: 240 seconds] 02:11 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit 05:16 -!- noradtux [~noradtux@port-1138.pppoe.wtnet.de] has quit [Ping timeout: 260 seconds] 05:17 -!- noradtux [~noradtux@2a02:2028:552:8101:ec4:7aff:fe33:3dc1] has joined #navit 05:58 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit 07:10 #navit: < eto> KaZeR: hi so i used navit in my car for the first time 07:12 #navit: < eto> i noticed several "notreally-issues" with it - one main is that notebook battery died thee fourths through roadtrip - do you think any inverter would help that? 07:13 #navit: < eto> second is i had no net so i was unable to figure out hw to make navit "update" 3D view continually - like commercial navs do 07:13 #navit: < eto> thir what is the state of opnegl port - gtk graphics is slow as shit to draw on my box 07:14 #navit: < eto> ? 07:28 -!- naggety [~naggety@126.red-80-27-221.dynamicip.rima-tde.net] has joined #navit 07:39 #navit: < naggety> eto: to update continually you have to edit navit.xml. Put attributes follow_cursor="1" and orientation="-1" in tag and attributes active="1" follow="1" in tag 07:40 #navit: < naggety> I also recomend to put attribute autozoom_active="1" in tag 08:12 #navit: < jkoan> KaZeR: why didn't you remind me that I don't forget about the map split on the new mapserver? ^^ 08:41 #navit: < eto> naggety: i have autozoom and orientation - i guess i will need to check follow_cursor 08:45 #navit: < naggety> eto: also active="1" and follow="1" in tag. Without active, navit doesn't know which vehicle to follow, and follow="1" it center the view every gps update (otherwise, it will only recenter the view when the vehicle goes out of the view) 08:46 #navit: < naggety> You can set follow="5", for example, to center the view to the vehicle every 5 gps updates, but I use follow="1" 09:14 #navit: < eto> naggety: okay i messed a bit with my cheapo gps receiver and supports two modes ascii one and binary one 09:15 #navit: < eto> for now i know navit works with acsii mode just fine - have yet to try binary mode - question is 09:15 #navit: < eto> what is gps update in this context? is it time dependant or movement speed dependant? 09:16 #navit: < eto> eg how many gps updates are there per second? minute? 09:16 #navit: < eto> as in follow="5" will make redraw each 5 seconds? or each 5 "move" snapshots? 09:20 #navit: < naggety> It depends on the GPS receiver, but normally they send 1 GPS update per second by default. 09:21 #navit: < naggety> Normally the GPS receiver sends the messages with the GPS info in a fixed interval of time, that in many cases it's 1 time per second. 09:22 #navit: < naggety> So if you set follow="5", it will be 5 seconds if your GPS receiver makes a GPS fix once per second 09:22 #navit: < naggety> If your GPS receiver makes a GPS fix once per 5 seconds, it will be 25 seconds 09:24 #navit: < naggety> set follow="1". This way, always Navit receives new GPS info it will update the view 14:30 #navit: < eto> roger 15:37 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.] 15:41 -!- naggety [~naggety@126.red-80-27-221.dynamicip.rima-tde.net] has quit [Quit: Konversation terminated!] 15:43 #navit: <@KaZeR> hi there 15:45 #navit: <@KaZeR> eto: yes an inverter would definitely help. How long did your battery last? 15:48 #navit: <@KaZeR> eto: the opengl driver should be stable enough for real world use. I'm actually going to test it this week-end for a long (1000kms+) trip 15:48 #navit: <@KaZeR> i'm still going to stick to gui_internal for now as the qml2 gui needs more work, but opengl should work, and it should be much better than gtk on some devices that have egl acceleration 16:04 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 16:22 #navit: < charles__> eto: for some laptops you can get power supplies that run directly off car power. Inverters mean two power conversions, car to mains, then mains to laptop. The direct is more efficient. Might be worth looking into. 16:46 #navit: <@KaZeR> jkoan: indeed, should have :D 16:47 #navit: < jkoan> It's more a must have feature 16:51 #navit: < jkoan> Also (as you have seen in the wiki) I didn't forgot about getting the file size from the server instead of storing it inside the android app itself. Everything i try to design should be friendly for automatic downloaders 16:56 #navit: < eto> charles__: thanks for hint 17:03 #navit: <@KaZeR> jkoan: nice 18:49 -!- charles__ [48241adf@gateway/web/freenode/ip.72.36.26.223] has left #navit [] 19:22 -!- pini [~pini@bou-fi.pustule.org] has joined #navit 19:59 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 240 seconds] 20:14 #navit: < jkoan> KaZeR: are you online? 20:16 #navit: < ilovekiruna> hi jkoan: 20:16 #navit: < jkoan> hi ilovekiruna 20:17 #navit: < jkoan> ilovekiruna: how good are you in mathematics? 20:17 #navit: < ilovekiruna> jkoan: should be reasonable well 20:17 #navit: < ilovekiruna> why? 20:20 #navit: < jkoan> its a algorithm problem for the new mapserver (i dont programing it right now, only think about the algo). WE have a shape (country for example and a rect (the file inside the bin) now i want to find out if the rect is inside the shape. how would your solution looks like? 20:21 #navit: < ilovekiruna> so you want to find the minimum rectangular encircling a shape? 20:22 #navit: < jkoan> i will send an image to make it clear what the result should be 20:24 #navit: < jkoan> This should be the result : https://static.jkoan.de/cloud/index.php/s/pbCTvtGksEXG6Xh 20:25 #navit: < ilovekiruna> ah, so more tiled 20:25 #navit: < jkoan> Yep 20:25 #navit: < ilovekiruna> the other one would have been easier ;-) 20:26 #navit: < ilovekiruna> a rather standard optimzation problem 20:26 #navit: < jkoan> I know, only 4 if/else statements 20:26 #navit: < jkoan> I probably have a really resource intensive way to calculate it 20:27 #navit: < ilovekiruna> am wondering what about a monte-carlo approach with classification? 20:28 #navit: < jkoan> My idea would be to build the intersection and calculate then the area size of this section. If it's zero the rect is not inside the shape 20:28 #navit: < jkoan> I don't know this 20:29 #navit: < ilovekiruna> It is for example used to calculate pi 20:29 #navit: < ilovekiruna> the so called statistical method 20:30 #navit: < jkoan> And what should this help here? ^^ 20:31 #navit: < ilovekiruna> if you randomly shoot on the whole map, and figure out which points are inside your area ( classification), u can also determine which values are outside 20:31 #navit: < ilovekiruna> and then just take the part of the grid inside 20:32 #navit: < jkoan> but is this more efficient? 20:33 #navit: < ilovekiruna> that i cant judge 20:35 #navit: < jkoan> Because we have around 1.000.000 rects in the binfile and probably only 100 which we want to grab 21:31 #navit: <@KaZeR> jkoan: yep 21:33 #navit: <@KaZeR> jkoan: what's wrong with the if/else approach? most of the time you won't even need to go through all checks 21:38 #navit: < jkoan> Kazer did you seen the picture? 22:14 #navit: <@KaZeR> jkoan: ah! i assumed that i was familiar with the problem. apologies! 22:14 #navit: <@KaZeR> i'm not convinced that this kind of filtering would be efficient to do in realtime, but i really hope that i'm wrong :) 22:30 #navit: < ilovekiruna> KaZeR: still no update :( 22:45 -!- charles__ [48241adf@gateway/web/freenode/ip.72.36.26.223] has joined #navit 22:46 #navit: < charles__> I found where the command strings are generated. navigation.c:get_distance_str. And I think I have the roadbook working for imperial. 22:46 #navit: < charles__> KaZeR: 22:50 #navit: < charles__> Also, there is code to display degrees as decimal degrees. Right click on a point, go to the top menu entry, "Point 0x...". You will see the lat and long in both dddmmss and d.ddddd... 23:13 #navit: < charles__> AAAAGGHHH! 23:14 #navit: < charles__> I just pulled in the western US from OpenStreetMapData, and converted it to a .bin file. My map is overlaid with straight lines that appear to be incorrectly rendered highways and roads. 23:39 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 240 seconds] 23:44 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit 23:59 #navit: <@KaZeR> hi charles__ --- Log closed Wed Nov 22 00:00:25 2017