Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 21
  1. #11
    Navigation software expert

    Cnfhbr's Avatar
    Join Date
    Jan 2010
    Location
    CIS
    Posts
    1,213
    Rep Power
    476

    Default

    Quote Originally Posted by Smulan View Post
    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.

  2.    Advertissements


  3. #12
    Vip Master
    Smulan's Avatar
    Join Date
    Oct 2010
    Location
    Who knows?
    Posts
    159
    Rep Power
    117

    Default

    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...

  4. #13
    Navigation software expert

    Cnfhbr's Avatar
    Join Date
    Jan 2010
    Location
    CIS
    Posts
    1,213
    Rep Power
    476

    Default

    Quote Originally Posted by Smulan View Post
    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:
    Code:
    Please Login or Register to see the links
    Last edited by Cnfhbr; 2nd April 2016 at 14:11. Reason: added info

  5. #14
    Vip Master
    Smulan's Avatar
    Join Date
    Oct 2010
    Location
    Who knows?
    Posts
    159
    Rep Power
    117

    Default

    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...

  6. #15
    Vip Master
    Smulan's Avatar
    Join Date
    Oct 2010
    Location
    Who knows?
    Posts
    159
    Rep Power
    117

    Default

    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?

  7. #16
    Navigation software expert

    Cnfhbr's Avatar
    Join Date
    Jan 2010
    Location
    CIS
    Posts
    1,213
    Rep Power
    476

    Default

    Quote Originally Posted by Smulan View Post
    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.


    Quote Originally Posted by Smulan View Post
    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. ]


    Quote Originally Posted by Smulan View Post
    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").

  8. #17
    Vip Master
    Smulan's Avatar
    Join Date
    Oct 2010
    Location
    Who knows?
    Posts
    159
    Rep Power
    117

    Default

    I have been working more with this map project and made some progress.
    The map works acceptable both in the gps and with the PC.
    The Detail Count settings suggested by Cnfhbr improved the performance with MapSource, still some strange behaviour when zooming but now acceptable. BaseCamp zooms well.

    The problem with the map names was solved when I gave the map an all new FID with GMapTool also in the MPS and in the Change tab (not quite sure which did it...). ImgTool does not show any of the "original" name (FriPro4) any more but it is still "hidden" in the tiles (from Copyright info ?) as can be seen in Details with GMapTool and also in ImgTool. But it does not cause any problem and is not showing in the map selector of the gps, just the new name given by me.
    Noticed in ImgTool that the TRE parameters are different for the part from FriPro and "my" part with Roads, 1-4-23-13 for FriPro part and 1-4-23-2 for the Roads map. What does the TRE params control?

    The value in the NAME field of the source files (strings) showed up in the map at different zoom levels and was annoying, solved it by simply clearing the content of the NAME field in the corresponding .dbf files since it is not of any real use.

    Also made some adjustments to the Detail Count in Edit Feature Display Properties in MPC in order to try to control when different details should disappear when zooming out. My intention was that foot paths and tractor roads could disappear first when zooming out and so on but I have not seen the real result of this. Maybe some more testing...

    I uploaded the img and the PC install of the district most used by me to Zippy if anyone is interested. Will probably continue with neighburing districts later, the shape source files are made avalible in districts from the "Lantmäteriet".

    The img here: [Only registered and activated users can see links. ]

    The PC install here: [Only registered and activated users can see links. ]

    Edit: made a mistake so that the typ file was not correct in the PC install. Fix with GMTK or editing the install.bat or changing the name of the typ file to Dalarna2016.typ
    Last edited by Smulan; 21st April 2016 at 13:23.

  9. #18
    Navigation software expert

    Giomen's Avatar
    Join Date
    Apr 2009
    Location
    Suomi-Russia
    Age
    49
    Posts
    2,578
    Rep Power
    589

    Default

    Quote Originally Posted by Smulan View Post
    My intention was that foot paths and tractor roads could disappear first when zooming out and so on but I have not seen the real result of this.
    Garmin devices have limitation to max level of zoom for some objects. Foot paths and tractor roads are in this number obviously. I know the one way only it is to change line type.
    Love your wife? Buy yourself a GPS for answering to her favorite question: "Dear, where are you?".

  10. #19
    Vip Master
    Smulan's Avatar
    Join Date
    Oct 2010
    Location
    Who knows?
    Posts
    159
    Rep Power
    117

    Default

    All lines in the "new" part of the map are of type CUSTOMIZABLE_LINE_XX so that is probably not the problem. The reason for using CUSTOMIZABLE_LINE is in order not to use any type already used by the part from FriPro and avoid problems with the typing.

  11. #20
    Navigation software expert

    Cnfhbr's Avatar
    Join Date
    Jan 2010
    Location
    CIS
    Posts
    1,213
    Rep Power
    476

    Default

    Quote Originally Posted by Smulan View Post
    Noticed in ImgTool that the TRE parameters are different for the part from FriPro and "my" part with Roads, 1-4-23-13 for FriPro part and 1-4-23-2 for the Roads map. What does the TRE params control?
    The 4th TRE parameter is described in detail in the 'Edit TRE parameters' tab of ImgTool.
    For example:
    "13" => Detailed Map + Display House # after Street + Display PCode before City
    "2" => Transparent Map


    Quote Originally Posted by Smulan View Post
    The value in the NAME field of the source files (strings) showed up in the map at different zoom levels and was annoying, solved it by simply clearing the content of the NAME field in the corresponding .dbf files since it is not of any real use.
    You can easily hide the labels (for the selected object types) using the MPC configuration or via TYP file.

    MPC:
    [Only registered and activated users can see links. ]

    TYPViewer:
    [Only registered and activated users can see links. ]
    Last edited by Cnfhbr; 21st April 2016 at 10:32.

 

 
Page 2 of 3 FirstFirst 123 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.