Welcome, Guest. Please login or register.

Login with username, password and session length
Forums Search:  


Author Topic: Garmin polyline TYP 0x17 conflicts  (Read 5856 times)

babj615

  • Expert Advisor
  • *****
  • Posts: 266
  • Karma: -4
  • The cache is a lie!
    • View Profile
    • Garmin Oregon 6xx Wiki
Garmin polyline TYP 0x17 conflicts
« on: November 04, 2013, 11:49:49 PM »
Anyone familiar with any potential conflicts with custom TYP 0x17 polylines?

I am using them for bridle trails in my maps, and they are displayed properly on my various Garmin GPS receivers, but they do not display properly in BaseCamp or MapSource.  When I mouse over them in BC/MS, the trail name is displayed, so the trail is present, but BC/MS both refuse to display my custom TYP 0x17. I have checked to be sure the colors used are 'Garmin Colors', and as I said, they show just fine on my Garmin GPSr.

Any and all input much appreciated.
Garmin GPSMap 60cs, Dakota 20, Colorado 400t, Oregon 300/400t/450/550t/650/650t, Montana 650, Lowrance Endura Sierra, nuvi 3790, iPhone 3G/4/4s
Geocaching ID: Atlas Cached
OpenCaching.com Ambassador

93ToyTruck

  • Jr. Member
  • **
  • Posts: 44
  • Karma: 0
    • View Profile
    • California Trail Map
Re: Garmin polyline TYP 0x17 conflicts
« Reply #1 on: November 23, 2013, 11:30:33 PM »
0x17 isn't a predefined polyline type. I've always re-purposed predefined types. My observation has been that the behavior of the line depends on how Garmin intended it to be used. There are some lines that won't appear at higher levels regardless of the EndLevel. I suggest hijacking a line type that isn't being used otherwise.

babj615

  • Expert Advisor
  • *****
  • Posts: 266
  • Karma: -4
  • The cache is a lie!
    • View Profile
    • Garmin Oregon 6xx Wiki
Re: Garmin polyline TYP 0x17 conflicts
« Reply #2 on: November 24, 2013, 12:31:11 AM »
If I use known types for my map, will that change how other maps loaded on the same GPSr show that line, or do my TYP files only affect my maps?
Garmin GPSMap 60cs, Dakota 20, Colorado 400t, Oregon 300/400t/450/550t/650/650t, Montana 650, Lowrance Endura Sierra, nuvi 3790, iPhone 3G/4/4s
Geocaching ID: Atlas Cached
OpenCaching.com Ambassador

93ToyTruck

  • Jr. Member
  • **
  • Posts: 44
  • Karma: 0
    • View Profile
    • California Trail Map
Re: Garmin polyline TYP 0x17 conflicts
« Reply #3 on: November 24, 2013, 08:37:17 AM »
Changing the TYP only affects your map. I've re-purposed almost all of the polyline types for a trail map that I created. Other maps appear normally in BaseCamp and on the gps receivers.


babj615

  • Expert Advisor
  • *****
  • Posts: 266
  • Karma: -4
  • The cache is a lie!
    • View Profile
    • Garmin Oregon 6xx Wiki
Re: Garmin polyline TYP 0x17 conflicts
« Reply #4 on: November 24, 2013, 12:43:24 PM »
Thank you!

This opens up more options to me :)
Garmin GPSMap 60cs, Dakota 20, Colorado 400t, Oregon 300/400t/450/550t/650/650t, Montana 650, Lowrance Endura Sierra, nuvi 3790, iPhone 3G/4/4s
Geocaching ID: Atlas Cached
OpenCaching.com Ambassador

scdiscdi

  • Newbie
  • *
  • Posts: 1
  • Karma: 0
    • View Profile
Re: Garmin polyline TYP 0x17 conflicts
« Reply #5 on: November 25, 2013, 08:18:17 AM »
Hello

Line 0x17 is invisible. The lines in this picture with the nodes are routable. Others like 0x11 0x12 0x13 will crash Mapsource.



babj615

  • Expert Advisor
  • *****
  • Posts: 266
  • Karma: -4
  • The cache is a lie!
    • View Profile
    • Garmin Oregon 6xx Wiki
Re: Garmin polyline TYP 0x17 conflicts
« Reply #6 on: November 25, 2013, 01:47:37 PM »
scdiscdi, under what circumstances will 0x11 0x12 0x13 crash Mapsource?
Garmin GPSMap 60cs, Dakota 20, Colorado 400t, Oregon 300/400t/450/550t/650/650t, Montana 650, Lowrance Endura Sierra, nuvi 3790, iPhone 3G/4/4s
Geocaching ID: Atlas Cached
OpenCaching.com Ambassador

 

anything