Garmin killed Birdseye imagery.

Not the correct forum I think.

At least someone should come out to explain the reason for the cancellation, but no one wants to respond

I'll repeat it here what I posted on another thread and I'll also start gathering people around a lawsuit:

GARMIN, hear us out: You sold these devices marketing that feature, that goes back to 64ST era. The only reason I bought a Fenix7X it was because I could have my own satellite image maps. Not because your Birdseye service was great! Quite the opposite, but I subscribed to it just to be able to side load my own maps on my device, since you chose to have a LOCK in your firmware that blocks us from loading unsigned JNX files on the devices.

To fix this is quite simple: You don't need to bring back or support your Birdseye service, just remove the artificial lock you added to our DEVICES and ALLOW THEM TO LOAD unsigned JNX files. That way users like myself and the community will be able to keep this feature alive by creating our own JNX maps.

You have all the rights to shutdown your service, but not to artificially block the feature from working. On the next few days I'll notify you guys formally seeking to address this.

munhozdiego said:

I can assure you there's a number of users out there just like myself who will be able to prove the way your marketed these devices

Forgive my ignorance because I last used the Birdseye subscription with my F6 Sapphire and never made my own JNX or KMZ files, but I seem to remember that they stopped "officially" listing the watches as supported with Birdseye view back when I still had my F6, and I never remember them advertising anything about it supporting 3rd party map files of any type.

Don't get me wrong - I am all for them opening up and allowing 3rd party maps, but you even said that you subscribed because that allowed you to work around a restriction that they already had in place which seems pretty clear that you were not following the intended use.

I know that tone is difficult to get from internet posts, so to be clear I am not disagreeing or arguing.  I am just curious what basis you would have for a lawsuit around this.

I believe you are completely missing the point here:

1 - I'm not working around something that was not intended, go back and read Garmin documentation.

2 - How is a feature not supported when they sold me that subscription and activated it on my Garmin Fenix 7X ?

3 - It's not about supporting 3rd party, its about killing a feature on a device that was sold having the said feature.

I understand some of you love Garmin, but the reality is this love does not go both ways, such shady practices makes it clear day after day.

The same way their provided solution on another thread for Garmin 64ST devices that were sold/advertised having this feature was: Buy a new device that supports Garmin Direct 

Yep... I've been gutted about it for months... My Fenix 5x,5x plus and 6x Sapphire all had more mapping capability than my Fenix 7x because Garmin decided we didn't need or want it anymore. A step backwards, I just hope they bring back.