The angle of rotation is defined in the original .dbf file like below where "trikt" means the direction of the text. The adjustement of the text in relation to the line, in this case the elevation curve, is also defined in the .dbf
MPC supports only those attributes in shapefiles that are listed in the Help.
Yes, you are right (as usual ) and I can not find any types not listed by MPC in the typ file of the original FriProv4 either.
One thing I have not figured out is the function of the "UseOrientation" argument shown in TYPViewer for the Polylines.
Maybe the answer can be found by reading help files or manuals but that is not the way we seek information...
One thing I have not figured out is the function of the "UseOrientation" argument shown in TYPViewer for the Polylines.
Maybe the answer can be found by reading help files or manuals but that is not the way we seek information...
AFAIK, this applies only to the pattern of a polyline, not the label.
See the tooltip for the "Use orientation": [Only registered and activated users can see links. ]
See also the mkgmap TYP file compiler documentation:
Excellent info! I was not aware of the tooltip info function in TYPViewer, always too quick maybe.
This explains also the behaviour of some thin bitmap lines sometimes not displaying good when in certain angles in relation to the pixels of the display maybe. I will do some experimenting with this and the checkbox "Wide Tool/Thin Tool" in MPC.
I have not used mkgmap but I can see good documentation of the TYP file structure there, more to read then...
Now my "hybrid" map works acceptable in both computer and gps but there are still some details to improve and understand.
In BaseCamp the maps works fine in all zoom levels but in MapSource the roads will start to partly disappear when zooming out. Since I prefer to use MapSource when planning my routes I would like this to work better.
I tried to change the number of layers in MPC from the default 3 to the maximum 5 but I can not see any major difference. The reason for this change is that it seems as the FriPro has 7 zoom levels according to GMapTool and the values of levels and zoom differs between the map with roads and FriPro. Is it possible to control theese values in any way?
GMTK gives a warning "Segment codes exist in other maps too" which of course is correct since part of the "new" map consists of FriPro segment. Theese segments also "knows" that their name is "FriProv4" and that can be confusing in the map selector of some gps models. Is it possible to change this name in any way so that the relation to the FriPro map is lost?
In BaseCamp the maps works fine in all zoom levels but in MapSource the roads will start to partly disappear when zooming out.
Check Detail Count settings in MPC tab "Edit Feature Display Properties" for the types of your roads that disappear.
Originally Posted by Smulan
I tried to change the number of layers in MPC from the default 3 to the maximum 5 but I can not see any major difference.
Try the following classical settings: [Only registered and activated users can see links. ]
Originally Posted by Smulan
Is it possible to change this name in any way so that the relation to the FriPro map is lost?
If it’s no bother, open your map in ImgTool and show us those names (that you want to change) in the screenshot of the main window (or the tab "CDSetNames").
Since the FriPro v5 for the whole of Sweden now is released the drive to produce more areas in the way I did is not so strong.
The purpose was to make an up-to-date map since the FriPro v4 had been there for some years and new roads had been built. And the data was released from Lantmäteriet free to use. My prime use of the Topo map is mountainbiking and walking so fresh road networks are essential. Unfortunately there is no field survey done so the foot paths are not updated for many years, not much to do there.
It was a lot of work and cpu time so generate the maps and a lot of manual work to translate all features from the shape files from Lanmäteriet to Garmin language. And you needed a good dbf editor, the one I used had a 30 days trial period which was ok for my little project but the 30 days are gone now...
I learnt a lot and now I understand much more of how the maps are built.
Credit to friends in this forum pointing me in the right direction when I was lost.
Bookmarks