09-05-2017 03:23 PM
We have worked well since installing Geomedia Desktop 2016 using the bings maps key, but after upgrading to version 2016.2, the service never again viewed the Bing maps service, we only get a blank window.
Please, it is important that we connect the service as well as have the product updated.
I hope someone can support us with a solution.
Greetings to the community
09-07-2017 11:41 AM
This is a bug in the GM 16.2 delivery and has been reported to development. If you want to log a sales force ticket it will be attached to the existing development ticket.
Bottom line the problem has been reported and submitted to development for correction.
09-11-2017 10:41 AM
And, do you know about additional issues with Geomedia Objects and Geomedia Viewer?, because we experimented several issues with both and Geomedia Desktop 16.2
01-16-2018 09:02 AM
We have spent considerable time on the problem, but do not yet have a solution. The Bing Maps API changes were apparently substantial, and the work required to become compatible with the latest API from that platform has been large for us and is still not complete. At this time it appears that with the 16.5 release in March we will likely still not be compatible, but I hope to make it available in a minor release after 16.5. - Hal
04-06-2018 04:56 AM
There is no change in status. The changes did not make the 2018 release, and our energy has been primarily directed to that release since my previous update to this thread. I remain hopeful that we will be able to resolve the issue in a post-release Update, hopefully one we plan for the May/June timeframe, but that remains tentative until we can go deeper into the problem. - Hal
04-11-2018 02:13 PM
There is no work-around to recommend for this issue. The fix will require new code changes in GeoMedia to accomodate the new Bing Maps format.
07-26-2018 07:45 AM
I still have this problem with GeoMedia 2018 (Version 16.5.0 Build 1109) - can you confirm that?
Is there a solution in the near future?