[Only registered and activated users can see links. ] - Garmin proprietary compiler for creating .IMG maps. Input formats: Esri Shapefile .SHP, AutoCAD Drawing Exchange Format .DXF, Raster DEM .BIL and Wavefront .OBJ. Here in the section you can find cra cked version of the program. Please read the manual and see the samples in the program folder first.
[Only registered and activated users can see links. ] - An unofficial compiler for Garmin IMG maps. Unfortunately, stoped of developing. Latest version 100d. Input format - .MP or widely known as Polish text format. Creates maps in non-NT and pseudo-NT.
Versions 0.85 and earlier can decompile non-NT .img maps into .mp.
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ] - Another unofficial free compiler. Understands the format .mp. Sometimes it is usefull for decompilation and analysis.
[Only registered and activated users can see links. ] - Another unofficial commercial complier of Garmin .IMG Maps, automatic vectorization and drawing software
[Only registered and activated users can see links. ] - Simplifies the installation of maps in Mapsource, can set draw priority to maps, transparency, change FID etc.
[Only registered and activated users can see links. ] - A very useful tool for manipulation of Garmin IMG maps.
[Only registered and activated users can see links. ]
Exemplary CAD drawing software
AutoCAD
ArcGIS
MapInfo Professional
[Only registered and activated users can see links. ] - An editor of the Polish .mp format and also a very good decompiler of non-NT Garmin IMG maps into .mp.
Converters
[Only registered and activated users can see links. ] - nice program for editing and converting from and to various formats. Supports many vector formats and can convert from and to .mp. Also it has ability for drawing maps.
[Only registered and activated users can see links. ]- a script for converting Polish .mp format into Garmin .shp
Useful information
[Only registered and activated users can see links. ] - Free program for downloading high-resolution satellite imagery and conventional maps
[Only registered and activated users can see links. ]
Format .shp: [Only registered and activated users can see links. ]
Format .dxf: [Only registered and activated users can see links. ]
Format .mp.: [Only registered and activated users can see links. ]
Format .IMG: Description of [Only registered and activated users can see links. ] format, sources [Only registered and activated users can see links. ], mkgmap, [Only registered and activated users can see links. ].
Last edited by catymag; 4th November 2012 at 04:32 PM.
Reason: added mp2shp link+ new MPC 8 link&GmapTool&Global mapper
I must say that I tried in the past to create a map for the area where I live, since the existent one had some mistakes and some minor streets totally lacking.
I succeeded at the end, but it turned to be an extraordinary time-consuming task. Be prepared!
Can anyone with a GPSMAP share their "best practices" for getting map data onto the GPS? I recently acquired a GPSMAP 62s. I understand all the tools (gmaptool, tkmap, gimgtools, mapsource patched and map install) however there appears still a number of directions one can go in. For instance, I'm running all the tools in a VirtualBox Windows XP session vs native OSX just because there seems to be more support for Windows (including the patched products) available. I have also found that the GPSMap 62s accepts over 4GB of map data as long as maps are in separate .img files, however the total map tile count among all the files needs to be < 4000 tiles. It appears if 4000 tiles is exceeded, the unit does not list the additional maps in the map setup screen. This really made the 32GB flash card I purchased useless. Through trial and error of creating my own .img files < 4000 tiles, I was only able to get the SDHC card to ~9GB.
Now there is the topic of map data. Map data can reside in the form of .gmap files for Basecamp/Mapsource (older format left out for this discussion) and .img files on the SDHC. The SDHC can be accessed inside the device itself via USB cable or placed into the computer's SDHC reader. It appears Basecamp is able to detect and read the SDHC .img map data when it's inserted into a SDHC reader. .img data can be converted to older MapSource (and .gmap with another tool) however in that direction routing information is lost.
Now the issue of map installation. Mapsource patched is good for creating a number of .img files. It allows one to create many .img files so the 4GB FAT32 file limit is overcome, while allowing user to use max 4000 tiles. Mapinstall (at least the Mac version) looks slick, however I"m not exactly sure what it's doing. Mapinstall Mac looks like it had the 4GB FAT32 file limit even though 4000 max tiles were no where near reached.
So how do folks operate efficiently? Here is my takeaways and place correct/comment if you can:
o For the .iso TOPO images (NW, NE, etc..) that get installed as .gmap, those have routing data intact so are a good source
o For .img files pulled from elsewhere (unlocked?) leave those on the device SDHC or some directory and place on device as necessary??
o Mapsource patched Windows is useful for creating .img on local hard disk
o Basecamp is good for KML data overlays. Unsure how to get the data out of this?
Your thoughts appreciated.
Thanks
Also there are a number of .img files with their MS flag == 1. There are mostly TOPOs generated from Garmin data. Can anyone comment on how they use this flag? I'm assuming it should be kept == 1 if the map was generated from data held in your Basecamp/MS and ==0 if Basecamp/MS data is non-existent.
Thanks
Last edited by Neil; 27th August 2013 at 07:01 AM.
Reason: Merged 2 consecutive posts.
Lots of questions and or/observations there. Actually most answers can be found/confirmed by searching the forum.
In essence, MS Flag needs to be 0 for BC to see an image. Change it easily with ImgTool or with GMAPTool.
Most of your other observations are basically correct but if you're suggesting literally that 'Mapsource patched ..... allows one to create many .img files so the 4GB FAT32 file limit is overcome' [my empathis], that's incorrect. As you have stated, the file size limit [actually 4Gibibyte - 1 byte] is a FAT32 limitation, and it cannot be [physically] overcome. From what you wrote elsewhere in your post you understand that, so probably what you mean is that you can create larger single images up to 4GiB by joining smaller maps from gmap folders, and yes that's right. You can also join smaller images together using GMAPTool. In either case beware of overlapping data from different FID maps. As well as the ~4000 tile limit with modern outdoor units, there is also an upper map limit of ~16 i think.
The problem is often not so much the size of the card, but the nature of the data on it. I've used both a 32GB and a 64GB [reformatted to FAT32] in some modern units and they work fine. But depending on the size of the tiles and the number of maps you'll soon run up against the other limits as you've found and long before a 32GB card is anywhere near full. 62c has 1.7GB of internal memory as well, but that isn't a great help. Numerous smaller cards with individual maps is the best policy imo but others may disagree.
[Only registered and activated users can see links. ]. [Only registered and activated users can see links. ]. [Only registered and activated users can see links. ].
'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned. Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam. [Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].
Thanks for the reply. Yes, I worded things incorrectly. 4GB - 1byte is the FAT32 limit for a file, aka single .img. You can have multiple .img's on the device, however all maps inside the imgs must be < 4,000 total maps. I have noticed as the map count grows, it takes longer for the device to start up. So far, loading up nearly 4K maps in separate .img files on the device (these are mostly Garmin TOPOs), I'm at about 8.6GB. Given that, I suspect for the person trying to cram in the most amount of map tiles on an SDHC and also add some raster images, 16GB card should be sufficient. For the personal sticking with the single standard 4GB .img, which I suspect would have generally much less map tiles (and faster load time), 8GB SDHC is probably a good choice.
I would still like to hear more about how people efficiently manage their maps.
Also, hoping someone works on an open source Garmin IMG creation tool/library like cgpsmapper and/or tkmap. It would be very useful so both Open Street Map and NOAA ENC/S-92 data could be automatically converted vs a manual process. Even better, this could be done on Unix.
Yes I agree with that. The more maps and tiles the unit has on it's internal or external memory, the slower the load time during boot. Changing cards is a pain i know though especially on the go in challenging conditions.
'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned. Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam. [Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].
Bookmarks