Error processing mp file
On Feb 13, 2009, at 21:55, Carlos Dávila wrote:
I'm trying to generate a map from a mp file of 105 MB and get the following error: GRAVE (BlockManager): overflowed directory with max block 202, current=203 Directory overflow. This is a bug in mkgmap How can I solve it?
This was reported before: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2008q4/000221.html I'm not sure the problem was actually resolved. Cheers Robert
I see this also but only if I run with --road-name-pois on a large input file. I put it down to there being too much data being generated by the road names although the OP doesn't state their switches Paul Robert Vollmert wrote:
On Feb 13, 2009, at 21:55, Carlos Dávila wrote:
I'm trying to generate a map from a mp file of 105 MB and get the following error: GRAVE (BlockManager): overflowed directory with max block 202, current=203 Directory overflow. This is a bug in mkgmap How can I solve it?
This was reported before: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2008q4/000221.html
I'm not sure the problem was actually resolved.
Cheers Robert
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Paul escribió:
I see this also but only if I run with --road-name-pois on a large input file. I put it down to there being too much data being generated by the road names although the OP doesn't state their switches
Paul
I tried without --road-name-pois, but still the same problem. Any other idea? Carlos
Robert Vollmert wrote:
On Feb 13, 2009, at 21:55, Carlos Dávila wrote:
I'm trying to generate a map from a mp file of 105 MB and get the following error: GRAVE (BlockManager): overflowed directory with max block 202, current=203 Directory overflow. This is a bug in mkgmap How can I solve it?
This was reported before: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2008q4/000221.html
I'm not sure the problem was actually resolved.
Cheers Robert
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Por favor, no me envíe documentos con extensiones .doc, .docx, .xls, .xlsx, .ppt, .pptx, .mdb, mdbx Instale OpenOffice desde http://es.openoffice.org/programa/index.html OpenOffice es libre: se puede copiar, modificar y redistribuir libremente. OpenOffice es gratis. El uso de OpenOffice es totalmente legal. OpenOffice funciona mejor que otros paquetes de oficina. OpenOffice está en continuo desarrollo y no tendrá que pagar por las nuevas versiones.
This was reported before: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2008q4/000221.html
I'm not sure the problem was actually resolved.
Well I used to think that it was not possible to get that error, without getting the normal 'map too big' error first. I now just think I was wrong. So I think it is just a case of the input file being too big to fit into one map and it needs to be split. So unless you believe that it is not too big I will change the message. ..Steve
On Mon, Feb 16, 2009 at 11:32 PM, Steve Ratcliffe <steve@parabola.demon.co.uk> wrote:
So I think it is just a case of the input file being too big to fit into one map and it needs to be split.
I frequently received this error message. In every case I could resolve it by reducing the tile size. (For routing and road-name POIs, I had to significantly reduce the default --max-nodes value of Splitter.) So I can at least confirm that it is possible to receive this error without first receiving a "map too big" error. Hope this helps.
Steve Ratcliffe escribió:
This was reported before: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2008q4/000221.html
I'm not sure the problem was actually resolved.
Well I used to think that it was not possible to get that error, without getting the normal 'map too big' error first.
I now just think I was wrong.
So I think it is just a case of the input file being too big to fit into one map and it needs to be split.
So unless you believe that it is not too big I will change the message.
I don't know if you mean big in MB (input file is 105 MB) or in area covered (bbox=-9.501,35.99,3.33,43.79), but probably this is the origin of the problem. I needed to use -Xmx700M to avoid memory overflow. Regards Carlos
participants (5)
-
Carlos Dávila -
Clinton Gladstone -
Paul -
Robert Vollmert -
Steve Ratcliffe