For my cyclemaps I use {Family-ID}.typ (10010 and 20010.typ) so it would be
nice if that would be possible to use this too.
-
Steve wrote:
I think I would build separately, and then combine in a second step.
However, everything is possible:
overview-mapname: mapset1
family-id: 10
> What if you want to have multiple map layers in a single gmapsupp.img
> (for old devices that do not support .img file selection)? Then I guess
> you could want to have up to one TYP file per family-id.
>
> Or would you have multiple overview maps (one per family-id) anyway?
I think I would bui
Can you send your reply again Steve, I cant read it.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Wed, Nov 16, 2011 at 02:29:54PM +, Steve Ratcliffe wrote:
>>Another issue is that mkgmap compiles my typfile.txt into
>>MKG(FID).TYP. Is it possible to specify the name of the typ file that
>>is created?
>
>That was a bad choice I agree. How about using --overview-mapname so
>it would be n
Hi Minko
[Sorry about previous blank email!]
> The header size
>
> This is not specified when I export my typ file to txt with typ viewer so it
> is set to short (old format).
> I noticed this give problems with extended polygon types like this one
Right, I was working with the minimum header
On 16/11/11 10:20, Minko wrote:
> Hi Steve,
> Thanks for integrating the typ/txt file into mkgmap. It seems to work pretty
> well, except for a few remarks:
>
> The header size
>
> This is not specified when I export my typ file to txt with typ viewer so it
> is set to short (old format).
> I not
Hi Steve,
Thanks for integrating the typ/txt file into mkgmap. It seems to work pretty
well, except for a few remarks:
The header size
This is not specified when I export my typ file to txt with typ viewer so it is
set to short (old format).
I noticed this give problems with extended polygon t
Hi
The TYP compiler is now integrated into mkgmap on the typ branch.
You should be able to supply a .txt file on the command line and it will
be compiled along with any other files.
If the gmapsupp option is given then the compiled TYP will be copied
into the gmapsupp as you would expect.
Like
