
Hi Marko- Thanks for the info. I started with an empty directory, just the osm.bz2 file, and after the splitter was done I did have a bunch of img and osm.pbf files along with template.args and areas.list. The areas.list file matches the template.args file. I ran mkgmap with a logging.properties file and output it, but all I saw were a bunch of warnings regarding various polygons, streets, etc. There were no error or catastrophic problems I saw. I will try again, stripping everything out but the bare minimum and see what I get, then add the parameters back and see what happens. On 9/9/11 12:39 AM, "Marko Mäkelä" <marko.makela@iki.fi> wrote:
On Fri, Sep 09, 2011 at 12:23:52AM -0500, Ron Olson wrote:
But again no joy. Is it possible the splitter parameters are wrong for what I'm trying to do?
What do you have in the areas.list generated by splitter? Do the tile names match the file names in the template.args that you passed to mkgmap? Did you try removing all *.img and *.osm.gz files before running splitter and mkgmap?
If all that is correct, then I think you should enable logging and check the mkgmap log output for further hints. But an empty map sounds like there should be something seriously wrong with the input parameters.
Marko _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev