Hello!
I tried NSIS and it worked! You were right, the problem was caused by a
software in the toolchain. Thanks for all of you for your help. :)
Zsolt
On Thu, Aug 4, 2011 at 8:02 PM, WanMil wrote:
> > Sorry, I thought MapSource usage is common on this list. The red areas
> > are where the map
> Sorry, I thought MapSource usage is common on this list. The red areas
> are where the map was completely rendered and you can mark them for
> upload. The grey and yelllow areas are rendered only on the lowest
> resolution, so they cannot marked for upload.
MapSource is well known on this list b
Zsolt,
> Sorry, I thought MapSource usage is common on this list. The red areas
> are where the map was completely rendered and you can mark them for
> upload. The grey and yelllow areas are rendered only on the lowest
> resolution, so they cannot marked for upload. The rendering process is
> brok
Sorry, I thought MapSource usage is common on this list. The red areas are
where the map was completely rendered and you can mark them for upload. The
grey and yelllow areas are rendered only on the lowest resolution, so they
cannot marked for upload. The rendering process is broken, but mkgmap
doe
I am afraid but I have to ask: where's the problem? I don't see it.
Maybe you could try to use the NSIS installer to install the map in
MapSource. This avoids to have some unknown software in the tool chain.
By polygons I mean multipolygons and polygons. Multipolygons are
converted to normal po
The red areas are the actually rendered areas.
http://imageshack.us/photo/my-images/64/screenshot717201110719p.png/
This is the result by splitting it to 8 pieces. The eastern part is already
OK.
By polygons do you mean multipolygons? I'm sure I broke a lot of
multipolygons by splitting the map
> I had another go with splitter this morning and it worked out. But it's
> strange.
> If I split Hungary into 3-4 pieces, the eastern part is usually OK. But
> even if I split Hungary into 33 pieces I get bad areas on the western
> part or near Budapest. I splitted it to 36 and it worked with this
I had another go with splitter this morning and it worked out. But it's
strange.
If I split Hungary into 3-4 pieces, the eastern part is usually OK. But even
if I split Hungary into 33 pieces I get bad areas on the western part or
near Budapest. I splitted it to 36 and it worked with this command:
On 02/08/2011 01:18, Peter Lerner wrote:
>
> Zsolt,
>
> ...
>> What am I doing wrong? If you need any more detail I'd be glad to
>> provide it.
>
> not an answer to your problem, but a question to the list:
>
> Do we have a bugtracking tool that we can use to document software problems?
>
> Peter
>
El 01/08/2011 22:36, Zsolt Bertalan escribió:
> Hello
>
> I try to render a Garmin map of Hungary from OSM data with my own
> rules and typ file. At first I used the Tile Splitter, but whatever I
> did, I didn't manage to render a good map.
splitter should work fine with Hungary data and you'l
Zsolt,
...
> What am I doing wrong? If you need any more detail I'd be glad to
> provide it.
not an answer to your problem, but a question to the list:
Do we have a bugtracking tool that we can use to document software problems?
Peter
___
mkgmap-dev
Hello
I try to render a Garmin map of Hungary from OSM data with my own rules and
typ file. At first I used the Tile Splitter, but whatever I did, I didn't
manage to render a good map. Then I extracted county borders (Hungary has 19
counties), and used Osmosis with polygon borders to split the dat
>
> Just an idea that struck me, not a real solution, but a quick improvement:
> At the moment mkgamp drops all the data in the area when it cannot be
> subdivided. It would be at least some improvement if it would just drop some
> data that exceeds the maximum content of an area instead of everyth
Just an idea that struck me, not a real solution, but a quick improvement:
At the moment mkgamp drops all the data in the area when it cannot be
subdivided. It would be at least some improvement if it would just drop some
data that exceeds the maximum content of an area instead of everything.
bye
Hi!
WanMil wrote:
>
> I cannot remember in detail what the patch did. But I remember that I
> came to the conclusion that the whole creation of the subdivisions need
> to be reorganized.
>
>From my analysis today I'd agree. mkgmap would have to subdivide the
geometry itself, not just the are
> Hi!
>
>
> WanMil wrote:
>>
>> The only possible solution is to split the polygon so that it contains
>> less points (either by selecting the splitter split points or by
>> changing the osm data). But that's a try and error solution.
>>
>
> Thanks for the information. In that thread you have been
Hi!
WanMil wrote:
>
> The only possible solution is to split the polygon so that it contains
> less points (either by selecting the splitter split points or by
> changing the osm data). But that's a try and error solution.
>
Thanks for the information. In that thread you have been discussion
Hi Nop,
this is a known mkgmap problem and there have been several questions
about that within the last month.
You might read:
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2011q1/009960.html
The only possible solution is to split the polygon so that it contains
less points (either by selecti
Hi!
I have been trying to build a map of portugal for a while, but it never
quite works out. There is no exception, but mkgmap shows a large number of
messags like this:
Area too small to split at
http://www.openstreetmap.org/?mlat=38.59838&mlon=-7.34522&zoom=17 (reduce
the density of points, l
19 matches
Mail list logo
