I have (eventually) got phyghtmap working - gave up on Python 3.3 and 64 bit and installed Python 2.7 and 32 bit, which works OK. The main problem I have with phyghtmap is spelling it! So that problem has gone away for me, but It might be good defensive programming to issue a warning if there is likely to be a problem with IDs.

Thanks to all for advice on this.

Roger

On 08/01/2013 19:50, Geoff Sherlock wrote:
As Thorsten said phyghtmap. Pain to set up on 64 bit system but good results.

Geoff

GerdP <gpetermann_muenchen@hotmail.com> wrote: 
WanMil wrote

do you know any other tool than SRTM2OSM? If it's only SRTM2OSM I guess 
there is no problem. The history of SRTM2OSM tells that version 1.10 
starts with IDs at 2^63-1 counting down. So there are 
4611686018427387903 ids until it conflicts with mkgmaps FakeIdGenerator.

No, I don't know other tools, but you are not right. 
Any id larger than 2^62 is considered to be a fakeid:

 public static boolean isFakeId(long id) {
  return id >= startId;
 } 

I think we should at least limit this range.

Gerd



--
View this message in context: http://gis.19327.n5.nabble.com/FakeIdGenerator-tp5743379p5743475.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.


mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev



_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

--

Roger Calvert