Re: [mkgmap-dev] House numbers

2012-12-06 Thread Alexander Atanasov
Hi. On 6 December 2012 23:55, Martin wrote: > Hi, > > maybe you can also include the zip-code-search. I know, house numbers a more > important, but zip-code-search is a nice feature, especially if you have a > big city, that has streets with the same name in different zip-areas (e.g. > Berlin

Re: [mkgmap-dev] polygon splitting/more than 255 polygons errors

2011-09-03 Thread Alexander Atanasov
Hi, On Fri, Sep 2, 2011 at 9:26 PM, Richard wrote: > Hi, > >> > I have recently downloaded some mkgmap generated maps that produce this >> > error when displayed >> > in navit: >> > :garmin_obj.c:1279:1|:Error more than 255 polygons/lines in a subdiv are >> > not supported >> >> This does not l

Re: [mkgmap-dev] img subfile extraction

2010-08-26 Thread Alexander Atanasov
Hi, On Thu, Aug 26, 2010 at 1:51 AM, Albert Hattingh wrote: > Is there an easy way to extract the sub-files of a Gramin img file, either > by using some of the mkgmap code or another piece of software?  I am > interested in delving deeper into the file format and playing around with > the unknown

Re: [mkgmap-dev] Really Serious bug when not using --route

2010-05-28 Thread Alexander Atanasov
Hi, On Thu, May 27, 2010 at 11:44 PM, Steve Ratcliffe wrote: > > >> In the TREHeader.java (like in the patch from steve) add a one more byte >> in first position. If I understand it correctly, this will set the >> ominous fourth byte to 01. (Not tested). > > In fact the 4th byte that appears in t

Re: [mkgmap-dev] MDR success and a couple of questions

2009-10-08 Thread Alexander Atanasov
Hi, A bit of mdr > 15 or on the device format. Looks like it's the same except references to mdr15 are stripped in the sections < 15. They are moved in mdr17 in each section there. MDR17 format is like this: Section: read one byte and check first bits, section lenght is encoded there. if (b&1) ->

Re: [mkgmap-dev] MDR success and a couple of questions

2009-10-06 Thread Alexander Atanasov
On Sun, Oct 4, 2009 at 1:58 PM, Steve Ratcliffe wrote: > Hi > >> MDR7 - Roads >> 1/2 bytes IMG id from MDR1 >> 3 bytes - unknown, may be a pointer in NOD, it's not a label or NET offset > > This definitely is or can be a pointer to LBL as I have now got working > street search based on it being a

Re: [mkgmap-dev] MDR success and a couple of questions

2009-09-30 Thread Alexander Atanasov
Hi, Steve! On Wed, Sep 30, 2009 at 2:18 AM, Steve Ratcliffe wrote: > > Hi Alex > >> The unknown byte is sequential as you see above. >>> From MDR4 where the type changes(just type, no the subtype) it >> coresponds to a record here. >> So you have a type from here you find where point with that ty

Re: [mkgmap-dev] MDR success and a couple of questions

2009-09-23 Thread Alexander Atanasov
Hi, On Tue, Sep 22, 2009 at 6:31 PM, Steve Hosgood wrote: > Steve Ratcliffe wrote: >> Hi >> >> I've managed to construct a working MDR file with all of 2 POIs in it. >> >> > Congratulations! Nice work. > >> Secondly any ideas on MDR 9?  The first record always appears to be 01 >> 01 00 00, and th

Re: [mkgmap-dev] MDR success and a couple of questions

2009-09-23 Thread Alexander Atanasov
Hi! This is going to be a long post. MDR1 - Images List. 4 bytes image id, 4 bytes detailed map id, like in the tdb MDR4 1 byte type, 1 byte unknown, 1 byte subtype garmin_mdr.c:1020:1|POI Type garmin_mdr.c:337:1|1(0)[] type=0x0300 x=4(4) :03 04 00 garmin_mdr.c:337:1|2(1)[0003] type=0x0400