[mkgmap-dev] how to get better error logs during map compile?

Wed Apr 6 12:44:42 BST 2011

Thanks.  I already have it  in my compile process.  The existing logs
give me errors for many data problems coastline gaps, oneways, etc..
Which part of logging.properties should provide info on uncompleted
compile?

On Wed, Apr 6, 2011 at 2:55 PM, Marko Mäkelä <marko.makela at iki.fi> wrote:
> On Tue, Apr 05, 2011 at 09:19:13PM +0800, maning sambale wrote:
>>All I get in my logs are:
>>time java -Xmx1512m -jar mkgmap.jar --read-config=args2.list
>>philippines.osm.pbf MINIMAL.TYP
> [...]
>>Is there way to get a log report that shows that the compile process is
>>completed and possible reasons for the uncompleted compile?
>
> java -Xmx1512m -ea -Dlog.config=logging.properties -jar mkgmap.jar ...
>
> In logging.properties you can say how much detail you want. You can find
> a sample file here:
> http://www.polkupyoraily.net/osm/files/logging.properties
>
> It will generate the output to a file mkgmap.log.0.
>
>        Marko
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>

-- 
cheers,
maning
------------------------------------------------------
"Freedom is still the most radical idea of all" -N.Branden
wiki: http://esambale.wikispaces.com/
blog: http://epsg4253.wordpress.com/
------------------------------------------------------