Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 1 to 10 of 20

Hybrid View

  1. #1
    Ballebar
    Guest

    Default

    @qrumba

    Have you checked that the MS flag (MapSource flag) is 0 in the IMG-file?
    Files created with MapSource / MapInstall will get MS flag = 1. BaseCamp needs MS flag = 0 when reading memory card IMG files.

    Example with MS flag = 1
    Code:
    Please Login or Register to see the links
    Check the IMG-file with gMapTool. If MS=1 then change that with gMapTool. Enable "☑ Advanced options" and then use "Write" tab and "☑ Set version in header" -> "MS 0".

  2.    Advertissements


  3. #2
    Member
    Join Date
    Oct 2010
    Location
    Austria / Vienna
    Posts
    22
    Rep Power
    16

    Default

    @Ballebar

    Yes, MS flag is 0 in IMG-file - this was the first I checked.
    When starting BaseCamp the progression bar for Wanderkarte is red and it stays red till the message comes, that it is not a valid Garmin chart. BaseCamp works some seconds (~ half minute) for this.
    I have many other charts on virtual floppy drive working with BaseCamp very well.
    I will try it with other 'Wander- & Reitkarten' - maybe it works with 'Inselkarte' and report results here.

  4. #3
    Master bommelb's Avatar
    Join Date
    Jun 2009
    Location
    EU
    Posts
    161
    Rep Power
    112

    Default

    Other question according to the Mapsoruce Flag (Ms=1 or Ms=0).
    When You use this method to see a map from the openstreetmap-community (velomap, openmtbmap, openfietsmap etc.) and You change the Ms(=0) you can see the map in Basecamp which is on gps or sd-card (connected to PC). So Far So good.
    But in Basecamp is also a Global Application Basemap (v2 for the latest Basecamp 3.2.2.). It looks like the gmapsupp.img is transparant because You see the Basemap together with Your gmapsupp.img. (example: You see the highways double). Gmapsupp.img from Garmin (created with MPC ?) don't have this.
    You can change the transparency of the osm-gmapsupp.img, but that has no effect. Osm-maps are normally made whith Mkgmap. Maybe that's the problem but maybe also the solution.
    Somebody recognize this "problem" and have the solution/answer the solve this or can give a parameter which is maybe wrong in a gmapsupp.img (and can be changed by Gmaptool).

    @Edit : latest version of Mkgmap (30/11/2011) should solved this problem. Just wait now for the new maps with this version.
    Last edited by bommelb; 2nd December 2011 at 04:47 PM.

 

 

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
  •