Re: [mkgmap-dev] Clash of FIDs in tdb & typ files

It seems that the following msg refers to the problem of FIDs not matching up. 'has a different sort order (20007 rather than 0' Perhaps some mention of a different FID might be more helpful? Also 'rather than 0 ' should perhaps be 'rather than the value given to the family id? -- View this message in context: http://gis.19327.n5.nabble.com/Clash-of-FIDs-in-tdb-typ-files-tp5728742p5728... Sent from the Mkgmap Development mailing list archive at Nabble.com.