GPSFileDepot.com
 

News:

Welcome to GPSFileDepot!

Main Menu

Joined .img files fail in MapSource

Started by glendeni, July 29, 2012, 09:53:23 AM

Previous topic - Next topic

glendeni

I have two .img files (stream data for different regions) which I can individually install as a mapset in MapSource using MapsetToolkit.  I want to make a single mapset from them to cover both regions, so used Gmaptool to "join" the .img files into a single .img file. MapsetToolkit installs that file into MS without any apparent problem (though the cpreview and cgpsmapper output lines stream by so quickly that I cannot know for certain whether a warning or error message is there), but when I try to start MapSource I get a popup window with error message "There is a problem with the BigSurTrailmap installation.  Please re-install BigSurTrailmap and start MapSource again".  This occurs both when I do and do not specify a FID during the Gmaptool join process.

I'm at a loss to see what I can do differently - the MapsetToolkit parameters I'm using are the same ones which worked for each of the individual .img files.  The joined .img file does work without problems when loaded into a GPS - so the MapSource installation is the problem.  So am hoping to find some help here.

Jack

PS: anyone know of a way to capture the cpreview and cgpsmapper output streams produced during MapsetToolkit into a file so I can examine them for any warning/error messages?

Boyd

Why are you using gmaptool at all? Can't you just use MapsetToolkit by itself? Works for me, but I always use a blank overview map.

Seldom

If you want to track down the error, add one mapset to BC at a time, or combine both sets of IMG files into a single mapset using cpreview.  To see what's happening try the batch file I've listed here.  FWIW, whenever I get those errors (running my batch file) I've either selected mymap_MDR.img instead of mymap.img as the overviewmap in MapSetToolKit, or included an old version of mymap.mp (overviewmap source) in my cpreview compile.  If you compile the TDB and overview map using the cpreview, you just "Install" the mapsets (let MSTK handle registry settings) using MapSetToolkit.

SmugWimp

#3
You may want to try this from the command line or batch file:

"cgpsmapper ac mymap.mp > .\compilelog.txt"

"cpreview mypv.txt > .\previewlog.txt"

and similar (without quotes, of course). It won't echo on the screen what is happening, but it will write all of the output to the logfile you designate if you add a 'direct' at the end of your command line ("> .\blahblah.txt").

Just a thought. (You had said it zipped by too fast...)

-- Smug
In a nutshell, I get claustrophobic.

glendeni

I've now been able to create a routable map in MapSource/BaseCamp using MapsetToolkit by simply using individual trail and topo and stream regional .img files (13 files) instead of the larger .img files which I had created from them for convenience (3 files, one each for trails, topo, and streams).  It works, but an issue I need to look at further is that cpreview is ending prematurely and fails to create a _HDR file (but that does not appear to be necessary for routing).   I hope to find a less cumbersome process but am happy to now have one that at least works!

Trying to use a batch file to allow saving output from cpreview had not been an option because the cpreview file input to created by MapsetToolkit was being erased after its use, hence I had no input to use in a batch file.  But then cpreview started ending prematurely, upon which my Windows 7 attempts to find a "fix" before actually killing the program - that allowed me to copy the input file prior to its erasure, so I now do have a MapsetToolkit-specific cpreview input file to use for batch tests.

Seldom

#5
Quote from: glendeni on July 31, 2012, 04:29:49 PM
Trying to use a batch file to allow saving output from cpreview had not been an option because the cpreview file input to created by MapsetToolkit was being erased after its use, hence I had no input to use in a batch file.

You need to write your own preview.txt file (SmugWimp's "mypv.txt").  Format for that file is on page 87 of cgpsmapper Manual 2.5.2.
This is a summary from the manual:[MAP]
FileName=..
MapSetName=..
ProductCode=..
ID=00000001
Levels=..
Level0=..
[END-MAP]
[FILES]
img=..
img=..
..
[END-FILES]

glendeni

Well the whole point of trying to use the batch file was to mimic what was going on in MapsetToolkit since that was giving me an error, hence I wanted to use the exact same cpreview input as MapsetToolkit's.  As stated in my last post, I now have a copy of a MapsetToolkit-created cpreview input file so will use that in my testing.

Seldom

Might be good to compare MSTK's text file with the manual to see if there are any discrepancies.