Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 2 of 5 FirstFirst 1234 ... LastLast
Results 11 to 20 of 41
  1. #11
    Master bommelb's Avatar
    Join Date
    Jun 2009
    Location
    EU
    Posts
    234
    Rep Power
    103

    Default

    No need to convert the map. Put the map on your gps (sd-card) and make a connection with your computer and start Basecamp. Basecamp is reading the card/map. Right click on the map > Select.
    Same way, but using a usb-stick: Put the map on the usb in X:\Garmin\ . The *.db file you put in the Garmin\SQL\
    Or make a [Only registered and activated users can see links. ]

  2.    Advertissements


  3. #12
    Master bommelb's Avatar
    Join Date
    Jun 2009
    Location
    EU
    Posts
    234
    Rep Power
    103

    Default

    Quote Originally Posted by Giomen View Post
    Please try to change in BaseCamp setting for the altitude value to feet and give report about screen digit label for Topo Lusitania contour line...

    P.S. The reference point is Murteiras Redondas (415.74m) (on the center overhead).
    I take the Sao Gens Mountain, a little bit left from the center.
    Changed the altitude in Basecamp in feet, this is the screen report of Topo Lusitania:
    doma8w
    When the heigt of the mountain is correct (about 510m) the contourline had to show ca. 1560 feet.

  4. #13
    GPSPower Helper

    x-trail's Avatar
    Join Date
    Jul 2010
    Location
    Europe
    Posts
    324
    Rep Power
    163

    Default

    Topo Portugal v3 light is absolutely correct, it displays meters as meters, with a step of 20 meters for each contour.

    The problem is with Topo Lusitania v0.97 in the creation of the map.
    The creators entered the correct numerical values for each contour ( ...300, 310,320,330,...) and they "thought" that those numbers were in meters.
    But Basecamp "thinks" those numbers as feet.
    So, when in Basecamp we choose meters, those numbers are divided by 3.28 and shown as "meters" which is wrong numbers.
    When we choose feet, the number are the same as those the map creators entered, but now Basecamp says they are "feet" which is wrong units.
    So in Basecamp, if we want to see the correct height numbers but wrong height units, we choose custom units and feet in height field.
    The trigonometrical point of S.Gens at 509.32 meters is ALWAYS correct because it's a Label on the map (poi with its height number as a "name")

    BC

    This problem remains in my 3490 and units as meters, the numbers are wrong.

    25443

    Mapsource shows the correct numbers AND correct units, what a surprise!!!!!!!!!!

    MS

    But if we want this map to shown correctly both in Basecamp and devices, the creators of the map have to fix this problem by multiplying every initial number with 3.28 (so they are in feet and not meters) and then Basecamp and device will make the division and show correct numbers ans units (Mapsource will be wrong then...)

  5. #14
    Master sergio2's Avatar
    Join Date
    Nov 2011
    Location
    Spain
    Age
    49
    Posts
    345
    Rep Power
    125

    Default

    Funny !

    When I change unit from meters to feet in BaseCamp, contour lines are now expressed in meters on Topo Lusitania (and in feet on Topo Portugal light)

  6. #15
    GPSPower Helper

    x-trail's Avatar
    Join Date
    Jul 2010
    Location
    Europe
    Posts
    324
    Rep Power
    163

    Default

    Do you like Topo Lusitania v0.97 to be correct in Mapsource, Basecamp and devices?

    TL01

    TL02

    TL03


    UPDATE
    The problem is that all the map tiles are set up with elevation as "feet" and in the contour labels the numbers should be in "feet" too.
    Seven tiles are set up as "feet" but in the contour labels the numbers are in "meters" (like 450 M, 460 M, 470 M...), so Basecamp and devices show the wrong numbers, because all height numbers in the map are considered as "feet" and that's why Basecamp and devices show wrong numbers (like 137 M, 140 M, 143 M.....)
    Unfortunately I could not fix the entire map, I get errors when I try to compose it with Mapsource, using the tiles I've corrected with GPSMapEdit.
    The Mapsource version (with the corrected tiles) shows all the height numbers correct in Basecamp.
    Someone from Portugal should contact the map creators and suggest to edit and correct the following Mapsource tiles:
    35100061.img
    35100069.img
    35100071.img
    35100073.img
    35100075.img
    35100079.img (this is the tile that I open in GPSMapEdit, I change feet to meters as with all above, export it OK, but when I try to compose the map with Mapsource, using this tile, I get an error)
    Last edited by x-trail; 17th April 2016 at 21:35.

  7. #16
    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 sergio2 View Post
    Funny !

    When I change unit from meters to feet in BaseCamp, contour lines are now expressed in meters on Topo Lusitania (and in feet on Topo Portugal light)
    It is the oldest Garmin issue. It is depended from Garmin devices or programs but it occurs from year to year even on Garmin MPC map...

    @x-trail, may be sherco40 and Cnfhbr can make the patch for changes unit in imgtool...
    Last edited by Giomen; 18th April 2016 at 01:21.
    Love your wife? Buy yourself a GPS for answering to her favorite question: "Dear, where are you?".

  8. #17
    Important User
    Join Date
    Aug 2011
    Location
    France
    Posts
    373
    Rep Power
    251

    Default

    Is there a flag in the img that indicates whether the elevation/depth unit is meter or foot?

    I have made some tests on these img and it seems that:
    - the elevation is stored in the label of the contour line.
    - if the label is a number (without non-numeric character after the last digit) Basecamp and Mapsource interprets the number as a measurement in feet.
    - if the label contains letters or spaces, Mapsource and Basecamp have various behaviours... (for example, "500 M" is interpreted as feet by Basecamp but Mapsource considers that it is a string and so it displays it as is , regardless of the elevation unit selected in the menu Preferences...)

    So, in order to work with both Mapsource and Basecamp, label must contain a number (representing the measurement in feet) with no other character (except eventually , some spaces before the digits)..I have modified in this way the img of "S Gens" , it seems to work on Basecamp and Mapsource but I do not have checked on a GPS unit...
    [Only registered and activated users can see links. ]
    Last edited by sherco40; 18th April 2016 at 18:38.

  9. #18
    Navigation software expert

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

    Default

    Roads of Russia TOPO from Navicom have got the label is a number (without non-numeric character after the last digit). In IMG the elevation labels is in feet:
    - Mapsource is no problem regardless of the elevation unit selected in the menu Preferences
    - In some of devices is feet on screen on any units in menu
    Love your wife? Buy yourself a GPS for answering to her favorite question: "Dear, where are you?".

  10. #19
    GPSPower Helper

    x-trail's Avatar
    Join Date
    Jul 2010
    Location
    Europe
    Posts
    324
    Rep Power
    163

    Default

    @ sherco40
    Very nice work, thank you you are totally right!
    I've checked it in 3490 and StreetPilot and works OK, every elevation is in meters!
    It works OK in Mapsource and when I created an .img file, Mapsource gave me no errors!
    (Mapsource gave me errors with my modified tiles).
    Can you please, if it's no trouble for you, to modify the rest [Only registered and activated users can see links. ] to meters, so that we can post a correct map for Mapsource and devices?

  11. #20
    Important User
    Join Date
    Aug 2011
    Location
    France
    Posts
    373
    Rep Power
    251

    Default

    @ x-trail
    Here are the corrected 5 files : [Only registered and activated users can see links. ]

 

 
Page 2 of 5 FirstFirst 1234 ... 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.