You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to export a map using the GarminCustomMaps plugin for use on a Garmin GPSMAP64s. The area of interest (AOI) is a Canadian forest management unit over 1MM hectares (10,000sq-km) in size.
I've read the tips in the export dialogue, used the highest recommended scale factor (along with countless other iterations with other variables), but no matter what I try, the resolution on the GPS unit is very low to the point that it can't be used. Sometimes the GPS doesn't display anything.
My organization has traditionally used a program called Mapwell which outputs IMG files which scale nicely on our GPS units, but the software is clunky and often doesn't hold our symbology choices when it gets to the GPS.
Has anyone encountered this? I was thinking it might be the size of the AOI, but I tried a much smaller AOI and the quality wasn't much better.
Thank you!
Jon
The text was updated successfully, but these errors were encountered:
I'm trying to export a map using the GarminCustomMaps plugin for use on a Garmin GPSMAP64s. The area of interest (AOI) is a Canadian forest management unit over 1MM hectares (10,000sq-km) in size.
I've read the tips in the export dialogue, used the highest recommended scale factor (along with countless other iterations with other variables), but no matter what I try, the resolution on the GPS unit is very low to the point that it can't be used. Sometimes the GPS doesn't display anything.
My organization has traditionally used a program called Mapwell which outputs IMG files which scale nicely on our GPS units, but the software is clunky and often doesn't hold our symbology choices when it gets to the GPS.
Has anyone encountered this? I was thinking it might be the size of the AOI, but I tried a much smaller AOI and the quality wasn't much better.
Thank you!
Jon
The text was updated successfully, but these errors were encountered: