Jump to content
Sign in to follow this  
Followers 5
jotne

Mapsource 6.5 Beta

Recommended Posts

http://www.garmin.com/support/download_details.jsp?id=625

 

Changes made from version 6.3 to 6.5 BETA:

 

Updated the default document format to the new GDB version 2 format.

Due to the availability of the Garmin nRoute application, no changes were made to the MapSource GPS tracking functionality.

Provided the capability for the user to define up to 64 custom waypoint symbols.

Added the capability to import GPX documents that use both versions 1.0 and 1.1 of the GPX schema and export GPX documents using version 1.1 of the schema.

Added the ability to batch-edit certain properties of user waypoints.

Added the ability to open GDB vers. 1, GDB vers. 2, MPS, GPX vers. 1.0, GPX vers. 1.1, and PCX5 documents using the “Open…” command in the “File” menu. Added the ability to save data to GDB version 1, GDB version 2, MPS, tab-delimited text, DXF, and GPX vers. 1.1 documents using the “Save As…” command in the “File” menu. Removed the “Import…” and “Export…” commands from the “File” menu.

Simplified the selection of symbols in the Waypoint Properties dialog.

Added the capability to do online software updates for non-Asian versions of MapSource.

Provided a right-click context menu available from the main MapSource window for showing and hiding of the MapSource toolbars. In previous versions, this could only be accomplished from the View menu.

Made some modifications to the Route Properties dialog to simplify the user experience. MapSource now disables the “Insert Waypoints” button when there are no waypoints in the active document, and disables the “Show on Map” when the route is empty. It is also now possible to insert multiple via points into the route in a single insert.

Added the capability for users to create a route by selecting one or more waypoints in the list on the waypoints tab and then selecting the appropriate menu option from the right-click context menu.

Added technology to allow for address searching in Asian map products.

Moved the capability to adjust map detail from the preferences to the view menu/toolbar and removed the map detail slider control from the display tab of the preferences property sheet.

Added the Icelandic Grid (ISN93).

Added visual feedback on the vertical route profile so that the user knows the exact altitude and distance for a point they click on the graph. Also added the capability to select a second arbitrary point on the graph and determine the altitude and distance changes between the two points.

Added new auto-routing configuration option to avoid carpool lanes, if desired. Note that this feature is not supported in all map products.

Changed the “OK” button to a “Close” button on non-editable properties dialogs (such as the tide prediction dialog) to decrease user confusion about how to exit the dialog.

Added the capability for a user to be able to automatically select all the maps adjacent to a route, track, or waypoint.

Modified drawing code so that the map labels are now drawn on top of GPS data like routes and tracks, but still appear below waypoint labels and the 'find results' marker.

Added direction arrows on selected routes so that it is easier for users to discern which direction a selected route is going.

Lowered the minimum speed on the routing properties page to allow the use of more realistic speeds for generating routes using alternate vehicles (i.e., bicycles) and pedestrians. Also raised the maximum speed to allow more flexibility for the user in route planning.

Added category and subcategory classifications to property pages for map features. This was done to help users better understand the classification scheme and be able to use it in feature finds.

Added ability to zoom in on sections of a route profile.

Reorganized categories used by the find places and find nearest dialogs to make finding items more intuitive.

Added a reset button to clear the search parameter fields on the find dialog.

Changed the help menu commands. We now have the command “MapSource help” which replaces the two commands “Contents” and “Index…” for accessing the MapSource help file. This was necessary due to changes made by Microsoft in the behavior of some system help file functions.

Modified the context menu that a user gets when he or she clicks on the map window to have the following behaviors: A context menu in the map window will only apply to one GPS feature (the one under the mouse when the user right-clicks), and non route-specific menu items should not be in the route context menu.

Modified MapSource so that all files, regardless of type, are added to the 'most recently opened files' list on the File menu.

Added the capability to create waypoints with known altitudes at any arbitrary position on maps that contain elevation data. On such map products, previous versions of MapSource would only fill in the altitude field in waypoints that were created on contour lines or point features that had a known altitude.

Removed option for sending terrain-shading data to GPS from the Maps tab. The determination to send this information will now be made automatically depending on whether the GPS to which the maps are being sent supports it.

Added technology to the find dialog for address and intersection searches that will exclude cities from the list of available cities that don't have any associated road information.

Modified the process for transferring maps to a GPS device so that MapSource checks to ensure that it can successfully unlock all the maps being transferred on the destination GPS before starting the lengthy index-building step. This will prevent customers from having to sit through the index building of their map set and then find out that some of the maps are unable to be unlocked (and therefore unusable) on their GPS.

Changed the label of the column on the Routes tab that was previously labeled “waypoints” to be labeled “via points”.

Improved the error text that a user gets when a write operation to a USB card programmer fails to verify.

Added some improvements to the device auto-detection code to decrease the likelihood of a failure while searching for user devices.

Changed behavior of route dialog so that if a user aborts the calculation of driving directions when clicking on the driving directions tab, they will stay on the Via Points tab and not see the Driving Directions tab with empty driving directions.

Removed term “non-dangerous” that was in the description of some marine map features.

Put in improved error reporting to assist the user when problems are encountered trying to transfer a map set to a Garmin iQue device.

Added additional error reporting parameters such as stack traces to certain error messages to improve the ability to debug the error.

Changed the logic in the driving directions generation software to better discriminate between the need for a “u-turn” and a “sharp left/right” turn in appropriate conditions.

Modified MapSource to provide the user with more useful feedback in certain situations where the program failed because of an invalid entry in the MapSource registry entries.

Modified the transfer dialogs to correctly reflect the fact that the cfQue device does not currently support route transfer.

Modified the waypoint dialog to correctly truncate the timestamp string when it was too long for the field it is displayed in.

Added an improved description of the removable media devices that show up in the list of devices that are automatically detected.

Added additional postal code filtering to the finder logic to help speed up searches being done when a postal code is provided.

Modified the 'find nearest' logic to speed up the 'find nearest' searches.

Modified 'find places' and 'find nearest' so that the user has the ability to abort finds that take a long time.

Added elevation information to the position information that we currently display on the status bar when the user hovers the mouse over the map. This will be available in certain map products that include altitude information.

Repositioned the toolbar on the Track Properties page so that it would be easier for users to understand that the toolbar functions will work in the name field as well as the trackpoints list.

Modified the 'find nearest' dialog to remember when the user types an entry in the 'containing' field.

Modified the 'find nearest' dialog so that the 'Waypoints' category option is not displayed if there are not currently any waypoints in MapSource (so that the find would always fail).

Modified the 'find' dialog so that the Find button will be pushed if user hits the enter key after typing in some entries in the find parameters.

Modified MapSource so that when a waypoint is created on a city map feature, the application will automatically use the 'City' icon.

Modified the 'find places' dialog so that input typed in the parameter fields is saved after the user clicks 'find'. This was done to create a consistent behavior with the find nearest dialog. The previous version of the find places dialog saved the input data immediately after the user typed it into the field (whether find was hit or not). It was decided that this could be confusing to users.

Added support for scroll-wheel in the auto-complete fields on the 'find' dialog.

Removed maximize and minimize buttons from the Waypoint dialog since these buttons were not appropriate and did not work correctly.

Added the 'select all' menu option to the context menu that is brought up when the user right-clicks on the via-points list in the route dialog.

Fixed issue where the 'find results' marker on the map was not correctly cleared in the map window when the user cancelled out of a 'find recent' or 'find nearest' search.

Fixed issue where some controls on the route dialog were not being drawn correctly when the dialog was being resized.

Fixed issue where detailed map data was not correctly display in some maps associated with certain BlueChart products.

Fixed issue where the auto-router would fail when trying to route in certain map conditions.

Fixed issue where MapSource would fail when certain modifications were made to a waypoint in the Waypoint Properties dialog.

Fixed issue where the Waypoint label was covered up by the map feature label in some instances.

Fixed issue where vertical route profiler could fail on extremely long routes.

Reworded potentially confusing prompt that was displayed when MapSource was started with no map products installed.

Fixed issue where the wrong color was being used to fill in certain non-map areas at some zoom scales.

Fixed issue on the 'find nearest' dialog where the search distance was not being updated correctly if the user modified this value and then initiated a search by hitting the Enter key.

Changed behavior of “Show on Map” for individual route and track points to be consistent with the waypoint’s behavior.

Fixed some localization issues in several Asian languages.

Fixed several auto-routing issues.

Fixed a vertical profiling issue.

Fixed issue with trying to create a route near the North or South pole.

Share this post


Link to post

SUPPORT FOR 64 CUSTOM WAYPOINT SYMBOLS!!! AWESOME!!! :blink:

 

When downloading custom waypoints from a color GPSr, they would show up as generic "Waypoint" symbols in MapSource. And when you sent those waypoints back to the GPSr, they would still be generic "Waypoint".

 

Sounds like this feature will allow MapSource to accept and retain your custom waypoints!

 

...but why 64??? My GPSMAP 60C only has 24? Will we be gettting more in the GPSrs in a future firmware upgrade?

 

Added the ability to batch-edit certain properties of user waypoints.

Edited by Neo_Geo

Share this post


Link to post

It has successfully imported 1000 caches from a GSAK generated gpx file without any problems :blink: .

Share this post


Link to post
It won't import my GPXSpinner spun files. :blink:

I've noticed that GPXspinner does not create "validatable" gpx files. If you attempt to validate the created file against the gpx schema, it does not meet the spec.

Share this post


Link to post
Has anyone actually tried the beta?  If so, do you find it stable?

 

Thanks,

 

TheHFamily

I have it installed and so far I have had no problems with it. I have associated the .gpx extension with Mapsource and now I can just double click on a GPX file to open it up in Mapsource. It works great. Besides the GPX import, the two things that I like in this new version are:

 

1. The ability to select map segments along a route. This will be great from my next trip. I always had to do this manually before.

2. The ability to change properties on multiple waypoints at the same time (like the waypoint symbol).

 

Give it a try. RM

 

Edit: I just noticed another nice improvement. When you open an old .mps file, it no longer gives you that stupid warning telling you that you are opening a file with the old format. This is nice for direct exporting from GSAK where the .mps file is passed to Mapsource.

Edited by Rocket Man

Share this post


Link to post

Pretty cool Prime Suspect. Would you share the icons?

 

Also is there a way to make the icons correct on a very large GPX file?

Share this post


Link to post
Pretty cool Prime Suspect. Would you share the icons?

 

Also is there a way to make the icons correct on a very large GPX file?

You can download the icons here.

MapSource is looking for "Custom 0" through "Custom 7" in the symbol tag.

<sym>Custom 0</sym>

 

Should be fairly easy to set up most of the 3rd party GPX utilities to do the translation. The associated numbers for each icon are listed in the zip file.

Share this post


Link to post

I have installed my custom symbols in identical slots in both my 60CS and in MapSource. I am able to download waypoints with these symbols and have them retain those symbols in MapSource, but when I try to upload the waypoints back to the GPSr, their symbols are getting converted to the "Small City" symbol. What am I missing?

Share this post


Link to post

MapSource is looking for "Custom 0" through "Custom 7" in the symbol tag.

<sym>Custom 0</sym>

Interesting. If you have a GPSBabel that's newer than Oct. 1, it'll support those icons but the numbers will be off by one.

 

One of the rules of programming is to not let "programmerisms" escape into user visiable space, so I started numbering them from 1 instead of 0.

Share this post


Link to post
...but why 64??? My GPSMAP 60C only has 24? Will we be gettting more in the GPSrs in a future firmware upgrade?

My Quest has 64 custom waypoints... but mapsource only supports 8 (the first 8? It looks like the *last* 8, since I have over 30 already edited and none show up in Mapsource). Already mailed Garmin about this... I want all 64 covered. =8- )

Share this post


Link to post

Hi Robert

 

I've emailed Garmin on this issue also but my biggest gripe with my Quest (and something that I'm sure can be fixed in the firmware) is that the unit does not beep directions (guidance beeps) from within the GPS unit itself while connected to external 12v power. The unit only provides voice guidance through the external speaker while connected to 12v and only beeps while running off of the internal battery. Since I don't care for the voice guidance & don't care to use it, I have to be disconnected from 12v to hear any guidance beeps. Other than that, the Quest is an awesome unit for it's intended purpose. :D

Edited by SergZak

Share this post


Link to post
I adapted the 8 custom icons to the GC type icons. Pretty cool.

Now, if Garmin would just make it possible to use multiple icons as the geocaching icon type.

 

Brian

Share this post


Link to post
Pretty cool Prime Suspect. Would you share the icons?

 

Also is there a way to make the icons correct on a very large GPX file?

You can download the icons here.

MapSource is looking for "Custom 0" through "Custom 7" in the symbol tag.

<sym>Custom 0</sym>

 

Should be fairly easy to set up most of the 3rd party GPX utilities to do the translation. The associated numbers for each icon are listed in the zip file.

Where do I unzip the files to?

Share this post


Link to post
when I try to upload the waypoints back to the GPSr, their symbols are getting converted to the "Small City" symbol. What am I missing?

To be clear, does anyone know of host software successfully sending waypoints using the custom icons to the units are are you guys all tweaking them on the unit?

 

If not, that saves me the effort of snooping the serial/USB line to see how they circumvented this problem

Share this post


Link to post
To be clear, does anyone know of host software successfully sending waypoints using the custom icons to the units are are you guys all tweaking them on the unit?

 

If not, that saves me the effort of snooping the serial/USB line to see how they circumvented this problem

I have a feeling that my problem comes from running into this issue. I have yet to hear of someone successfully uploading waypoints with custom symbols from software to their Garmin GPS and having them retain those symbols.

Share this post


Link to post

I got a response from Garmin that says that the custom waypoint symbol transfer problem is actually in the unit. It appears that the 60, 76c and Quest all have the same problem. Namely, if you send waypoints to the unit from MapSource all custom waypoints are converted to the dot. Also if you send waypoints from the unit to MapSource, any waypoint whose symbol is greater than the 6th custom waypoint symbol is changed to use the 6th symbol. Go figure. It looks like we have to wait for a firmware update... :(

Share this post


Link to post

Ah! I already mailed Garmin that Mapsource 6.3 didn't use the custom waypoints correctly, but it indeed seems broken in 6.5 also. I even copied the bmp files over from the xImage dir to the My Garmin\Custom Waypoints subdir and renamed them to match the naming convention used. No luck...

 

And I use the 1st to 36th symbol, but none of the 1st to 5th show up... :D

 

So, we wait for the next Mapsource and/or firmware update for the Quest. :huh:

Edited by elsinga

Share this post


Link to post

Hrmph. I told Garmin I thought the firmware was hosed w.r.t. transfer of custom icons months ago and didn't get a response. It's likely I was ignored becuase I was doing it with an "unsupported third party application" (never mind that I'm the lead developer on that application) but it's still interesting to watch this unfold.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  
Followers 5

×
×
  • Create New...