--- Log opened Mon Oct 26 00:00:08 2015
02:50 -!- xenos1984 [~xenos1984@127-166-191-90.dyn.estpak.ee] has joined #navit
03:00 -!- circleci-bot [~circleci-@ec2-54-196-147-5.compute-1.amazonaws.com] has joined #navit
03:00 #navit: < circleci-bot> Success: jandegr's build (#657; push) in navit-gps/navit (trunk) -- https://circleci.com/gh/navit-gps/navit/657
03:00 -!- circleci-bot [~circleci-@ec2-54-196-147-5.compute-1.amazonaws.com] has quit [Client Quit]
03:12 -!- circleci-bot [~circleci-@ec2-54-158-186-253.compute-1.amazonaws.com] has joined #navit
03:12 #navit: < circleci-bot> Success: pgrandin's build (#658; push) in navit-gps/navit (master) -- https://circleci.com/gh/navit-gps/navit/658
03:12 -!- circleci-bot [~circleci-@ec2-54-158-186-253.compute-1.amazonaws.com] has quit [Client Quit]
03:33 -!- RobertP [d9f3f0ac@gateway/web/freenode/ip.217.243.240.172] has joined #navit
03:35 #navit: < RobertP> hi
03:42 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has joined #navit
03:52 -!- epy [~epy@2a02-8429-80f2-1501-3e97-0eff-feaa-374d.rev.sfr.net] has joined #navit
04:20 -!- pini [~pini@bou-fi.pustule.org] has quit [Read error: Connection reset by peer]
04:22 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
05:20 -!- jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #navit
06:06 -!- zoff99 [~chatzilla@unaffiliated/zoff99] has joined #navit
08:11 -!- jjelen [jjelen@nat/redhat/x-ynwluwybptddeumc] has joined #navit
09:42 -!- epy [~epy@2a02-8429-80f2-1501-3e97-0eff-feaa-374d.rev.sfr.net] has quit [Ping timeout: 256 seconds]
10:06 -!- RobertP [d9f3f0ac@gateway/web/freenode/ip.217.243.240.172] has quit []
10:10 -!- zoff99 [~chatzilla@unaffiliated/zoff99] has quit [Quit: ChatZilla 0.9.86-rdmsoft [XULRunner 1.9.1/20090707221522]]
10:16 -!- circleci-bot [~circleci-@ec2-54-234-54-1.compute-1.amazonaws.com] has joined #navit
10:16 #navit: < circleci-bot> Success: mvglasow's build (#660; push) in navit-gps/navit (trunk) -- https://circleci.com/gh/navit-gps/navit/660
10:16 -!- circleci-bot [~circleci-@ec2-54-234-54-1.compute-1.amazonaws.com] has quit [Client Quit]
10:17 -!- circleci-bot [~circleci-@ec2-54-161-207-142.compute-1.amazonaws.com] has joined #navit
10:17 #navit: < circleci-bot> Success: mvglasow's build (#659; push) in navit-gps/navit (pull/32) -- https://circleci.com/gh/navit-gps/navit/659
10:17 -!- circleci-bot [~circleci-@ec2-54-161-207-142.compute-1.amazonaws.com] has quit [Client Quit]
10:27 -!- circleci-bot [~circleci-@ec2-54-157-151-243.compute-1.amazonaws.com] has joined #navit
10:27 #navit: < circleci-bot> Success: pgrandin's build (#661; push) in navit-gps/navit (master) -- https://circleci.com/gh/navit-gps/navit/661
10:27 -!- circleci-bot [~circleci-@ec2-54-157-151-243.compute-1.amazonaws.com] has quit [Client Quit]
10:53 -!- epy [~epy@2a02-8400-0114-0701-3e97-0eff-feaa-374d.rev.sfr.net] has joined #navit
11:38 -!- epy [~epy@2a02-8400-0114-0701-3e97-0eff-feaa-374d.rev.sfr.net] has quit [Ping timeout: 252 seconds]
12:00 -!- epy [~epy@174.249.0.109.rev.sfr.net] has joined #navit
12:34 -!- epy [~epy@174.249.0.109.rev.sfr.net] has quit [Quit: Quitte]
12:48 -!- jandegr [5741586c@gateway/web/freenode/ip.87.65.88.108] has joined #navit
12:54 -!- RobertP [5cd9e7ab@gateway/web/freenode/ip.92.217.231.171] has joined #navit
13:03 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has quit [Ping timeout: 246 seconds]
13:05 -!- mvglasow [4d0dbe32@gateway/web/freenode/ip.77.13.190.50] has joined #navit
13:05 #navit: < mvglasow> hi kazer
13:06 #navit: < mvglasow> did you manage to have a look at #1324 yet?
13:23 -!- jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Ex-Chat]
13:49 -!- jjelen [jjelen@nat/redhat/x-ynwluwybptddeumc] has quit [Quit: Leaving]
14:15 #navit: < RobertP> I have aquestion, again: How is the map rendered? I ask because I think that navit prints the street names way too often. Once or twice per visible street would be enough - im my opinion. Its no major thing, but i feel it looks unprofessional.
14:18 #navit: < RobertP> Here is a picture: http://pasteboard.co/1FA2EZZL.png The Autobahn labels A39 and A2 are printed very often.
14:54 -!- tryagain [~quassel@178.216.76.75] has joined #navit
14:55 #navit: < tryagain> RobertP Hi
14:56 #navit: < tryagain> Navit just attempts to put name on every street segment. It splits every street on every crossing to form segments.
14:56 #navit: < tryagain> And doesn't attempt to merge them back.
14:57 #navit: < RobertP> Would it be possible to count the occurences of the same street name to prevent that?
14:59 #navit: < RobertP> Is probably a bad idea... all names would be at the same side of the screen
15:05 #navit: < tryagain> actually it should not be not too hard (both computationally and to code) to merge connected segments with the same name and of the same type. That would allow much more perfect look, and allow to draw names where it's not possible now
15:48 #navit: < mvglasow> RobertP, tryagain: I opened a ticket for that a while back: http://trac.navit-project.org/ticket/1251
15:49 #navit: < mvglasow> one issue is with segmentation itself: Navit splits OSM ways into segments wherever a point is shared by multiple ways
15:49 #navit: < mvglasow> i.e. crossroads, splits and similar
15:50 #navit: < mvglasow> currently this also happens when a road and a non-routable way (such as the boundary of a forest) share a node
15:51 #navit: < mvglasow> the worst case is when a road adjacent to a forest makes a long turn and the mapper has decided to have the road and the forest share the same nodes
15:52 #navit: < mvglasow> the difficulty is that routability is not set in stone: it is determined dynamically by the vehicleprofile
15:58 -!- jandegr [5741586c@gateway/web/freenode/ip.87.65.88.108] has quit [Quit: Page closed]
16:12 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 256 seconds]
16:41 #navit: < tryagain> mvglasow iirc all routable items are defined in item.c inside struct default_flags default_flags2[] array.
16:42 #navit: < tryagain> i think i've hit once a problem with unability to route over a road not in that array
16:46 #navit: < mvglasow> tryagain maybe, I didn't look in detail into how routability is determined
16:47 #navit: < mvglasow> but I have encountered a road some time ago that shared nodes with a landuse polygon and the road was completely segmented, despite being a single way in OSM
16:49 #navit: < tryagain> yeah, it's the way the split works: it does not distinguish item types. But i think it shouldnt be a very common case...
16:49 #navit: < RobertP> mvglasow: Could you point me to the code, where the decision is made where to draw the text element?
16:49 #navit: < tryagain> https://github.com/navit-gps/navit/blob/trunk/navit/graphics.c#L1165
16:51 #navit: < RobertP> thanks. ;)
16:51 #navit: < mvglasow> RobertP: sorry, I don't know my way around that part of the code particularly well
16:51 #navit: < RobertP> np. me neither.
16:52 #navit: < tryagain> we could start making it split item label into pieces to fit parts over complete way instead of attempting to fit whole label to each segment separately
16:55 #navit: < tryagain> also, some way simplification could be done at that point
16:57 #navit: < tryagain> For example, if middle points deviate small enough (say, 1/2 of text height) from the shortcut connecting two corner points of subsegment, we can draw label over shortcut
17:10 -!- mvglasow [4d0dbe32@gateway/web/freenode/ip.77.13.190.50] has quit [Quit: Page closed]
17:22 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
17:40 -!- tryagain [~quassel@178.216.76.75] has quit [Remote host closed the connection]
17:47 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 240 seconds]
17:50 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
18:07 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 252 seconds]
18:08 -!- RobertP [5cd9e7ab@gateway/web/freenode/ip.92.217.231.171] has quit []
19:41 -!- xenos1984 [~xenos1984@127-166-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
--- Log closed Tue Oct 27 00:00:09 2015