8 Jan
2013
8 Jan
'13
10:12 p.m.
WanMil wrote
I think we should at least limit this range.
Why? mkgmap checks for a fake id only at 2 points: Multipolygon: some logging is changed in case it is a fake id or not. SeaGenerator: some coastline ways are copied when they don't have a fake id.
OK, so the potential problem is small, but would it be a problem to change isFakeId() to something like this? public static boolean isFakeId(long id) { return id >= startId && id < startId + 1L << 32; } Gerd -- View this message in context: http://gis.19327.n5.nabble.com/FakeIdGenerator-tp5743379p5743507.html Sent from the Mkgmap Development mailing list archive at Nabble.com.