Yeah! Alec's solution worked on AIMS2017 as well! :)
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapguide-users
That's awesome, Jackie. Thanks
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapguide-users
Yes to this fix being in 3.1.2.
And 3.1.2 (RC or final, yet to decide) should drop end of this week or early
next week. Going through a shortlist of other FDO and Fusion annoyances.
- Jackie
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
Hi Jackie,
Any word on whether this fix will be included in 3.1.2? Also, when will
3.1.2 be available?
Thanks
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
Hi All,
I've posted a test build of Fusion with the Google Maps fix:
http://download.osgeo.org/mapguide/patches/fusion3.1.2_googlemapsfix/fusion-3.1.2-pre-GoogleMapsFix.zip
The fix in question is: https://trac.osgeo.org/fusion/changeset/3049
The 3.1.2 release or RC (yet to decide) coming up
Hi, as said by Alec, without this function the selection with shift-click
does not work.
The solution proposed by Alec to change the name in the fusion to the
function (from find to find2) worked. In this way both basemaps and
shift-click selection work.
--
Sent from:
Really? This function again?
It seems every breakage of Google Maps in Fusion revolves around this
function.
If removing this function indeed fixes the issue, then I'll get these
changes into Fusion pronto. I'm starting the 3.1.2 release cycle soon, so if
this is indeed the fix, I want it in
Hi from memory the original issue was caused by Google Maps API implementing
the Array.prototype.find as it became standard in ECMA 2015.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/find
Commenting out the function at the time resolved the issue but
Ok, I understand where the problem is!!
Inside the Fusion (compressed or no) there is the same function that was
present in the patch of your post. After removing the following part of code
from Fusion, all started working properly!!
Part of code removed from fusion:
Array.prototype.find =
Hi, I tried to use a version of Openlayers without changes (2.13.1) instead
of using Fusion. In this way everything works correctly. If I try to insert
the patch that I find in the following page (created to solve other problems
with the ApiKey), however, the problem reoccurs.
ide-users on behalf of
Charl Jameson Beukes
Sent: Wednesday, February 20, 2019 8:22:03 AM
To: 'MapGuide Users Mail List'
Subject: Re: [mapguide-users] Google Offset in MGOS 3.1.1
Tried to fiddle with the mapguide fusionSF.js file trying to get the WKT for
the World Azimuthal Equidistant projec
sage-
From: mapguide-users On Behalf Of Alec
Bell
Sent: 20 February 2019 02:55 AM
To: mapguide-users@lists.osgeo.org
Subject: Re: [mapguide-users] Google Offset in MGOS 3.1.1
Going by this link Google Maps changed to azimuthal projection not sure if that
means the api has changed as well.
There'
Going by this link Google Maps changed to azimuthal projection not sure if
that means the api has changed as well.
There's nothing in the release notes for Google Maps API indicating this
change.
https://gis.stackexchange.com/questions/302795/what-is-the-new-projection-for-google-maps-called
Hi,
I don't think they fix it yet, if this is actually a issue should be fixed
by Google Map or Mapguide itself.
I will just use 3.34 for now, and you should send the Google Map API team
regarding to this issue as well. I didn't get any responses from them.
Then, test the newer version they
I got the same problem with 3.36 and 3.35 and set the version to 3.34 to
continue use.
Has anyone gotten any response from Google about the problem?
Thanks...
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
OK. Today v3.33 just seems to have dropped off. 3.34 still works but for how
long?
Will there be a MapGuide fix by the time we have to move to v3.35 or newer?
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
Google Map JS API V3.34 will still be working with MapGuide, but not V3.35.
Yeah, I should set the version to 3.34 for now.
I also sent Google Map API team a feedback, and hope they may fix it at some
point. It works for me once for sending them a request about Google Map API
full screen wasn't
The Monthly may end up changing the API next month and you might have the
same issue.
I haven't seen the change that offsets everything in Google API yet.
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
I also turned to the Google release notes and dint find anything after 3.35
which worked perfectly till last night as well. Glad someone fixed it cause
I was busy testing all possible coordinate systems.
On Tue, 13 Nov 2018, 19:37 RenoSun I wonder why we couldn't use the latest version. What did
I wonder why we couldn't use the latest version. What did Google Map API
change to cause this offset issue?
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
Same here with AIMS 2017, fixed by changing the XML of the fusion from
http://maps.google.com/maps/api/js?key=APIKEYv=weeklyuse_slippy=true
to
http://maps.google.com/maps/api/js?key=APIKEYv=quarterlyuse_slippy=true
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
Solved it: Google has updated it's API in the past couple of days. This
offsets the map.
I just had to force it to use the older API:
https://maps.googleapis.com/maps/api/js?key=AIzaSyD9iypThfjzfCwasdaasdfasdfe_dGs*v=3.33*
--
Sent from:
Same problem, now it's clear that this is not only my problem :)
Whats going on with it?
Kajar
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
This affects all MGOS 3.1.1 sites currently using Google. just happened
overnight.
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
24 matches
Mail list logo
