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
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.mak...@iki.fi wrote:
On Tue,
On Wed, Apr 06, 2011 at 07:44:42PM +0800, maning sambale wrote:
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?
I was
Hello,
I have a map that built correctly with 1903 which also builds correctly
with 1908 if I use sea-generator=multi-polygon but fails to build in
r1908 with sea-generator=extend-sea-sectors. The error is:
java.lang.OutOfMemoryError: GC overhead limit exceeded
at
Hi,
I get some wrong/bad routing results when it comes to a starting
onewayroad. Like it is on a crossing like this one:
^: the oneway road
- |: the normal roads whithout oneway
+: the corner point of the roads
^
^
^
^
^
^
+--- coming from here
|
|
|
|
|
|
|
|
want to get routed
A fellow mapper complained that some highways carry a 5-digit ref on the
mkgmap-produced map, even though the ref is nowhere to be seen on street
signs. OK, mkgmap cannot possibly know that, but I was wondering if we
could split this rule in the default style:
highway=* {name '${ref} ${name}'
On Wed, Apr 06, 2011 at 08:37:37PM +0200, Markus Hetzmannseder wrote:
In this situation my Garmin Dakota 20 is routing me up the oneway part
several roads around the block to get to the target just down the
street.
Could it be that we are incorrectly merging the oneway street with the
