> MPS record 0x46 ('F') contains family name and FID/PID values.
> Record 0x50 ('P') contains FID/PID values and some flags. 'P' could mean
We have an F record but not a P record. I believe that P is a newer
record, as it is not present in gmapsupp produced by early versions
of mapsource - or perhaps there is something that has to be
present in the input to make it appear.
> The name "mp4" is placed in img header. In my opinion it should be
> repeated in MPS subfile as a record 'V'. I think Mapsorce and Mapinstall
> do that.
We add a V record, it defaults to the string 'OSM map set'. This
can be changed with the mapset-name option (which has to be written
as --x-mapset-name='hello world' as it is not in the options file).
So I suppose that 'OSM map set' is not appearing and maybe it
needs the P record to be present for it to be used?
I've done some more research and it seems that there is more to it than simply adding an extra 0x50 block - even copied the mapinstall mps block into the mkgmap.img & adjusted the length of the block & maintaining the fid accordingly
The results are still the same :
I just get map4
It looks like my original assumption might be right in that some other byte(s) might be set.
I've never seen the 'OSM map set' appearing in my Oregon althouygh I can see it in the gmapsupps
> I've done some more research and it seems that there is more to it than
> simply adding an extra 0x50 block - even copied the mapinstall mps block
> into the mkgmap.img & adjusted the length of the block & maintaining the
> fid accordingly
> The results are still the same :
OK interesting. I've found that I can get the subtitle if I set
offset 0x0e in the gmapsupp to 1 (and perhaps you need all the other
things in mps too - it was the last thing I tried ;)
However setting 0xe is problematic in other ways - about displaying in
Basecamp if I remember.
Changing it to 1 really works ! Brilliant! Now I get a sub description for all my maps !
Also,there doesn't seem to be the need to add an extra 0x50 block in the mps,however 'correct' that might be.
I have a feeling mapinstaller uses old coding practices as it insists on typ names being restricted to a maximum of 12 characters.
As its a gmapsupp, it shouldn't affect Basecamp?
Many thanks for your input.
Any chance for it to be implemented?