BaseCamp 4.2.2 posted

BaseCamp 4.2.2 can be downloaded from http://www8.garmin.com/support/download_details.jsp?id=4449, or autoupdate. The App Store version is in the approval process.

Changes include:
Fixed startup crash that occurred when there was a device connected (App Store)
Fixed issue that where dragging a find result into the user data pane caused a crash
Fixed start-up issue when opening some map installations
Fixed start-up issue with opening Trip Planner
Fixed activity based routing
Fixed issue that preventing Shortest Distance to be set in the routing preferences
Fixed various issues with upgrading legacy databases
Fixed issue with editing routes received from a device
Fixed issue that caused GarMap Sub-Saharan Africa Streetmaps to not display
Fixed issue where creating a waypoint in Trip Planner could cause a crash

0 JaVaWa over 11 years ago

I reported this in the BaseCamp for Windows section:

I don't know whether it has been reported before or not, but I observed a problem with "mixed" routes: when I create a route with different profiles for each route leg, export the route to a GPX file, delete the original route in BaseCamp and re-import the GPX file, the selection of the different profiles isn't preserved (they all get the main route profile).
This also applies to the Mac version of BaseCamp.

In addition to this: When I remove a via point from a route in the Mac version of BaseCamp the custom profiles of the other via points will be reset. The Windows version doesn't show this behaviour.

0 PSEABOLT over 11 years ago

Just a guess but the GPX file probable does no support profiles/activities. GPX being an open eXchange Format, probable means Garmin can't just add another XML schema to be used by BaseCamp .

0 JaVaWa over 11 years ago

It certainly does. The GPX format allows custom extensions, an option that is extensively used by Garmin. In this case the XML scheme http://www.garmin.com/xmlschemas/ViaPointTransportationModeExtensionsv1.xsd is used (not available online where it should be, but when you use the Finder to browse the package contents of the BaseCamp app you can find it in the folder Contents/Resources)
It looks like this:

<?xml version="1.0"?>

<xsd:schema targetNamespace="www.garmin.com/.../v1"

  elementFormDefault="qualified" xmlns="www.garmin.com/.../v1"

  xmlns:xsd="www.w3.org/.../XMLSchema">

  <xsd:annotation>

    <xsd:documentation> This schema defines the Garmin rtept extensions to be used

      with the GPX 1.1 schema. The GPX 1.1 schema is available at

      www.topografix.com/.../gpx.xsd. </xsd:documentation>

  </xsd:annotation>

  <xsd:element name="ViaPointTransportationMode" type="ViaPointTransportationModeExtension_t"/>

  <xsd:complexType name="ViaPointTransportationModeExtension_t">

    <xsd:annotation>

      <xsd:documentation> Route via points are announced stops during a route. This type contains

        data fields intended to be used as child elements of the ViaPoint element in the TripExtension v1 schema

      </xsd:documentation>

    </xsd:annotation>

    <xsd:sequence>

      <xsd:element name="TransportationMode" type="xsd:token">

        <xsd:annotation>

          <xsd:documentation> Suggested transportation mode for this route. If the processor does

            not know about the suggested transportation mode, a default will be chosen. Examples

            include; Automotive, Motorcycling, Walking, Hiking, Mountaineering, Bicyling,

            TourCycling, MountainBiking, ATV, DirtBiking, Truck, RV </xsd:documentation>

        </xsd:annotation>

      </xsd:element>

      <xsd:element name="Extensions" type="Extensions_t" minOccurs="0"/>

    </xsd:sequence>

  </xsd:complexType>

  <xsd:complexType name="Extensions_t">

    <xsd:annotation>

      <xsd:documentation>This type provides the ability to extend any data type that includes

        it.</xsd:documentation>

    </xsd:annotation>

    <xsd:sequence>

      <xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

    </xsd:sequence>

  </xsd:complexType>

</xsd:schema>

0 azdrmn over 11 years ago

I reported this in the BaseCamp for Windows section:

I don't know whether it has been reported before or not, but I observed a problem with "mixed" routes: when I create a route with different profiles for each route leg, export the route to a GPX file, delete the original route in BaseCamp and re-import the GPX file, the selection of the different profiles isn't preserved (they all get the main route profile).
This also applies to the Mac version of BaseCamp.

This is "working as intended". We may be able to revisit that decision, but this was a known short-coming of this feature to make adoption on the devices easier.

In addition to this: When I remove a via point from a route in the Mac version of BaseCamp the custom profiles of the other via points will be reset. The Windows version doesn't show this behaviour.

Doh! We'll take a look into that. Thanks for the heads up.

0 JaVaWa over 11 years ago

This is "working as intended". We may be able to revisit that decision, but this was a known short-coming of this feature to make adoption on the devices easier.

Can you elaborate on this? BaseCamp puts the information about the different profiles into the GPX file, but doesn't use this on import. I know that not every device can use every extension (just like the option of turning via points into shaping points; works in the zumo 3x0 series and certain nüvis, but won't be used by other devices), but since the information is there, I don't understand why BaseCamp doesn't use it...

0 Former Member over 11 years ago

Can you elaborate on this? BaseCamp puts the information about the different profiles into the GPX file, but doesn't use this on import. I know that not every device can use every extension (just like the option of turning via points into shaping points; works in the zumo 3x0 series and certain nüvis, but won't be used by other devices), but since the information is there, I don't understand why BaseCamp doesn't use it...

+1, :confused:

0 azdrmn over 11 years ago

Can you elaborate on this? BaseCamp puts the information about the different profiles into the GPX file, but doesn't use this on import. I know that not every device can use every extension (just like the option of turning via points into shaping points; works in the zumo 3x0 series and certain nüvis, but won't be used by other devices), but since the information is there, I don't understand why BaseCamp doesn't use it...

Hmmm well you got me on that one. The plan was to only have transportation method on the route, but apparently that's not how it got implemented. So, I can see no reason we wouldn't be reading it back in. We'll check on that.

0 PSEABOLT over 11 years ago

Apparently I was using the wrong version to try to reproduce the issue, because I certainly can recreate it with the installed version of 4.2.2. Sorry for the mix up. It lets you pick the custom profile, but then never saves it. That is definitely an issue that will be fixed in the next release. One marginal work around (until it is fixed) is to create routes in the custom profile by switching the app to that profile and creating a route. You can drag the waypoints that are in the original route into the new route. Sorry for the inconvenience.

Are we getting close to the next release? I would really like to apply custom profiles/activities.

Thanks

0 Former Member over 11 years ago

Since the change to black-and-white toolbar icons (v4.2.1?), there are a couple of cosmetic bugs in the highlighting of the currently-selected tool in the toolbar:

(1) If you switch from using a tool in the Map Tools group (hand, zoom, selector, or measure) to clicking a tool in the Creation Tools group (waypoint, route, or track), or vice versa, the previously-selected tool is not un-highlighted. I.e., you end up with two tools being highlighted at the same time.

(2) If you select a new tool from the Tools menu or by typing its shortcut (^H, ^Z, etc.), the new tool is not highlighted and the previous tool(s) remain highlighted.

Fortunately, you can still tell what tool is active by the current cursor.

0 Former Member over 11 years ago

Where to do we go to submit suggestions to improve BaseCamp? There are quite a few little things that would not be hard to fix that could make BC a lot more user friendly.