[mkgmap-dev] Driving on Trail

2014-11-15 Thread Brian Egge
Frequently in areas where sidewalks are drawn, my GPS decides we are driving on the sidewalk and not on the road. When this happens it displays 'Driving on Trail'. I've verified the footways are tagged, and I've viewed the default style rule. I've double checked to make sure my GPS is in driving mo

Re: [mkgmap-dev] Optimizing MapSplitter

2014-11-15 Thread Gerd Petermann
Hi Steve, > > I don't think that the current algo is completely wrong. > > I think it is better to start with the complete data and divide it into > > smaller parts as that algo keeps the information of > > the location of elements, while your approach is likely > > to compare many bboxes which ar

Re: [mkgmap-dev] Optimizing MapSplitter

2014-11-15 Thread GerdP
Hi Andrzej, thanks for testing. I also think that the possible improvements are rather small. I'll try a few more changes, e.g. splitting large objects earlier, but I don't expect any big improvements. A typical case where it would help is a long diagonal line. The bbox for it is very big, and a

Re: [mkgmap-dev] Optimizing MapSplitter

2014-11-15 Thread Steve Ratcliffe
Hi Gerd I tried out the v3 of the patch. It looks good, just looking at the pattern in inkscape. There is a shift towards smaller divs, though the average is still quite large (in area). I don't think that the current algo is completely wrong. I think it is better to start with the complete

Re: [mkgmap-dev] Optimizing MapSplitter

2014-11-15 Thread Andrzej Popowski
Hi Gerd, patch v3 is working. I have done some speed test on nuvi but conclusions aren't clear. My feeling is that your original settings is a bit slower than standard mkgmap. I have tried some values and settled to: LARGE_OBJECT_DIM = 8192; int wantedSize = MAX_RGN_SIZE / 4; This seems to b

Re: [mkgmap-dev] Optimizing MapSplitter

2014-11-15 Thread Gerd Petermann
Hi Andrzej, yes, I did not test with your data yesterday and did not notice an old problem with high precision coordinates. Attached is a new patch that implements both changes which I suggested here: http://gis.19327.n5.nabble.com/Optimizing-MapSplitter-tp5823702p5824224.html I am not sure abo

Re: [mkgmap-dev] Optimizing MapSplitter

2014-11-15 Thread Gerd Petermann
Hi Steve, I don't think that the current algo is completely wrong. I think it is better to start with the complete data and divide it into smaller parts as that algo keeps the information of the location of elements, while your approach is likely to compare many bboxes which are (too) far away f