[mapguide-users] MapGuide Fusion Error for Google Maps API

[David Bowen]

Thanks for providing this Jackie. Couple of additional questions:

1. Just to confirm, is the Bing Maps API fully supported in both the Fusion
and React viewers?

2. Is there any method to address Apache server vulnerabilities that are
found once MGOS is released, without having to wait for an MGOS update?

Thanks,
David

On Thu, Feb 9, 2023 at 7:28 AM Jackie Ng <jumpinjackie at gmail.com> wrote:

> If you want to use the mapguide-react-layout viewer over Fusion, I (as the
> primary maintainer of the react viewer) am going to warn you up-front:
>
> While we try to aim for maximum Fusion widget and Flexible Layout
> compatibility in this viewer, Google Maps will not be supported by this
> viewer, nor will I entertain any thoughts about integrating support for it
> or any of the surrounding services (like Places, StreetView, etc, etc). The
> Google Maps API is too much of a technological and legal minefield to
> integrate with other map viewer libraries. There's a reason OpenLayers 3+
> doesn't support it out of the box (eg:
> https://github.com/openlayers/openlayers/issues/2205), and neither will
> we.
>
> Frankly, that OpenLayers v2 (and thus Fusion by inference) had "supported"
> Google Maps all this time is just plain luck. The only reason I haven't
> fully yanked out this support in Fusion is that there might be backlash
> from users and so my stance on the matter is purely "use at your own
> risk/discretion".
>
> My viewpoint on external map service integration is always going to be:
> Please use Bing Maps or OpenStreetMap instead. They have much more
> technologically and legally friendly integration stories.
>
> - Jackie
>
> You wrote:
>
> We had a meeting with Gordon Luckett to discuss this issue and he provided
>
> insight into what's causing it and a workaround solution. The Fusion
>
> template relies on OpenLayers v2 and with Google Maps API v3.50, something
>
> has changed that prevents it from working with OpenLayers v2, resulting in
>
> Fusion errors.
>
> As a workaround solution, if you remove both the GoogleScript tag, from the
>
> XML, and live Google base maps in Maestro, the Fusion errors no longer
>
> occur. You can replace the live Google base maps with the tiled versions,
>
> which allows continuity for the end user.
>
> It was also suggested to consider pivoting to using the React viewer
>
> instead of Fusion, which is something I hope to look into in the future.
>
> Hope this helps,
>
> David
>
>
>
> --
> *Please Note: I no longer create new posts or post replies to any OSGeo
> mailing list through nabble. As a result, you most likely won't see this
> message appear on nabble's view of any OSGeo mailing list and may only see
> this message through mailing list archives or depending on your mailing
> list subscription settings, through daily message digests or automated
> notifications from the mailing lists.*
> _______________________________________________
> mapguide-users mailing list
> mapguide-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapguide-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapguide-users/attachments/20230216/250fea72/attachment.htm>