--- Log opened Sun Mar 29 00:00:23 2015
01:14 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
04:14 -!- KaZeR [~KaZeR@50-1-102-131.dsl.dynamic.fusionbroadband.com] has joined #navit
04:14 -!- mode/#navit [+o KaZeR] by ChanServ
05:07 -!- KaZeR [~KaZeR@50-1-102-131.dsl.dynamic.fusionbroadband.com] has quit [Ping timeout: 265 seconds]
06:06 -!- xenos1984 [~xenos1984@43-29-196-88.dyn.estpak.ee] has joined #navit
06:34 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has joined #navit
07:14 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 255 seconds]
07:55 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds]
08:08 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has joined #navit
09:45 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has quit [Ping timeout: 272 seconds]
09:58 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has joined #navit
10:00 -!- tim0123 [5edf8d81@gateway/web/freenode/ip.94.223.141.129] has joined #navit
10:14 #navit: < tim0123> Hi! Is it possible to create a layout which renders a map similar to opencyclemap.org?
10:38 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds]
10:52 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has joined #navit
11:05 -!- tryagain [~quassel@178.216.76.44] has joined #navit
11:13 #navit: < tryagain> tim0123 Short answer would be "yes, layouts are fully configurable".
11:13 #navit: < tryagain> Though navit at map processing time (by maptool) converts osm tags to navit's own item types, and some information might be lost at that time.
11:13 #navit: < tryagain> We could change maptool if you point such missing infos.
11:16 -!- drlizau [~liz@billiau.net] has quit [Remote host closed the connection]
11:32 -!- robertp [5b2a8ccf@gateway/web/freenode/ip.91.42.140.207] has joined #navit
11:38 #navit: < Navit> mdankov * r6033 /trunk/navit/navit/debug.c: Fix:port_android:Do not catch SIGSEGV because catching it breaks Lollipop NullPointerException handling. http://sourceforge.net/p/navit/code/6033/
11:45 -!- robertp [5b2a8ccf@gateway/web/freenode/ip.91.42.140.207] has quit [Quit: Page closed]
11:55 #navit: < tryagain> navit, compile
11:55 #navit: < tryagain> Navit, compile
11:55 #navit: < tryagain> Navit, jump
11:56 -!- Navit [~Navit@www.v6.navit-project.org] has quit [Quit: Coyote finally caught me]
11:56 -!- Navit [~Navit@www.v6.navit-project.org] has joined #navit
11:56 #navit: < Navit> Hi!
11:56 #navit: < tryagain> Navit, jump
11:56 #navit: < Navit> How high?
11:56 #navit: < tryagain> Navit, compile
11:56 #navit: < Navit> Starting compiler
12:00 #navit: < tim0123> tryagin, the cycle routes in osm are relations with several properties. Are these relations thrown away by maptool?
12:02 #navit: < tim0123> for example http://www.openstreetmap.org/relation/1727037
12:06 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds]
12:08 #navit: < tryagain> We process only a few selected types of relations, and do not consider bicycle routes right now...
12:10 #navit: < tim0123> i see. What kind of relations are processed at the moment?
12:11 #navit: < tryagain> administrative boundaries and associated streets
12:14 #navit: < tryagain> How would you like to use this data? Just to display the map? I guess we should somehow consider it when building routes for bicycle.
12:17 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has joined #navit
12:19 #navit: < tim0123> I'm only interested in displaying the cycle paths on the map.
12:23 #navit: < tryagain> you may post the feature request on trac.navit-project.org so that somebody would implement it. But i really think we would consider using that data in routing, so you'll  be able to be guided through the selected route.
12:23 #navit: < tryagain> btw,  if you have some C coding experience, you might do it yourself ;)
12:27 #navit: < tim0123> using the information for routing is also a good idea, but we have to think how this should really work. In some cases you might not want to use the cycle paths in other cases only international paths and no local paths etc. I think there are many things to consider.
12:30 #navit: < tim0123> I'm just browsing around the code, maybe I'll do something if it's not too much effort.
12:33 #navit: < tryagain> great!
12:35 -!- noradtux [~noradtux@2a02:8108:28bf:fc94::1] has quit [Quit: Bye]
12:43 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds]
12:46 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has joined #navit
12:52 #navit: < Navit> Compilation successful
12:53 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
13:01 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
14:33 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
14:41 -!- jandegr [57415ecd@gateway/web/freenode/ip.87.65.94.205] has joined #navit
15:15 -!- tryagain_ [~nobody@217.118.95.125] has joined #navit
15:15 #navit: < tryagain_> jandegr: hi
15:15 #navit: < jandegr> hi tryagain
15:16 #navit: < jandegr> great you could fix #1287
15:16 #navit: < tryagain_> have you already tried the new experimental map?
15:16 #navit: < jandegr> you mean with coastlines ?
15:17 #navit: < tryagain_> yep, quite obvious failure. after we know the fix ;)
15:17 #navit: < tryagain_> yes coastlines
15:17 #navit: < tryagain_> have to go
15:18 -!- tryagain_ [~nobody@217.118.95.125] has quit [Client Quit]
16:02 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has joined #navit
16:22 -!- pini [~pini@bou-fi.pustule.org] has quit [Read error: Connection reset by peer]
16:35 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
16:58 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds]
16:59 -!- pini [~pini@bou-fi.pustule.org] has quit [Read error: Connection reset by peer]
16:59 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
17:13 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has joined #navit
17:28 -!- jandegr [57415ecd@gateway/web/freenode/ip.87.65.94.205] has quit [Quit: Page closed]
17:44 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 252 seconds]
18:09 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has quit [Ping timeout: 248 seconds]
18:14 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has joined #navit
18:25 #navit: < Navit> mdankov * r6034 /trunk/navit/navit/android/src/org/navitproject/navit/NavitMapDownloader.java: Fix:port_android:Adjust map sizes reported in Map Download menu to reflect current planet.bin contents. http://sourceforge.net/p/navit/code/6034/
18:28 #navit: < Navit> mdankov * r6035 /trunk/navit/navit/android/src/org/navitproject/navit/NavitDownloadSelectMapActivity.java: Fix:port_android:Do not allow to download maps above 1.8G, as android build is currently unable to process them. http://sourceforge.net/p/navit/code/6035/
18:28 #navit: < tryagain> Navit, compile
18:28 #navit: < Navit> Starting compiler
19:24 #navit: < Navit> Compilation successful
19:24 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
19:59 -!- jjelen [~jjelen@ip4-95-82-163-69.cust.nbox.cz] has joined #navit
20:15 -!- drlizau [~liz@billiau.net] has joined #navit
20:41 -!- noradtux [~noradtux@2001:470:51e7:1::1] has joined #navit
20:50 -!- _rd [~rd@p4FD1C114.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds]
21:04 -!- xenos1984 [~xenos1984@43-29-196-88.dyn.estpak.ee] has quit [Quit: Leaving.]
21:20 -!- jjelen [~jjelen@ip4-95-82-163-69.cust.nbox.cz] has quit [Ping timeout: 272 seconds]
21:39 -!- KaZeR [~KaZeR@172.56.38.26] has joined #navit
21:39 -!- mode/#navit [+o KaZeR] by ChanServ
21:51 -!- KaZeR [~KaZeR@172.56.38.26] has quit [Remote host closed the connection]
21:52 -!- KaZeR [~KaZeR@172.56.38.26] has joined #navit
21:52 -!- mode/#navit [+o KaZeR] by ChanServ
21:56 -!- KaZeR [~KaZeR@172.56.38.26] has quit [Ping timeout: 250 seconds]
22:55 -!- KaZeR [~KaZeR@172.56.38.156] has joined #navit
22:55 -!- mode/#navit [+o KaZeR] by ChanServ
23:01 -!- tryagain [~quassel@178.216.76.44] has quit [Remote host closed the connection]
23:29 -!- tim0123 [5edf8d81@gateway/web/freenode/ip.94.223.141.129] has quit [Ping timeout: 246 seconds]
--- Log closed Mon Mar 30 00:00:23 2015