Welcome, Guest. Please login or register.

Login with username, password and session length
Forums Search:  


Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Boyd

Pages: [1] 2 3 ... 253
1
I agree. The main attraction of using Mapsource/MapInstall is that you can choose the exact portion of the map you want to send to the device. This was important when GPS units had small amounts of memory. Today.... not so much.

By "MS version set to 0", do you mean that this enables the map to be seen in Basecamp when the GPS (or a flash drive) is connected to the computer? I think that is rather limiting, I prefer to have the map permanently installed so that it can be accessed all the time in both Mapsource and Basecamp. So I provide both options with my own maps.

2
Sorry, I don't do requests. ;) Too many of my own projects, too little time. But IMO, if you want to use maps on your computer in Basecamp, learn how to properly install them instead of accessing them over USB from the GPS.

3
I think that is right, but am not interested in testing Garmin's broken software so I don't know for sure. And it's expecting a lot for a user to figure that out.

But - regardless - this problem has existed for a year now, and there is no mention of it here at GPSFileDepot, except from users like us who discuss it in the forum. So, somebody comes here, downloads a map, follows all the instructions, and then it doesn't work. Not a very good user experience IMO....

4
What an insulting - and clueless - response from Garmin. This issue has nothing to do with 8 bit or 16 bit "GPSFileDepot software".

But there might be a germ of truth (although not for the reasons that "Chris" stated). If I understand this issue correctly, the problem specifically relates to the old registry-based Garmin maps. That would be the majority of maps here at GPSFileDepot.

But Garmin started moving away from this format many years ago, when they first started supporting the Macintosh and created the gmap format. Garmin has used gmap for their own Windows and Macintosh maps for 10 years at least because it works on both platforms. But mapmakers at GPSFileDepot have been very reluctant to switch to the new format, although I have been urging it since 2011 ( https://forums.gpsfiledepot.com/index.php?topic=2383.0 ).

Sorry for the mini-rant, but this has been a pet peeve of mine for awhile, and now - combined with Garmin's arrogant attitude - it has finally started to bite the ordinary person who just wants a map for their GPS. So, if I'm correct about the bug only affecting registry-based maps, then I'd say GPSFileDepot does bear some responsibility for the problems people are having. And GPSFileDepot also bears some responsibility for the large number of old maps here that don't work properly on newer Windows systems because of a well-documented problem with their installers.

But none of this excuses the fact that Garmin broke Basecamp/MapInstall and then slammed the door on further development. That is outrageous IMO. And.... happy anniversary, next week it will be a full year since they introduced the current, broken version.  >:(

5
fo0bar's specific question (if I understood...) was in regard to the effect of polygon draw order when multiple maps of the same draw priority were enabled at the same time. That is an unusal way to use Garmin maps, and I don't see where eaparks addressed that.

But - really - there's something weird with your maps if you are having these issues with basemap conflict. I think you need to sort that out first.

6
Sorry, I have always avoided using multiple maps with the same draw priority. Can't think of a situation where that would have been useful. But it should be simple enough for you to test though.

7
All I can say is that it never happened to me. ;)

Don't confuse draw priority with draw order in the .typ file. The priority affects how the map stacks with other maps that are enabled at the same time. The draw order only affects polygons within the same map.

The draw priority settings should only go from 0 to 31. A setting of 31 should cover up every other Garmin map.

8
Regarding that LIDAR map on my site, it was a fun hack I wanted to try so I built my own system for doing it. But it's really a dead end. It works well in Basecamp/Mapsource, but GPS devices just choke on that much data. It works on my DriveSmart 61 but did not work on any other devices I tested. So, I would not aspire to making maps like that. They are very limited and certainly won't work on an eTrex.

If you want to use raster imagery, your eTrex can handle that natively with .kmz files, but Garmin intentionally cripples it for regular users, so you can only make a very small map. But you can make your own .jnx (birsdeye) files that allow the creation of large maps. Then you can overlay your vector data (roads, poi's) on top of that. I have been doing this on my DriveTrack 71 and really like this kind of "hybrid" map. See my posts starting with #9 in this thread: https://forums.gpsfiledepot.com/index.php?topic=4615.0

Regarding your specific issues, what draw priority have you set for your map? I don't understand why you are getting conflicts with the basemap, have never seen that myself. Try setting a higher priority for the map, I think the basemap has a 0 priority.

And about the cgpsmapper watermark, removing that is trivial. Just create an blank custom typ with invisible text for the watermark point feature. IIRC, it is typ 0x0b.


9
I have a registered copy of GPSMapEdit but haven't really used it in years, and my experience with mkgmap is pretty limited. I use globalmapper and export directly as .mp files for cgpsmapper.

But a few questions come to mind. How are you creating .typ files? I have used many tools for this, but settled in with typviewer a number of years ago, and it's great.

https://sites.google.com/site/sherco40/

I rely very heavily on custom types, so that's an area I have some experience with. This map uses every available typ, and I have created raster imagery where each pixel is a separate polygon.

https://boydsmaps.com/lidar-in-the-pines-sd/

When you say "simple .img maps", what exactly do you mean? Are you creating a single .img file for a large map? I don't know if this is the problem, but I break my maps into tiles that correspond with the boundaries of USGS 7.5 minute quads (from the 24k USGS topo's). This gives me individual .img files anywhere in the range of 300KB up to 5MB depending on the map.

If you want the maps to work in Basecamp, you might also want to actually install them on your computer instead of using them on a USB storage device like the GPS. I use Mapsettoolkit for that. There are other ways, but I just got used to doing it this way

https://sites.google.com/site/cypherman1/

You mentioned ""Area of map selection/coverage" polygons". Are you using the types 0x4a and 0x4b? After years of doing this the wrong way, I have stopped using those polygons in my maps. They were causing problems on a new Garmin automotive device and when I actually read the cpgpmapper docs, it points out that these polygons aren't needed in most situations and can cause various problems. I wanted a white background on my map, instead of the putrid default Garmin background, and I always used 0x4b for that. Now I have just re-purposed another polygon for the same thing.

Not sure if any of this helps, but it shouldn't be hard to accomplish what you want if you set everything up properly. You might try removing the 0x4a and 0x4b polygons for starters and see if that helps. I also like to use Mapsource to check my maps, just as a "reality check". Also a lot faster to work with than Basecamp. You would have to install the map on your computer to do that however, it doesn't support maps on external devices.

10
Assuming that Garmin allows you to install apps, have a look at OruxMaps. It's free and very powerful, with virtually no limits on map size. https://www.oruxmaps.com/cs/en

11
BTW, since your Monterra is an Android device, I assume you could install alternate software. There are a lot of Android apps that don't have Garmin's ridiculous limits on raster imagery. The link I posted above shows Android apps that are compatible with Mobile Atlas Creator: https://boydsmaps.com/mobile-atlas-creator/

[edit] Was looking at your OP again and you mentioned the availability of imagery that is 15,000x15,000 pixels. Those should actually be compatible with your Monterra (assuming the tile limit is 500). Those could be processed as 225 tiles at 1024x1024, so you could use two of those downloads at a time.

12
First, you don't want to turn this into an .img file, that involves converting raster data to vector data and will not give you good results.

I think your Monterra supports 500 raster map tiles (in .kmz files) but am not positive since I haven't used one myself. I know my Montana supports 500 tiles though and have read the Monterra is the same.

But the custom map (.kmz) format just won't allow enough coverage for a map as large as you want. I only offer local maps on my own website, however the Mobile Atlas Creator software I use should be able to do what you want, if you can find your desired map on a server somewhere and create a custom mapsource to access it. Mobile Atlas Creator (MOBAC) is a free open source program that runs on all platforms and can make maps for just about any device and app, including your Monterra.

Custom mapsources are more complicated than I can explain right now, but the MOBAC docs have examples of custom mapsources and you will find more examples with some Google searches.

See my MOBAC page here, it includes a detailed tutorial: https://boydsmaps.com/mobile-atlas-creator/

Section 6 goes into detail about making Garmin maps. See the advanced section about getting around Garmin's tile limits by creating .jnx files. The catch is that you need to have an active Birdseye subscription for that to work however.

You could also use the okmap software described there to create custom maps and .jnx files from other sources, if you don't want to use MOBAC. But Okmap is not free.

13
General Discussion / Re: Downloaded Map Not Complete
« on: April 19, 2019, 09:23:46 AM »
Garmin needs to fix this, it's a disgrace. It has been almost a year since they broke MapInstall.

14
Map Making Support / Re: Changing a GPS devices software version
« on: April 17, 2019, 09:35:52 AM »
My understanding is that the "GPS Software" is the low level firmware for the GPS chipset itself. I don't know why that would affect anything in a map, but it's possible. No experience with creating locked maps.

What is a "key generator"? That sounds like the kind of hacker tool that some people have used to illegally crack Garmin's maps. If so, then the management of this site would not approve of any discussion.

15
Map Making Support / Re: Changing a GPS devices software version
« on: April 17, 2019, 07:41:42 AM »
OK, I see. But still don't understand the part about different data for devices with different serial numbers. Is that just because you customize the data depending on who you give the unit to? I don't see how GPS firmware version would have any effect on that.

If you just want to try different firmware, it is all archived on this website. IIRC, with an old device like yours, you would change the name of the downloaded firmware file to GUPDATE.GCD and place it in the \Garmin folder on the GPS. When you restart the device, it should ask if you want to install older firmware if a newer version is already installed.

http://www.gawisp.com/perry/nuvi/

Not sure how this would help you though. Or do you want to install firmware from a completely different device on your Nuvi? Garmin certainly doesn't want you to do that and I don't think it is easy. People used to discuss this kind of thing in the GPSPassion Nuvi forum. But those days are long gone, there is very little interest in the whole field of dedicated automotive GPS anymore, let alone advanced topics like firmware hacking.

Pages: [1] 2 3 ... 253