Suffix for waypoints can't be set to 0000 [Bug 45]

[ConiKost]

If you try to set a 'Suffix' to '0000' under Setup -> Waypoints, it saves '10000' instead.
Reported to Garmin, let's see, if they consider this as a bug.

[GPSrChive]

I am curious to find out also, as, technically, a '0000' suffix is no different than no suffix. I can not imagine why anyone would have tried to use all zeros for a suffix, and it never occurred to me!

[987]

I am curious to find out also, as, technically, a '0000' suffix is no different than no suffix. I can not imagine why anyone would have tried to use all zeros for a suffix, and it never occurred to me!

That is not entirely true. Even if one sets the suffix to 0000 and the unit changes it to 10000, next time when MARK is pressed, the unit will start from the lowest non used number, which may be 0001 in case there is no waypoint with this number. If it already exists, it will instead skip forward to the next free number. It does not seem possible to turn off the suffix. (i tried on a GPSMAP 66 but imagine it works the same)

[GPSrChive]

Now that is definitely a bug.

Posted to the GPSMAP 66s/st, GPSMAP 66i, GPSMAP 66sr, and Montana 7x0 Common Issues pages.

[ConiKost]

I am curious to find out also, as, technically, a '0000' suffix is no different than no suffix. I can not imagine why anyone would have tried to use all zeros for a suffix, and it never occurred to me!

I don't understand this. Why is '0000' equal to no suffix?
Maybe I completly missunderstood the function.
But isn't the suffix just added upon using 'Mark'?

[GPSrChive]

I am curious to find out also, as, technically, a '0000' suffix is no different than no suffix. I can not imagine why anyone would have tried to use all zeros for a suffix, and it never occurred to me!

I don't understand this. Why is '0000' equal to no suffix?
Maybe I completly missunderstood the function.
But isn't the suffix just added upon using 'Mark'?

When a waypoint is marked and saved using the same name as an existing waypoint, standard operating procedure is to append the name with the first available numerical suffix, starting with "1", which is the same as "01", "001", and "0001".

The original (or first) waypoint to be saved with a unique name is effectively "0000", but that suffix is not displayed as it is not necessary to display suffix numbers when only one file exists with the name used.

The next waypoint saved with that name will get the "1" suffix, then the next "2", and then "3", and so on...

The leading zeros indicate they support four digit suffix numbers, or a potential total of 10,000 waypoints with the same name, all differentiated by a unique suffix, the original (hidden) being "0000".

[ConiKost]

The original (or first) waypoint to be saved with a unique name is effectively "0000", but that suffix is not displayed as it is not necessary to display suffix numbers when only one file exists with the name used.

I just played with that function and I think, I missundestood the function so far.
The 'Suffix' option is an auto increment, which is automatically by 1 increased, when I use 'Mark Waypoint' and save such waypoint. So I can see, that the 'Suffix' configuration field increased.

Makes so far sense to me.

But I don't understand, when it's the case, when no suffix is being displayed? You don't have such option to configure, as Suffix is not optional. When I do set suffix to '0001' or '0000', which is displayed as '10000', and have no further waypoints, 'Mark Waypoint' creates a default name including '0001' Suffix. So from this point of view, I would have never guessed, that '0000' is some special variant.

The leading zeros indicate they support four digit suffix numbers, or a potential total of 10,000 waypoints with the same name, all differentiated by a unique suffix, the original (hidden) being "0000".

Makes sense, since Garmin officially says, max 10.000 waypoints supported.

At least Garmin doesn't seem to accept that as a bug in their first reply.

[GPSrChive]

Please also see GPSrChive > Montana 7x0 > Setup > Waypoints for additional information.

[ConiKost]

Problem still exists in latest firmware 8.20. I am not sure, if Garmin will this fix.

[ConiKost]

Still not fixed in 8.40.