--- Log opened Thu Jan 25 00:00:11 2018 00:59 -!- Horwitz [~mich1@p200300800E03D900022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds] 01:07 -!- Irssi: Connection lost to irc.freenode.net 01:07 -!- Irssi: Removed reconnection to server irc.freenode.net port 6667 01:07 -!- Irssi: Looking up irc.freenode.net 01:07 -!- Irssi: Reconnecting to irc.freenode.net [149.56.134.238] port 6667 - use /RMRECONNS to abort 01:07 -!- Irssi: Connection to irc.freenode.net established 01:07 !cherryh.freenode.net *** Looking up your hostname... 01:07 !cherryh.freenode.net *** Checking Ident 01:07 !cherryh.freenode.net *** No Ident response 01:07 !cherryh.freenode.net *** Couldn't look up your hostname 01:07 -!- Welcome to the freenode Internet Relay Chat Network NavitLogger 01:07 -!- Your host is cherryh.freenode.net[149.56.134.238/6667], running version ircd-seven-1.1.4 01:07 -!- This server was created Wed Jan 4 2017 at 16:45:00 EST 01:07 -!- cherryh.freenode.net ircd-seven-1.1.4 DOQRSZaghilopswz CFILMPQSbcefgijklmnopqrstvz bkloveqjfI 01:07 -!- CHANTYPES=# EXCEPTS INVEX CHANMODES=eIbq,k,flj,CFLMPQScgimnprstz CHANLIMIT=#:120 PREFIX=(ov)@+ MAXLIST=bqeI:100 MODES=4 NETWORK=freenode STATUSMSG=@+ CALLERID=g CASEMAPPING=rfc1459 are supported by this server 01:07 -!- CHARSET=ascii NICKLEN=16 CHANNELLEN=50 TOPICLEN=390 DEAF=D FNC TARGMAX=NAMES:1,LIST:1,KICK:1,WHOIS:1,PRIVMSG:4,NOTICE:4,ACCEPT:,MONITOR: EXTBAN=$,ajrxz CLIENTVER=3.0 CPRIVMSG CNOTICE SAFELIST are supported by this server 01:07 -!- ELIST=CTU WHOX ETRACE KNOCK are supported by this server 01:07 -!- There are 119 users and 85791 invisible on 34 servers 01:07 -!- 31 IRC Operators online 01:07 -!- 7 unknown connection(s) 01:07 -!- 50177 channels formed 01:07 -!- I have 4814 clients and 1 servers 01:07 -!- 4814 7122 Current local users 4814, max 7122 01:07 -!- 85910 96600 Current global users 85910, max 96600 01:07 -!- Highest connection count: 7123 (7122 clients) (786930 connections received) 01:07 -!- - cherryh.freenode.net Message of the Day - 01:07 -!- - Welcome to freenode - supporting the free and open source 01:07 -!- - software communities since 1998. 01:07 -!- - 01:07 -!- - By connecting to freenode you indicate that you have read and 01:07 -!- - accept our policies and guidelines as set out on https://freenode.net 01:07 -!- - 01:07 -!- - In the event that you observe behaviour that contravenes our policies, 01:07 -!- - please notify a volunteer staff member via private message, or send us an 01:07 -!- - e-mail to complaints@freenode.net -- we will do our best to address the 01:07 -!- - situation within a reasonable period of time, and we may request further 01:07 -!- - information or, as appropriate, involve other parties such as channel operators 01:07 -!- - Group Contacts representing an on-topic group. 01:07 -!- - 01:07 -!- - freenode runs an open proxy scanner. 01:07 -!- - 01:07 -!- - If you are looking for assistance, you will be able to find a list of 01:07 -!- - volunteer staff using the '/who freenode/staff/*' command, and you may 01:07 -!- - message any of us at any time. Please note that freenode predominantly 01:07 -!- - provides assistance via private message, and while we have a network 01:07 -!- - channel the primary venue for support requests is via private message to 01:07 -!- - a member of the volunteer staff team. 01:07 -!- - 01:07 -!- - From time to time, volunteer staff may send server-wide notices relating to 01:07 -!- - the project, or the communities that we host. The majority of such notices 01:07 -!- - will be sent as wallops, and you can '/mode +w' to ensure that you 01:07 -!- - do not miss them. Important messages relating to the freenode project, including 01:07 -!- - notices of upcoming maintenance and other scheduled downtime will be issued as 01:07 -!- - global notices. 01:07 -!- - 01:07 -!- - Representing an on-topic project? Don't forget to register, more information 01:07 -!- - can be found on the https://freenode.net website under "Group Registration". 01:07 -!- - 01:07 -!- - freenode organises an annual conference, and we would like to extend our 01:07 -!- - thanks to the attendees, exhibitors and speakers who made freenode #live 2017 01:07 -!- - possible. And of course, our generous sponsors: Bytemark, Canonical (Ubuntu), 01:07 -!- - Falanx Cyber Security, Private Internet Access and Yubico for footing the bill. 01:07 -!- - 01:07 -!- - Thank you also to our server sponsors for the sustained support in keeping the 01:07 -!- - network going for close to two decades. 01:07 -!- - 01:07 -!- - freenode #live returns to Bristol, UK on November 3rd-4th 2018, keep an eye 01:07 -!- - on the https://freenode.live website for our call for volunteers and call for 01:07 -!- - participation. If you are interested in sponsoring next year's event, please 01:07 -!- - send us an e-mail to sponsor@freenode.live 01:07 -!- - 01:07 -!- - Thank you for using freenode! 01:07 -!- - 01:07 -!- - 01:07 -!- End of /MOTD command. 01:07 -!- Mode change [+i] for user NavitLogger 01:07 -!- NavitLogger [~NavitLogg@176.126.247.29] has joined #navit 01:07 -!- Topic for #navit: The open source vector based navigation program with routing engine. See http://wiki.navit-project.org. Please be patient if you don't get a response immediately. Please use http://navit.pastebin.com for your pastes! Channel is logged : http://irclogs.navit.ie/ Follow @NavitProject on Twitter. 01:07 -!- Topic set by KaZeR [~kazer@4.170.67.86.rev.sfr.net] [Mon May 23 17:10:04 2011] 01:07 [Users #navit] 01:07 [@ChanServ] [@Number6 ] [+youte ] [ ColdFyre ] [ Navit ] [ pmckinley] 01:07 [@Horwitz ] [+ilovekiruna] [ bzed ] [ j_f-f ] [ NavitLogger] [ rdorsch ] 01:07 [@KaZeR ] [+jkoan ] [ Celelibi] [ Millesimus] [ noradtux ] 01:07 -!- Irssi: #navit: Total of 17 nicks [4 ops, 0 halfops, 3 voices, 10 normal] 01:07 -!- Channel #navit created Sun Nov 26 06:47:57 2006 01:07 -!- Irssi: Join to #navit was synced in 6 secs 01:07 #navit: <@Number6> The logger is down. This is a known issue thanks to Spectre / Meltdown. Remind me if it's not back on the 26th :-) 01:23 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 240 seconds] 01:28 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit 05:24 #navit: <+jkoan> Number6: if you want to fill the time between the logger is down I can provide logs so we can fill the gap :D 06:11 -!- noradtux [~noradtux@port-7927.pppoe.wtnet.de] has quit [Ping timeout: 256 seconds] 06:16 -!- noradtux [~noradtux@2a02:2028:645:fb01:ec4:7aff:fe33:3dc1] has joined #navit 07:58 #navit: <+jkoan> hi @all 09:25 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit 09:25 -!- mode/#navit [+v xenos1984] by ChanServ 11:05 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Ping timeout: 246 seconds] 12:38 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit 12:38 -!- mode/#navit [+v xenos1984] by ChanServ 13:37 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.] 15:21 -!- Mineque [~androirc@2a00:f41:58ca:859d:0:3e:e6ce:f801] has joined #navit 15:21 #navit: < Mineque> Hi 15:28 #navit: <+jkoan> hi Mineque 15:28 #navit: <+jkoan> whats up? 15:36 #navit: < Mineque> At work :) 15:37 #navit: <+jkoan> Work for Navit? 15:37 #navit: < Mineque> Nope 15:37 #navit: <+jkoan> Not good :P 15:38 #navit: < Mineque> I'm not dev, neither user, no designer 15:39 #navit: < Mineque> Just warming up chair 15:39 #navit: <+jkoan> Oh, really? ^^ I thought you are a Dev :O 15:41 #navit: < Mineque> I started with translation then some skins years ago 15:41 #navit: < Mineque> But that time maps for Poland sucked 15:42 #navit: < Mineque> So navit was hard to use daily 15:42 #navit: <+jkoan> And now? Did maps got better? 15:44 #navit: < Mineque> I guess 15:44 #navit: < Mineque> Don't know 15:45 #navit: <+jkoan> Do you have a tomtom device? Then you can probably test soon :) 15:45 #navit: < Mineque> I have to push Kazer with qt gui code 15:45 #navit: < Mineque> And UX from my side 15:46 #navit: <+jkoan> Ah also a good idea :) 15:46 #navit: <+jkoan> KaZeR should be around soon, but as always I can't guarantee 15:47 #navit: <+jkoan> Can I help you with some other topics right now? 15:47 -!- twoelk [~twoelk@p5DC87F20.dip0.t-ipconnect.de] has joined #navit 15:51 #navit: < Mineque> No ;) 15:51 #navit: < Mineque> Pretend I'm not here ;p 15:55 #navit: <+jkoan> Okay :) 15:55 #navit: <+jkoan> Hi twoelk 15:55 #navit: < twoelk> o/ 15:55 #navit: <+jkoan> twoelk: how can I help you? 15:56 #navit: < twoelk> just lurking 15:56 #navit: * twoelk is studying the channel list 15:57 #navit: <+jkoan> twoelk: if you need help just ask :) 15:57 #navit: < twoelk> quite a few more programs that I use seem to have channels than I thought :-) 16:00 #navit: <+jkoan> Yes, a lot of projects use freenode :) 16:04 #navit: < Mineque> Twoelk: CIA spy? 16:06 #navit: < Mineque> I just imagine rocket navigation system 16:07 #navit: <+jkoan> Mineque: interesting idea, not for rockets but for drones 16:08 #navit: < Mineque> If you are Google and have 3d maps of globe then yes 16:08 #navit: < twoelk> drones using navit? 16:09 #navit: < Mineque> I guess it's more complicated than "turn right after 3rd Oak 16:09 #navit: <+jkoan> twoelk: no, we just make silly ideas 16:11 #navit: < twoelk> just read about selfdriving experiments, where the technicans complained the gps signals go bad every time the us turns the attention of the gps-satelites to syria 16:13 #navit: < twoelk> probably no good idea to have selfdriving devices depend on some us owned satelites 16:15 #navit: < Mineque> You have glonass by Russia or European joke 16:15 #navit: < Mineque> Each choice sucks 16:26 #navit: < twoelk> hmm, is http://gpsd.berlios.de/ down? 16:29 #navit: < Mineque> Yel 16:29 #navit: < Mineque> Yep 16:29 #navit: <+jkoan> twoelk: yes, berlios.de is downfor a long time 16:29 #navit: < twoelk> iirc though you cannot chose between gps sources in navit even if the hardware provides it 16:49 -!- youte [~youte@rla39-h01-176-133-215-10.dsl.sta.abo.bbox.fr] has quit [Ping timeout: 248 seconds] 16:57 #navit: <@KaZeR> hi there 16:57 #navit: <+jkoan> hi KaZeR 16:57 #navit: <+jkoan> you got a private message 16:59 #navit: <@KaZeR> hi twoelk and welcome 17:07 #navit: < twoelk> just unzipped current windows version and \navit\locale\ar\LC_MESSAGES\navit.mo could not be created 17:08 #navit: < twoelk> guess I don't need that locale anyways 17:09 #navit: <+jkoan> twoelk: could you provide the link you used to download this version? 17:10 #navit: < twoelk> oops and avast just killed it :-( 17:10 #navit: <+jkoan> thats verry interesting 17:11 #navit: <+jkoan> do you have a link for me? 17:11 #navit: < twoelk> http://download.navit-project.org/navit/win32_cmake/svn/navit-current.zip 17:12 #navit: < twoelk> lol, avast is sending the navit.exe to their labs for inspection 17:12 #navit: <+jkoan> okay, this one is really outdated :D wait a moment, i send you the new link 17:14 #navit: <+jkoan> KaZeR: we dont store the win32 exe on circleci 17:14 #navit: <+jkoan> twoelk: just try with this one: http://download.navit-project.org/navit/win32_cmake/svn/navit-current.zip 17:15 #navit: * twoelk is downloading 17:25 #navit: < twoelk> strange, zip-file size is same but it takes way longer to unpack 17:26 #navit: <+jkoan> probably the compression is bigger 17:36 -!- jandegr [55eac8e0@gateway/web/freenode/ip.85.234.200.224] has joined #navit 17:36 #navit: * twoelk adventures to define a new mapset 17:52 #navit: < twoelk> interesting artefacts https://i.imgur.com/7hjC0eb.jpg 17:56 #navit: < twoelk> also seems areas in relations still don't show filling color 18:01 #navit: <@KaZeR> twoelk: are you talking about the somewhat squared shoreline ? 18:03 #navit: < twoelk> nope, the light green areas rendered along grid lines 18:04 #navit: < twoelk> probably tile borders or such 18:06 #navit: < twoelk> anyways, pic is proof that navit can digest relative paths - so now I can rebuild my navigation system on a portable device :-D 18:08 #navit: < jandegr> small items will drop down to an appropriate lower level tile, but if they are small but overlapping tile borders they are not clipped 18:12 #navit: < twoelk> I wonder wether I can workout a sensible way of having clever mapsets with befor and after comparism 18:13 #navit: <@KaZeR> twoelk: something like this ? http://trac.navit-project.org/ticket/854#comment:7 18:18 #navit: < twoelk> http://www.openstreetmap.org/#map=10/53.7710/10.6142 you can see here the green patches actually do not follow any grid pattern 18:22 #navit: < twoelk> KaZeR: the water flooding tiles seems to be a problem of interpreting large shapes, such as that of an ocean, while the generating of objects along a prefered grid is something different, maybe as jandegr said 18:23 #navit: < twoelk> both may be problems of recognising areas across tile borders correctly though 18:27 #navit: < jandegr> distinct issues : 18:27 #navit: < jandegr> green patches on a grid : known issue, see above 18:28 #navit: < jandegr> water artefacts disappearing on lower zoomlevels, known issue with a known fix, cfr the link kazer posted 18:29 #navit: < jandegr> real flooding : often caused by wrong usage of natural=coastline in OSM, showing water on all zoomlevels where there should be land 18:30 #navit: < jandegr> natural=coastline is only for shores along ocean, but sometimes found on islands in lakes and such 18:30 #navit: < jandegr> the last can be searched for with overpass turbo 18:40 #navit: <@KaZeR> twoelk: oh absolutely. i pasted that link as an example for you question 18:40 #navit: <@KaZeR> "... mapsets with befor and after comparism" 18:45 #navit: < twoelk> maybe I should rather say "now and then" 18:47 #navit: <@KaZeR> ha. well you can have multiple maps defined in navit and switch between them. it's even possible to do it programmatically via dbus 18:47 #navit: < twoelk> like I made an osm-file-format version of my village around 1740 18:47 #navit: <@KaZeR> so you just need to keep the binfile 18:48 #navit: <@KaZeR> which is exactly how the screenshots i shared were generated 18:48 #navit: <@KaZeR> there's code below the screenshots 18:48 #navit: < twoelk> hm, hadn't played with this data for quite a while 18:57 #navit: <+ilovekiruna> hi there 19:04 #navit: <@KaZeR> hi ilovekiruna 19:05 #navit: <+ilovekiruna> KaZeR: any time scope for the PR? 19:06 -!- youte [~youte@rla39-h01-176-133-215-10.dsl.sta.abo.bbox.fr] has joined #navit 19:06 -!- mode/#navit [+v youte] by ChanServ 19:09 #navit: < twoelk> duh, no gpx or klm support for poi files :-( 19:09 #navit: < twoelk> now I remember why I used navit so seldom 19:15 #navit: <@KaZeR> what do you mean twoelk ? 19:17 #navit: * twoelk just downloaded gpx2navit_txt.jar and will throw some self built gpx files at it 19:19 -!- Mineque [~androirc@2a00:f41:58ca:859d:0:3e:e6ce:f801] has quit [Quit: AndroIRC - Android IRC Client ( http://www.androirc.com )] 19:19 -!- Mineque [~Mineque@2a00:f41:58ca:859d:e45c:e3e7:bd0d:5f16] has joined #navit 19:20 #navit: <@KaZeR> twoelk: is that for a route or for something like a bookmark? 19:20 #navit: < twoelk> bookmarks 19:21 #navit: <@KaZeR> would you like to work on gpx support for bookmarks with us? 19:22 #navit: < twoelk> actually I made some scripts a while ago that would generat POI files from selections with notes made with our CRM software t 19:23 #navit: <+ilovekiruna> random question: do we use in any way multithreads or similar in navit? 19:23 #navit: < twoelk> they would also be used in slippy maps on our intranet 19:26 #navit: < twoelk> guess I may be able to help. never looked at navit code though. (will clone git as a start) 19:26 #navit: <@KaZeR> ilovekiruna: we do for the spotify playback for example. jandegr also has some code to use that in opengl graphics. we need more of them in my opinion given today's hardware 19:26 #navit: <@KaZeR> twoelk: awesome 19:37 -!- jandegr [55eac8e0@gateway/web/freenode/ip.85.234.200.224] has quit [Quit: Page closed] 19:46 #navit: < twoelk> hm, can I define in the POI file at what loom level points should appear? 19:46 #navit: < twoelk> *zoom level 19:48 #navit: < Mineque> twoelk: in xml afair 19:51 #navit: < twoelk> well I might have a file with hundreds of points to a single city while another has few points spread over a large area, therefore some value within a poi file might be usefull 20:01 #navit: < twoelk> hmm, garmin icon types are not transfered also 20:03 -!- Mineque [~Mineque@2a00:f41:58ca:859d:e45c:e3e7:bd0d:5f16] has quit [Quit: Leaving] 21:35 -!- noradtux [~noradtux@2a02:2028:645:fb01:ec4:7aff:fe33:3dc1] has quit [Ping timeout: 240 seconds] 21:40 -!- noradtux [~noradtux@port-54259.pppoe.wtnet.de] has joined #navit 22:56 #navit: <@KaZeR> twoelk: yeah currently POI display is managed via the layout, not the map 23:24 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 248 seconds] 23:33 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit --- Log closed Fri Jan 26 00:00:13 2018