Google Maps API v2 no more supported. Is v3 or other provider the solution ?

[pitchke]

Google Maps API v2 is no more supported and we now get a message on maps "For development purposes only" as Exhibit v3 is made to work with Maps API v2. A simple example available here.

Browser debug console reports "NoApiKeys" error (even if you provide a valid key) which is described here:

"If you are loading Maps JavaScript API from the deprecated v2 path with an old v2 key, you will get the NoApiKeys warning, even if you specified the key parameter. Please check the v2 to v3 upgrade guide and migrate your application to Maps JavaScript API v3."

I tested the behaviour by creating a Map API v3 key but the result is the same.
If I understand well the current statement for Exhibit v3 here, we can't fallback to another provider today?

I am wondering on which solution(s) we should work:

• Migrating Exhibit v3 to use Map v3 API (guide), - I don't know how complex this is, maybe I could try to contribute.
• restore alternative providers like OpenLayers or BingMap, or ...
• Maybe other solution(s) you may think about, and if my above investigation is wrong please correct me.

Thanks too keep Exhibit alive as it was and is still a really nice and useful project !

[jjon]

Pierre, @pitchke,
A while ago I was experimenting with Exhibit using Google Maps v3 and found it relatively straightforward. My main aim was to explore linking the timeline and maps visualizations dynamically.

You can find this experiment here: http://neolography.com/staging/itinExhibitSketchII.html. Except for the Maps and Exhibit libraries, the page is self-contained. This was very much an experiment, so I'm sure that there's all sorts of things wrong with it, but perhaps you'll find the source instructive.

Note that I was attempting to host all the exhibit software (version: "3.1.2-rc3") locally. Note also that the header that calls the google maps software uses the data-ex-apikey attribute:

<link href="../common-js/exhibit-master/scripted/src/extensions/map/map-extension.js?bundle=false"
        data-ex-apikey='MyMapsV3ApiKey'
        type="text/javascript" 
        rel="exhibit-extension"
/>

I share your view that Exhibit is a really nice and useful project!

[karger]

So in fact, we did the work several years ago to deal with the api changeover, and it's been deployed on the HEAD branch for quite some time, but some numbskull (me) neglected to update the current version of exhibit. I've now done so; if you visit the exhibit page you'll see the map is working fine. Note that the source code still has lots of anachronistic mentions of api v2, but it's actually using v3.

…

------ Original Message ------ From: "Jon Crump" <[email protected]> To: "simile-widgets/exhibit" <[email protected]> Cc: "Subscribed" <[email protected]> Sent: 10/25/2018 5:50:50 PM Subject: Re: [simile-widgets/exhibit] Google Maps API v2 no more supported. Is v3 or other provider the solution ? (#192)

Pierre, @pitchke <https://github.com/pitchke>, A while ago I was experimenting with Exhibit using Google Maps v3 and found it relatively straightforward. My main aim was to explore linking the timeline and maps visualizations dynamically. You can find this experiment here: http://neolography.com/staging/itinExhibitSketchII.html. Except for the Maps and Exhibit libraries, the page is self-contained. This was very much an experiment, so I'm sure that there's all sorts of things wrong with it, but perhaps you'll find the source instructive. Note that I was attempting to host all the exhibit software (version: "3.1.2-rc3") locally. Note also that the header that calls the google maps software uses the data-ex-apikey attribute: <link href="../common-js/exhibit-master/scripted/src/extensions/map/map-extension.js?bundle=false" data-ex-apikey='MyMapsV3ApiKey' type="text/javascript" rel="exhibit-extension" /> I share your view that Exhibit is a really nice and useful project! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#192 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABFpXlZd5bFVqHk4wctGgnzY_j3c1n6uks5uojI6gaJpZM4X6XCD>.