--- Log opened Fri Nov 17 00:00:31 2017
00:14 -!- Horwitz [~mich1@p200300800E4F1900022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
00:28 -!- Horwitz [~mich1@p200300800E4B1800022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
00:28 -!- mode/#navit [+o Horwitz] by ChanServ
00:35 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
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:28 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 240 seconds]
01:35 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
06:00 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
07:27 -!- naggety [~naggety@241.red-37-158-1.dynamicip.rima-tde.net] has joined #navit
07:28 #navit: < jkoan> Hi naggety
07:29 #navit: < jkoan> What's up? :)
07:30 #navit: < naggety> Hi! How are you?
07:32 #navit: < jkoan> The morning was good except that the German train company has a delay so I couldn't catch my connecting train
07:32 #navit: < jkoan> But I used to time for navit so everything is okay
07:34 #navit: < jkoan> I read about the zip file format because of the map server which we will probably rewrite some time. I should not be to hard
07:41 #navit: < naggety> You mean to download .bin mapsets?
07:42 #navit: < jkoan> Correct, this software will probably be rewriten
07:47 #navit: < naggety> Great! That's very necessary
07:49 #navit: < naggety> And that reminds me a few things
07:50 #navit: < naggety> 1 - What about ticket #854
07:53 #navit: < naggety> 2 - Some areas appears blue but they're land and other appear brown but they're water
07:54 #navit: < naggety> Both are related to maptool
08:09 #navit: < jkoan> Yes, you are right, this is related to maptool not mapserver. The mapserver is basically a stream lined zip file reader
08:17 #navit: < naggety> I don't understand what it does, then
08:21 #navit: < naggety> https://www.dropbox.com/s/lnzqxmrbeunmhsm/IMG_20171117_090819_254.jpg?dl=0
08:21 #navit: < naggety> https://www.dropbox.com/s/3bl09qoubcx83bs/IMG_20171117_091003_111.jpg?dl=0
08:24 -!- god [817ebb4a@gateway/web/freenode/ip.129.126.187.74] has joined #navit
08:25 -!- god is now known as Guest88630
08:25 -!- Guest88630 [817ebb4a@gateway/web/freenode/ip.129.126.187.74] has quit [Client Quit]
08:48 #navit: < jkoan> i think this bug is due to maptool (as you said before) but what i was talking about is the mapserver (the software behind maps.navit-project.org) and this need to be rewritten not the maptool. But of cause we need to look also in this bug 
08:50 #navit: < naggety> yes yes, but I say that I don't know what the mapserver does
08:50 #navit: < naggety> Ah ok, I see. It extract an area from OSM
08:50 #navit: < naggety> In what format?
08:55 #navit: < jkoan> the download format from the mapserver are in a ready to use binfile
08:57 #navit: < naggety> so it also use maptool?
09:39 #navit: < jkoan> yes. The mapserver only accesses the original planet.bin file which was provided by maptool.
09:40 #navit: < naggety> what is that planet.bin file?
09:42 #navit: < jkoan> did you already tryed to use maptool with the experimental features? (this could fix your problem)
09:43 #navit: < jkoan> planet.bin is a binfile with the total planet included 
09:43 #navit: < naggety> Yes. The experimental feature (modified by me) solves a different problem: the coastlines rendering. But this seems a different problem, that only happens in some specific places.
09:45 #navit: < naggety> In the bug tracker someone said that it could be related to some "bugs" in OSM data (unclosed coastlines, for example). But the fact is that in OSM this doesn't happen, so maptool can't handle the same data as well as OSM.
09:47 #navit: < naggety> about mapserver: ok now I get how it works
09:47 #navit: < jkoan> okay, but i dont have time to look into maptool :X
09:48 #navit: < naggety> ah, no, I was just commenting, not to be done now
09:48 #navit: < naggety> haha
09:49 #navit: < jkoan> okay ^^
09:50 #navit: < jkoan> how is your project going, any new informations like release date or something like this? ^^
09:51 #navit: < naggety> It's going well. Now I'm tweaking navit with custom OSDs and custom menu GUI to be easier to use
09:51 #navit: < jkoan> nice :)
09:52 #navit: < jkoan> gtk or qt? :X
09:52 #navit: < naggety> I hope next week it's almost ready
09:52 #navit: < naggety> gtk, I have tried a few times with qt. In the computer some OSD elements didn't work, and for my device I wasn't able to build it
09:53 #navit: < jkoan> will you use upstream navit or a own fork?
09:53 #navit: < naggety> I want to use upstream
09:54 #navit: < jkoan> nice
09:54 #navit: < naggety> Maintaining my own fork would be much harder
09:54 #navit: < jkoan> yes, i agree
09:55 #navit: < jkoan> how do you solve the updating? 
09:55 #navit: < naggety> good question
09:56 #navit: < naggety> that will depend on the whole system, also
09:56 #navit: < naggety> and there is much work to do with that. As I told you, the product is not just a GPS navigator. The navigator is just an "app" inside the whole system.
09:57 #navit: < naggety> And I'm not taking care of the rest of the system for the moment, so I don't know
09:59 #navit: < jkoan> but you have a complected computer. So the other apps are not on the same device?
09:59 #navit: < naggety> The device as a dual core ARM processor
09:59 #navit: < naggety> running Linux
10:00 #navit: < naggety> The device has (*)
10:00 #navit: < naggety> So there is not a connected computer. It's standalone.
10:00 #navit: < naggety> With system I meant the OS, the other apps and programs...
10:01 #navit: < jkoan> yes, but the apps and your buildroot are on the same device?
10:01 #navit: < naggety> Yes
10:01 #navit: < naggety> With buildroot we bundle the OS and all apps/programs
10:02 #navit: < naggety> There is no package manager such as apt
10:02 #navit: < jkoan> but you are not the person which should bring all things together?
10:02 #navit: < jkoan> i know that buildroot has no package manager
10:02 #navit: < naggety> For the moment no. Maybe later my boss tell me to work on it...
10:04 #navit: < jkoan> hm okay, one idea would be not to use buildroot and swich to alpin linux with a own repo (for example)
10:05 #navit: < jkoan> this would have a own package manager
10:07 #navit: < naggety> Interesting, I didn't know it. However, I don't think we are going to change this now.
10:07 #navit: < naggety> Additionally, with buildroot you can add a package manager too
10:07 #navit: < jkoan> yes, but this is not really nice...
10:08 #navit: < naggety> why?
10:08 #navit: < jkoan> probably you need to write a own script
10:08 #navit: < jkoan> because the package manager does not know about the things buildroot does
10:09 #navit: < naggety> As far as I know (I may be mistaken) buildroot doesn't do anything after compiling the system
10:10 #navit: < jkoan> yes that is right
10:12 #navit: < jkoan> probably a script which writes download a new system image and writes it to rom and then reboots?
10:12 #navit: < jkoan> but then it would be goot to have something like a recovery (probably u-boot with usb boot)
10:13 #navit: < naggety> I was thinking something similar, yes, but probably the device is not going to be connected to the internet (it is capable, though), so I will have to be done manually.
10:14 #navit: < jkoan> yes, but for updates you only have two options (as far as i know) physical connection (plug in a usb stick with a update file) or internet update service.
10:15 #navit: < jkoan> to have both would be really good
10:18 #navit: < naggety> correct
10:20 #navit: < jkoan> do you have something like a boot loader 
10:20 #navit: < jkoan> ?
10:20 #navit: < naggety> u-boot
10:20 #navit: < jkoan> nice
10:21 #navit: < jkoan> so it should also be possible so provide a rescue over usb drive
10:22 #navit: < naggety> It can be easier than that, too: everything is installed in an SD-card (bootloader, OS, programs...). It's enought to extract it, reflash it, and insert it again.
10:23 #navit: < jkoan> hm okay, but online update would be more nice for the user
10:24 #navit: < naggety> Yes, but as I say, probably it won't be connected to the internet.
10:24 #navit: < jkoan> okay
10:25 #navit: < naggety> It's a product for buses, so probably updates will be done by a technician of the company......if they're done
10:26 #navit: < naggety> but obviously, I agree, online update would be great
10:27 #navit: < jkoan> so you are not planing to provide also a consumer variant? ;)
10:27 #navit: < naggety> We would like to but that's much more difficult
10:28 #navit: < naggety> Many competitors
10:28 #navit: < jkoan> why? only a case is needed :P
10:29 #navit: < naggety> haha
10:29 #navit: < naggety> and a commercial network to sell it <- that's the difficult part
10:29 #navit: < naggety> for buses we already have clients, and there are much less products specific for buses
10:29 #navit: < jkoan> amazon? ^^
10:30 #navit: < naggety> I will give your contact to my boss, and you convince him
10:30 #navit: < naggety> be enthusiastic
10:30 #navit: < naggety> XD
10:30 #navit: < jkoan> no ^^
10:30 #navit: < naggety> haha
10:34 #navit: < jkoan> but if you have everything ready you could give it a try on kickstarted and only if its founded you produces it, this would also give you customers and promotion
10:37 #navit: < naggety> I think we are an old fashioned company. I don't think that this "modern" ideas like to my boss.
10:40 #navit: < jkoan> was it difficult to convince him to use navit and linux?
10:42 #navit: < naggety> Not so much.........because we save LOTS of money
10:44 #navit: < jkoan> ah okay ^^
10:46 #navit: < naggety> haha. I'm afraid that people have to know where they are working.
10:49 #navit: < jkoan> i dont understand what you mean
10:50 #navit: < naggety> I mean that I try to convince my boss about inovating, but I know him and the company, and there are things that they're not going to listen, at least for now.
10:53 #navit: < jkoan> ah okay :/ i know the same thing somethimes
10:53 #navit: < jkoan> *sometimes 
12:15 #navit: < naggety> anybody knows what has the profile car_pedantic different to other profiles?
13:15 #navit: < naggety> and another question: when "follow_cursor=1", if the user drags the map, it is centered to vehicle position according to "timeout". Is there any commands that resumes following the vehicle immediately?
13:17 #navit: < naggety> I found "set_center_cursor", but it just move the map to the current vehicle position, but it don't resume following it.
14:01 -!- naggety [~naggety@241.red-37-158-1.dynamicip.rima-tde.net] has quit [Quit: Konversation terminated!]
15:42 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
15:54 -!- ZeroOne [~ZeroOne@91.114.11.118] has joined #navit
15:57 -!- noradtux [~noradtux@2a02:2028:554:bf01:ec4:7aff:fe33:3dc1] has quit [Ping timeout: 240 seconds]
16:03 -!- noradtux [~noradtux@2a02:2028:73a:f501:ec4:7aff:fe33:3dc1] has joined #navit
16:03 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
16:20 -!- ZeroOne [~ZeroOne@91.114.11.118] has quit [Read error: Connection reset by peer]
17:09 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Ping timeout: 260 seconds]
18:13 -!- youte [~youte@AStrasbourg-551-1-157-75.w86-235.abo.wanadoo.fr] has quit [Ping timeout: 240 seconds]
18:18 -!- MarcR [~marc@p5DD92651.dip0.t-ipconnect.de] has joined #navit
18:18 #navit: < MarcR> Hi Guys
19:50 -!- frank [~frank@134.97.168.107] has joined #navit
19:56 #navit: <@KaZeR> hi there
20:05 #navit: < MarcR> hi KaZeR 
20:05 #navit: < frank> Hi folks
20:05 #navit: < MarcR> hi frank 
20:06 #navit: <@KaZeR> naggety | Not so much.........because we save LOTS of money : you guys can still sponsor us on opencollective ;)
20:07 #navit: <@KaZeR> naggety | anybody knows what has the profile car_pedantic different to other profiles? : it uses a deeper graph for routing and try to be more accurate at the cost of more cpu/memory usage
20:07 #navit: <@KaZeR> with today's resources, it shouldn't be an issue though
20:07 #navit: <@KaZeR> naggety | and another question: when "follow_cursor=1", if the user drags the map, it is centered to vehicle position according to "timeout". Is there any commands that resumes         │
20:07 #navit: <@KaZeR>                      | following the vehicle immediately? 
20:08 #navit: <@KaZeR> -> how about timeout = 1 ? check out the "refresh" parameter too
20:08 #navit: <@KaZeR> and i'm caught up on the backlog, yay!
20:08 #navit: <@KaZeR> 'sup guys?
20:15 #navit: < MarcR> playing around with an usb sound card right now, to get a mic in and maybe a better sound output 
20:24 #navit: <@KaZeR> cool
20:25 #navit: < MarcR> hmmm, it works under kodi .... but not as default sound at all ... :-( 
20:26 #navit: <@KaZeR> aplay -l; aplay -L; and a ~/.asoundrc file should help
20:33 #navit: < MarcR> hmm 
20:35 #navit: < MarcR> in asoundrc the default card is the usb card , I could bet, that it is not configured right, because it is a 5.1 sound card :P so I have front rear and all the other stuff that you have with surround 
20:43 #navit: <@KaZeR> not sure i understand your exact issue
20:43 #navit: < MarcR> no problem 
20:43 #navit: < MarcR> i think i nearly have it ;) 
20:44 #navit: < MarcR> ok nearly 
20:45 #navit: < MarcR> speaker test takes the right sound card now, but espeak doesn't 
20:46 #navit: <@KaZeR> do you specify a device with speaker test?
20:49 #navit: < MarcR> nope
20:59 -!- youte [~youte@se371-1-88-189-105-1.fbx.proxad.net] has joined #navit
21:15 #navit: < MarcR> KaZeR: did you had a chance to take a look at my updates for the speech wiki page ? 
21:16 #navit: <@KaZeR> yep, i receive email notification when there's updates on the wiki :)
21:16 #navit: <@KaZeR> thanks for taking care of that!
21:16 #navit: < MarcR> ah ok, but you didn't get 10 emails because i updated it 10 times or more? ;-) 
21:17 #navit: < MarcR> no problem
21:22 #navit: < MarcR> hmm, with the alsa audio gui tool, I have made it work 
21:23 #navit: < MarcR> but not via config files :'-(
21:25 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
21:38 #navit: < MarcR> yeap, it works ... 
21:39 #navit: < MarcR> now I have to find a way, how I can mount the screen in my car, without damaging the dashboard 
21:40 #navit: < MarcR> for testing and fine tuning navit 
21:59 #navit: < MarcR> KaZeR: is there a way I can turn of the screen saver while navit is in navigation mode? or navit is active at all? 
21:59 #navit: < MarcR> navit is active = screensaver is inactive / navit is inactive = screensaver active 
22:22 -!- youte [~youte@se371-1-88-189-105-1.fbx.proxad.net] has quit [Ping timeout: 248 seconds]
22:22 #navit: <@KaZeR> MarcR: no, updates are grouped by page, don't worry :)
22:25 #navit: <@KaZeR> i don't have a screensaver installed in my car. To prevent screen blanking, i use "xset s off" and "xset -dpms" in my xinitrc
22:25 #navit: <@KaZeR> we could probably have navit do that for you and make it configurable, but it's also quite easy to do it via .xinitrc
22:32 #navit: < MarcR> I will turn of the screensaver - no problem
22:40 #navit: < MarcR> maybe this could be a nice to have option at all ? 
22:40 #navit: < MarcR> "turn off screensaver, while Navit is active" 
22:41 #navit: < MarcR> or "turn off screensaver, while a route in navit is active" 
22:44 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
22:49 #navit: <@KaZeR> we do have it for other platforms like mobile devices
22:49 #navit: <@KaZeR> we could add that easily for linux i think
22:50 #navit: < MarcR> that was one point, that I have noticed at first, at my first on road tests 
22:52 #navit: < MarcR> navit was on, and navigation was active. want to take a look at the screen, because there was no announment, and .. upsi screen black, because of screensaver ;) 
23:10 #navit: <@KaZeR> ha yeah :) this won't happen with the qt5 image, as it doesn't even need X
23:13 #navit: < MarcR> :)
23:14 #navit: < MarcR> I will give the qt5 image a try later :) 
23:21 #navit: < MarcR> see you later! Have a good sleep! 
23:22 -!- MarcR [~marc@p5DD92651.dip0.t-ipconnect.de] has quit [Quit: Verlassend]
23:35 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 248 seconds]
23:35 -!- youte [~youte@AStrasbourg-551-1-157-75.w86-235.abo.wanadoo.fr] has joined #navit
23:42 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
23:55 #navit: < ilovekiruna> hi all
--- Log closed Sat Nov 18 00:00:33 2017