--- Log opened Sat Jan 26 00:00:40 2013
02:34 -!- Hotdog [~owas1@ip98-164-157-168.mc.at.cox.net] has joined #navit
02:51 #navit: < Hotdog> How does the xml file for an OSM map downloaded via the navit website get created? Does it just magically happen when maps are obtained that way?
02:58 -!- cp15` [ynpadm@p57B1CC0B.dip0.t-ipconnect.de] has joined #navit
02:58 -!- cp15 [vgckeg@p57B1CF0F.dip0.t-ipconnect.de] has quit [Disconnected by services]
02:58 -!- cp15` is now known as cp15
02:58 -!- mode/#navit [+o cp15] by ChanServ
04:01 -!- noradtux [~noradtux@2002:4e36:7b3e::1] has quit [Ping timeout: 245 seconds]
04:07 #navit: < Hotdog> I have learned how to read the chat log files so I'll check back later. Thanks to anyone who responds.
04:08 -!- noradtux [~noradtux@2002:5ce0:323f::1] has joined #navit
04:10 #navit: < Hotdog> Hi, Noradtux. That is a neat nickname.
04:14 -!- Hotdog [~owas1@ip98-164-157-168.mc.at.cox.net] has left #navit []
06:47 -!- _rd [~rd@p57B480AD.dip0.t-ipconnect.de] has joined #navit
07:00 -!- _rd [~rd@p57B480AD.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds]
07:19 -!- TauSo [~thomas@g227129096.adsl.alicedsl.de] has joined #navit
07:48 -!- _rd [~rd@p57B480AD.dip0.t-ipconnect.de] has joined #navit
08:17 -!- Neuntoter [Neuntoter@173-24-25-62.client.mchsi.com] has quit [Ping timeout: 245 seconds]
08:35 -!- tryagain [~tryagain@178.216.76.17] has joined #navit
09:17 -!- Neuntoter [Neuntoter@173-24-25-62.client.mchsi.com] has joined #navit
09:18 -!- Neuntoter [Neuntoter@173-24-25-62.client.mchsi.com] has quit [Client Quit]
10:41 -!- TauSo [~thomas@g227129096.adsl.alicedsl.de] has left #navit []
11:13 -!- Navit [~Navit@static.3.141.4.46.clients.your-server.de] has joined #navit
11:13 #navit: < Navit> Hi
11:14 #navit: < tryagain> welcome
11:17 -!- Navit [~Navit@static.3.141.4.46.clients.your-server.de] has quit [Client Quit]
11:17 -!- Navit [~Navit@static.3.141.4.46.clients.your-server.de] has joined #navit
11:40 -!- _rd [~rd@p57B480AD.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
12:33 -!- _rd [~rd@p57B480AD.dip0.t-ipconnect.de] has joined #navit
12:50 #navit: < Navit> Sa 26. Jan 13:56:15 CET 2013
12:50 #navit: < Navit> Sa 26. Jan 13:56:15 CET 2013
12:51 -!- _rd [~rd@p57B480AD.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds]
12:53 #navit: < Navit> ***** Nagios *****
12:53 #navit: < Navit> Notification Type: RECOVERY
12:53 #navit: < Navit> Service: Scratch Filesystem
12:53 #navit: < Navit> Host: localhost
12:53 #navit: < Navit> Address: 127.0.0.1
12:53 #navit: < Navit> State: OK
12:53 #navit: < Navit> Date/Time: Sat Jan 26 13:58:56 CET 2013
12:53 #navit: < Navit> Additional Info:
12:53 #navit: < Navit> DISK OK - free space: /scratch 245395 MB (42% inode=99%):
13:00 -!- _rd [~rd@p57B480AD.dip0.t-ipconnect.de] has joined #navit
15:26 -!- woglinde [~henning@g225167194.adsl.alicedsl.de] has joined #navit
15:52 -!- TauSo [~thomas@g226251170.adsl.alicedsl.de] has joined #navit
16:50 -!- tryagain [~tryagain@178.216.76.17] has quit [Ping timeout: 276 seconds]
17:00 -!- woglinde [~henning@g225167194.adsl.alicedsl.de] has quit [Quit: Lost terminal]
17:19 -!- xenos1984 [~quassel@131.237.196.88.dyn.estpak.ee] has joined #navit
17:19 #navit: < xenos1984> hi everybody
17:21 -!- woglinde [~henning@g225167194.adsl.alicedsl.de] has joined #navit
18:29 -!- xenos1984_ [~quassel@131.237.196.88.dyn.estpak.ee] has joined #navit
18:30 -!- xenos1984 [~quassel@131.237.196.88.dyn.estpak.ee] has quit [Disconnected by services]
18:30 -!- xenos1984_ is now known as xenos1984
18:33 -!- Hotdog_ [62a49da8@gateway/web/freenode/ip.98.164.157.168] has joined #navit
18:38 #navit: < Hotdog_> Hello to anyone onboard.
18:40 #navit: < woglinde> yes
18:42 #navit: < Hotdog_> woglinde, nice to see some one here. Do you run Navit on a desktop or a laptop under Linux?
18:43 #navit: < woglinde> does not matter
18:43 #navit: < woglinde> whats your problem?
18:44 #navit: < xenos1984> hi Hotdog_ & woglinde
18:44 #navit: < Hotdog_> I'd like to know how the xml file for a map downloaded from the Navit website gets created?
18:44 #navit: < Hotdog_> Hello, xenos1984
18:45 #navit: < Hotdog_> That is an OSM map, woglinde.
18:50 #navit: < woglinde> hotdog with tool called maptool
18:50 #navit: < woglinde> you can download a snippet from osm data and convert it with maptool
18:51 #navit: < woglinde> http://wiki.navit-project.org/index.php/OpenStreetMap#Convert_OSM_data_to_Navit_binfile
18:51 #navit: < Hotdog_> Does that happen automatically? I've downloaded some small maps for testing and they work but I did not do anything extra. The link you just posted is where I got them.
18:52 #navit: < xenos1984> Hotdog_: i guess you're rather looking for an xml file content like this? http://wiki.navit-project.org/index.php/Configuration#Maps_Options
18:52 #navit: < xenos1984> the maps you download from navit's website have already been converted from OSM to navit bin format
18:54 #navit: < Hotdog_> xenos1984, that is the answer I think, no map-specific xml needed?
18:54 #navit: < xenos1984> Hotdog_: not necessarily, you can simply include new maps into your existing navit.xml file
18:55 #navit: < Hotdog_> The demo map that came with Navit had in /usr/share/navit a mapfile (bin) pluse a small xml file that refered to the mapfile, just one line in the xml.
18:55 #navit: < Hotdog_> I understand about the big xml for configuring Navit.
18:56 #navit: < xenos1984> ah, yes, the demo map uses this redirection through a small xml file (but i don't know the reason why)
18:57 #navit: < Hotdog_> xenos1984, it was confusing for me too, since subsequent maps did not have one, and they worked fine.
18:58 #navit: < xenos1984> yes, in general this should work fine, unless you put your maps into non-standard locations or use a different map type
18:58 #navit: < Hotdog_> I am fasinated with Navit and want to contribute. Right now I am just trying to learn as much as I can.
18:59 #navit: < woglinde> there are diffrrent ways to specifiy the maps
18:59 #navit: < Hotdog_> I'm trying to write my own little 'How-to' from what I learn.
18:59 #navit: < woglinde> why?
18:59 #navit: < woglinde> better fix the wiki
18:59 #navit: < woglinde> so everyone has something of it
19:00 #navit: < Hotdog_> What is wrong with the wiki, woglinde?
19:00 #navit: < woglinde> it must something wrong in the wiki when you need to write your own howtos
19:00 #navit: < woglinde> be
19:01 #navit: < Hotdog_> Sorry, I understand, woglinde. I will do just that when I have enough. The wiki does not make a good introduction for new users who may be accustomed to commercial offerings.
19:02 #navit: < Hotdog_> No commercial mapping allows customization like Navit.
19:02 #navit: < woglinde> yes
19:02 #navit: < woglinde> + we have dbus support
19:02 #navit: < woglinde> which opens a lot of intresstings scenarios
19:03 #navit: < Hotdog_> Great point, woglinde. And good reason for good How-to's.
19:03 #navit: < woglinde> after cp15 adding postal search to dbus
19:03 #navit: < Hotdog_> Postal, have not heard that. Wonderful!
19:04 #navit: < woglinde> we only need a little module with a speech regconization programm and we can search for routes via voice
19:04 #navit: < Hotdog_> Wow, look out commercial progs
19:05 #navit: < Hotdog_> Guys, thanks for the info. Will be looking forward to seeing you here again
19:05 #navit: < woglinde> downside is we may not always have the best routing search algorithm
19:06 #navit: < woglinde> okay so is your problem solved or not?
19:06 #navit: < Hotdog_> That is what I want to help with
19:06 #navit: < Hotdog_> woglinde, yes it is, thanks
19:06 #navit: < woglinde> sure first step I have on my long agenda and did not found time is to make routing stuff pluginable
19:06 #navit: < woglinde> like the other plugins
19:07 #navit: < Hotdog_> You are on the right track with doing it via plugins
19:07 #navit: < woglinde> which means the first step in this process is make a generic search api
19:07 #navit: < woglinde> which will then be implemented by the plugins
19:08 #navit: < Hotdog_> Does the xml get input all at once or by section as needed?
19:08 #navit: < woglinde> at once
19:09 #navit: < Hotdog_> So there is a slight price in terms of memory used, right?
19:09 #navit: < woglinde> yes
19:09 #navit: < Hotdog_> Do you think all-at-once will always be used?
19:12 #navit: < woglinde> xml is parsed at starting
19:12 #navit: < Hotdog_> Understand. I enjoyed this chat (my first ever in 64 years!) I will be back. Thanks guys.
19:13 #navit: < woglinde> 64?
19:13 #navit: < Hotdog_> Meant 'understood'
19:13 #navit: < Hotdog_> Right!
19:13 #navit: < woglinde> ah in
19:13 #navit: < woglinde> sorry
19:14 #navit: < woglinde> lol
19:14 #navit: < woglinde> I read it since
19:14 #navit: < Hotdog_> Still wondering what I want to be when I grow up!
19:15 #navit: < woglinde> I do not grow up either
19:15 #navit: < Hotdog_> Things like Navit help keep getting old at bay
19:16 #navit: < Hotdog_> Things like Navit keeps you young
19:17 #navit: < Hotdog_> I'm gone for now
19:22 -!- Hotdog_ [62a49da8@gateway/web/freenode/ip.98.164.157.168] has quit [Ping timeout: 245 seconds]
19:23 -!- TauSo [~thomas@g226251170.adsl.alicedsl.de] has left #navit []
20:04 -!- xenos1984 [~quassel@131.237.196.88.dyn.estpak.ee] has quit [Ping timeout: 256 seconds]
20:05 -!- tryagain [~tryagain@87.245.203.24] has joined #navit
20:41 -!- ScriptFanix [vincent@Hanaman.riquer.fr] has quit [Ping timeout: 245 seconds]
22:24 -!- woglinde [~henning@g225167194.adsl.alicedsl.de] has quit [Ping timeout: 240 seconds]
22:37 -!- _rd [~rd@p57B480AD.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds]
22:39 -!- _rd [~rd@p57B480AD.dip0.t-ipconnect.de] has joined #navit
23:13 -!- _rd [~rd@p57B480AD.dip0.t-ipconnect.de] has quit [Ping timeout: 244 seconds]
--- Log closed Sun Jan 27 00:00:40 2013