--- Log opened Mon Feb 04 00:00:14 2019
01:41 -!- Horwitz [~mich1@p200300EC9BFDED00022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 250 seconds]
01:54 -!- Horwitz [~mich1@p200300EC9BC9B300022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
01:54 -!- mode/#navit [+o Horwitz] by ChanServ
02:47 -!- xenos1984 [~xenos1984@d066-f9bd-1ebd-45b2-8780-87e7-07d0-2001.dyn.estpak.ee] has quit [Quit: Leaving.]
06:13 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
06:13 -!- mode/#navit [+v xenos1984] by ChanServ
07:41 -!- naggety [~naggety@48.red-81-47-34.dynamicip.rima-tde.net] has joined #navit
09:24 -!- e0mi [~e0mi@p5791A701.dip0.t-ipconnect.de] has joined #navit
09:56 -!- naggety [~naggety@48.red-81-47-34.dynamicip.rima-tde.net] has quit [Ping timeout: 240 seconds]
09:56 -!- naggety [~naggety@246.red-80-27-33.dynamicip.rima-tde.net] has joined #navit
15:36 -!- naggety [~naggety@246.red-80-27-33.dynamicip.rima-tde.net] has quit [Quit: Konversation terminated!]
15:57 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
17:23 -!- xenos1984 [~xenos1984@0fa5-8efc-a27b-48db-8780-87e7-07d0-2001.dyn.estpak.ee] has joined #navit
17:23 -!- mode/#navit [+v xenos1984] by ChanServ
18:21 -!- ilovekiruna [~ilovekiru@ip1f12af77.dynamic.kabel-deutschland.de] has joined #navit
18:21 -!- mode/#navit [+v ilovekiruna] by ChanServ
18:21 #navit: <+ilovekiruna> hi all
21:01 -!- mvglasow [~mvglasow@dslb-178-002-060-156.178.002.pools.vodafone-ip.de] has joined #navit
21:04 #navit: < mvglasow> hi folks
21:05 #navit: < mvglasow> question: has anyone successfully built Navit for Tomtom after December 2016?
21:05 #navit: < mvglasow> even better after September 2017?
21:06 #navit: < mvglasow> to me the artifacts from September 2017 onwards look broken, but I am not an expert and may be wrong
21:06 #navit: <+ilovekiruna> hi mvglasow
21:06 #navit: <+ilovekiruna> you mean both compiled and successfully installed, right?
21:09 #navit: < mvglasow> either that or at least being able to tell me if a particular package is broken
21:09 #navit: < mvglasow> thing is, later packages lack the XML file in /navit/share
21:09 #navit: < mvglasow> I have seen a CI build from Dec 2016 where it it still present
21:10 #navit: < mvglasow> and in another from September 2017 (and all later builds) it is missing
21:10 #navit: < mvglasow> first question: is that an error? there is no XML file anywhere in that package
21:10 #navit: <+ilovekiruna> i vaguely remember that I think jkoan installed it on a tomtom last year in Feb
21:10 #navit: <+ilovekiruna> during the fosdem
21:11 #navit: < mvglasow> I've already added him to the ticket but haven't heard back from him yet
21:12 #navit: <+ilovekiruna> btw: a user from munich talked to me during fosdem
21:13 #navit: <+ilovekiruna> he uses sailfish and seems to somehow have a problem
21:13 #navit: <+ilovekiruna> I told him to write an issue
21:43 #navit: < mvglasow> no idea who that could be, though
21:45 #navit: <+ilovekiruna> he didnt report anything yet, i also pointed him to IRC, but didnt have too much scope
21:45 #navit: <+ilovekiruna> you also worked on the routing algorithm, right?
21:45 #navit: < mvglasow> yeah. I did a few things
21:45 #navit: < mvglasow> maneuver generatio a few years back, then replacing Dijkstra with LPA*
22:00 #navit: <+ilovekiruna> I also partially saw a presentation on fosdem by the graphhopper team
22:00 #navit: <+ilovekiruna> was curious if there is anything interesting we should steal ;-)
22:02 #navit: <+ilovekiruna> would share the link with the video with you once I get it
22:13 #navit: < mvglasow> did they have anything that looked interesting?
22:20 #navit: <+ilovekiruna> also dynamic routing
22:20 #navit: <+ilovekiruna> for example also including public transport based on raw data
22:20 #navit: < mvglasow> as in, modifying segment costs for an existing route and doing a partial recauculation?
22:21 #navit: <+ilovekiruna> they get the positions and time tables from some cities and do a navigatio nbased on that
22:21 #navit: <+ilovekiruna> I talked to the presenter from graphhopper
22:21 #navit: <+ilovekiruna> I also contacted now Öffi if they are interested in moving from pedestrian navigation to navit
22:22 #navit: <+ilovekiruna> graphhopper itself is not that great for us  as it is coded in java
22:35 #navit: < mvglasow> anyways there would be portability issues, as the map layer in Navit is likely very different from Graphhopper's
22:36 #navit: < mvglasow> not last because OSM was an afterthought in Navit, the original map data model predates OSM
22:36 #navit: <+ilovekiruna> was the original garmin?
22:37 #navit: < mvglasow> not sure, either that or Marco Polo, or both
22:37 #navit: < mvglasow> I think the beginnings were in 2002-2003, and the code was open sourced around 2005
22:38 #navit: < mvglasow> and when I stumbled across it in 2010, OSM was already in wide use, and other map formats became niche products pretty soon
22:39 #navit: <+ilovekiruna> when did you join?
22:40 #navit: < mvglasow> I submitted my first patch in 2010
22:40 #navit: < mvglasow> and got commit rights in 2014 iirc
22:42 #navit: <+ilovekiruna> wow, very long
22:42 #navit: <+ilovekiruna> impressive
--- Log closed Tue Feb 05 00:00:15 2019