--- Log opened Tue Sep 15 00:00:07 2015
00:20 -!- juse19 [~juse@fow4.kyla.fi] has quit [Ping timeout: 244 seconds]
01:01 -!- _rd [~rd@p4FD1E0BC.dip0.t-ipconnect.de] has joined #navit
01:12 -!- juse19 [~juse@wireless-86-50-147-44.open.aalto.fi] has joined #navit
01:15 -!- _rd [~rd@p4FD1E0BC.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
01:24 -!- _rd [~rd@p4FD1E0BC.dip0.t-ipconnect.de] has joined #navit
01:26 -!- juse110 [~juse@wireless-86-50-147-44.open.aalto.fi] has joined #navit
01:27 -!- juse111 [~juse@85-76-18-83-nat.elisa-mobile.fi] has joined #navit
01:28 -!- juse19 [~juse@wireless-86-50-147-44.open.aalto.fi] has quit [Ping timeout: 255 seconds]
01:30 -!- juse110 [~juse@wireless-86-50-147-44.open.aalto.fi] has quit [Ping timeout: 272 seconds]
01:42 -!- _rd [~rd@p4FD1E0BC.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
01:43 -!- juse112 [~juse@85-76-18-83-nat.elisa-mobile.fi] has joined #navit
01:44 -!- juse113 [~juse@85-76-18-83-nat.elisa-mobile.fi] has joined #navit
01:45 -!- juse111 [~juse@85-76-18-83-nat.elisa-mobile.fi] has quit [Ping timeout: 244 seconds]
01:47 -!- juse112 [~juse@85-76-18-83-nat.elisa-mobile.fi] has quit [Ping timeout: 246 seconds]
02:26 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has joined #navit
02:49 -!- juse113 [~juse@85-76-18-83-nat.elisa-mobile.fi] has quit [Quit: Nettalk6 - www.ntalk.de]
02:54 -!- jjelen [jjelen@nat/redhat/x-ehzjdmhajqbhxvmq] has joined #navit
03:29 -!- xenos1984 [~xenos1984@127-166-191-90.dyn.estpak.ee] has joined #navit
04:50 -!- _rd [~rd@p4FD1E0BC.dip0.t-ipconnect.de] has joined #navit
04:59 -!- _rd [~rd@p4FD1E0BC.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
05:02 -!- _rd [~rd@p4FD1E0BC.dip0.t-ipconnect.de] has joined #navit
05:24 -!- _rd [~rd@p4FD1E0BC.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds]
05:35 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has quit [Ping timeout: 246 seconds]
06:31 -!- Netsplit *.net <-> *.split quits: xenoxaos
06:33 -!- Netsplit over, joins: xenoxaos
07:10 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has joined #navit
11:05 -!- jandegr [5bb55056@gateway/web/freenode/ip.91.181.80.86] has joined #navit
11:41 -!- _rd [~rd@p57A0FC11.dip0.t-ipconnect.de] has joined #navit
11:51 -!- _rd [~rd@p57A0FC11.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds]
11:58 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has quit [Ping timeout: 246 seconds]
12:02 -!- _rd [~rd@p57A0FC11.dip0.t-ipconnect.de] has joined #navit
12:07 #navit: <@KaZeR> hi there
12:24 -!- jjelen [jjelen@nat/redhat/x-ehzjdmhajqbhxvmq] has quit [Ping timeout: 246 seconds]
12:40 -!- _rd [~rd@p57A0FC11.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
12:40 #navit: < tryagain> f-droid has an updated navit version now https://f-droid.org/repository/browse/?fdfilter=navit&fdid=org.navitproject.navit
12:41 #navit: < tryagain> afk
12:41 -!- _rd [~rd@p57A0FC11.dip0.t-ipconnect.de] has joined #navit
12:58 #navit: <@KaZeR> yay!
13:08 -!- _rd [~rd@p57A0FC11.dip0.t-ipconnect.de] has quit [Ping timeout: 268 seconds]
13:23 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
13:24 -!- tryagain_ [~nobody@217.118.95.124] has joined #navit
13:26 #navit: < tryagain_> KaZeR, i have a few minutes to discuss interpolation
13:28 #navit: < tryagain_> do you have osm way id which doesnt work?
13:28 -!- _rd [~rd@p57A0FC11.dip0.t-ipconnect.de] has joined #navit
13:29 #navit: <@KaZeR> actually i also asked jandegr
13:30 #navit: <@KaZeR> from recent experience, almost everywhere. give me a sec
13:31 #navit: < tryagain_> iirc jandegr was the author
13:32 #navit: <@KaZeR> author of what?
13:33 #navit: <@KaZeR> tryagain_: i think that https://www.openstreetmap.org/way/190255052 is the one
13:34 #navit: < tryagain_> of interpolation code. probably i'm wrong and that was sleske
13:35 #navit: < tryagain_> i see no interpolation tags on that way...
13:36 #navit: <@KaZeR> it can definitely be an issue in the map. actually it most probably is. but this issue is really common here, so i hope that we can figure some kind of automated way to address it
13:36 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 256 seconds]
13:38 #navit: < tryagain_> hm, how do you think addr interpolation works?
13:39 #navit: < tryagain_> we do not make house numbers of the air
13:39 #navit: < tryagain_> we use a way tagged with addr:interpolation
13:40 #navit: <@KaZeR> from my understanding, the map says "this segment contains numbers 50-100" and then we split the values along the segment
13:40 #navit: <@KaZeR> correct?
13:40 #navit: < tryagain_> yep
13:40 #navit: < tryagain_> but segment you have shown says nothing
13:44 #navit: <@KaZeR> i can fix this one, but i'd like to find a way to fix that on a more global scale :)
13:45 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
13:46 #navit: < tryagain_> hey addr interpolation is already for the lazy people not caring to map each individual house
13:47 #navit: <@KaZeR> i could understand why people would not want to map each individual house :)
13:49 #navit: < tryagain_> in some places there are
13:49 #navit: < tryagain_> lags in numbering
13:50 #navit: < tryagain_> simply they have house #13 built over demolished houses 3-21
13:51 #navit: <@KaZeR> ok. in the example i gave you, i was over a kilometer away from the right address
13:51 #navit: < tryagain_> theres no way to know it without visiting the ground
13:51 #navit: <@KaZeR> yeah i understand that
13:52 #navit: < tryagain_> did navit suggest you a wrong place for that address?
13:53 #navit: < tryagain_> or just no suggestion?
13:54 #navit: < tryagain_> we probably could display in search results some nearby addresses in numeric sense if theres no exact match found
13:56 -!- _rd [~rd@p57A0FC11.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
13:56 #navit: < tryagain_> but thats a feature request, not a bug report ;)
14:04 #navit: <@KaZeR> well. that + the UI/UX makes it a bug :) the UI is not clear on the fact that it does not really know where to drive you to :)
14:05 #navit: < tryagain_> afk
14:06 #navit: <@KaZeR> ok
14:09 -!- tryagain_ [~nobody@217.118.95.124] has quit [Remote host closed the connection]
14:32 -!- _rd [~rd@p57A0FC11.dip0.t-ipconnect.de] has joined #navit
14:42 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 246 seconds]
14:57 -!- jandegr [5bb55056@gateway/web/freenode/ip.91.181.80.86] has quit [Quit: Page closed]
15:00 -!- _rd [~rd@p57A0FC11.dip0.t-ipconnect.de] has quit [Ping timeout: 244 seconds]
15:03 -!- _rd [~rd@p57A0FC11.dip0.t-ipconnect.de] has joined #navit
15:50 -!- _rd [~rd@p57A0FC11.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds]
16:01 -!- _rd [~rd@p57A0FC11.dip0.t-ipconnect.de] has joined #navit
16:11 -!- _rd [~rd@p57A0FC11.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
16:17 -!- _rd [~rd@p57A0FC11.dip0.t-ipconnect.de] has joined #navit
18:10 -!- _rd [~rd@p57A0FC11.dip0.t-ipconnect.de] has quit [Ping timeout: 272 seconds]
18:20 -!- circleci-bot [~circleci-@ec2-54-197-146-233.compute-1.amazonaws.com] has joined #navit
18:20 #navit: < circleci-bot> Success: pgrandin's build (#615; push) in navit-gps/navit (master) -- https://circleci.com/gh/navit-gps/navit/615
18:20 -!- circleci-bot [~circleci-@ec2-54-197-146-233.compute-1.amazonaws.com] has quit [Client Quit]
18:26 #navit: < tryagain> KaZeR i seem to have missed your reply "well. that + the UI/UX makes it a bug :) the UI is not clear on the fact that it does not really know where to drive you to :)"
18:28 #navit: < tryagain> what ui do you talk about? In internal gui Town search? Or in Android native search dialog? Internal gui works fine forme, showing no results at all.
20:30 -!- Marc0_ [~marco@mx.hidden-primary.net] has joined #navit
20:36 -!- Netsplit *.net <-> *.split quits: Marc0, chille
20:42 -!- Netsplit over, joins: chille
20:44 -!- xenos1984 [~xenos1984@127-166-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
22:28 -!- Netsplit *.net <-> *.split quits: chille
22:34 -!- Netsplit over, joins: chille
--- Log closed Wed Sep 16 00:00:08 2015