David, what about my initial question? Would it be interesting to have more maps than google maps? There are a lot of users that prefer other maps.
Saludos, -- luismiguel (@lmorillas) 2016-11-17 15:13 GMT+01:00 David Karger <[email protected]>: > Jay, it's really difficult to diagnose these things without access to > examples. If you can put something on the web, it's more likely someone can > solve it. > > > On 11/14/2016 2:13 PM, Jay Gray wrote: > > > All local-host implementations work (i.e. C: or D: on Win-10), David. > > But none of the remote-host/server implementations works. > > If we don't use the "..data-ex-apikey=OUR-KEY" technique, the app works but > Google will not load the map. > For example, the non-map views of Italian soccer load correctly and behave > as expected. > > If we do use the "..data-ex-apikey=OUR-KEY" technique, the app locks up; > nothing loads (no facets, text, non-map views, etc.). > > To reiterate, we're running HTTPS under nginx. > Our thinking is that it's an HTTPS-related issue. > > /jay > > > > On Monday, November 14, 2016 at 11:54:53 AM UTC-6, David Karger wrote: >> >> Jim, trying to load data from a different site seems asking for trouble >> (exhibit's never been particularly good at that); does it work if you link >> to your own local copy of the data? >> >> >> On 11/14/2016 12:06 PM, Jay Gray wrote: >> >> >> Hi David >> >> We cannot get the approach using data-ex-apikey='OUR-KEY' to work. >> >> We have a version of Italian Soccer that uses 'data.json' rather than: >> >> http://www.simile-widgets.org/exhibit3/examples/other-versions/HEAD/italian-soccer/italianSoccer.txt >> >> The 'data.json' version works perfectly. >> >> We are running an HTTPS environment (https://domain.io) >> Because the 'italianSoccer.txt' file is not served using CORS, we can't >> load it. >> >> We are using these libraries: >> <script type='text/javascript' >> src='https://api.simile-widgets.org/exhibit/HEAD/exhibit-api.js'></script> >> <script rel='exhibit-extension' type='text/javascript' >> src='https://api.simile-widgets.org/exhibit/HEAD/extensions/map/map-extension.js'></script> >> >> For example, the 'Thumbnail View' and the 'Table View' work as expected. >> >> Then, after the core libraries, we load: >> <link rel='exhibit-extension' >> href='https://api.simile-widgets.org/exhibit/HEAD/extensions/map/map-extension.js' >> data-ex-apikey='OUR-KEY' /> >> >> The instance hangs. It's not just that the map does not load; the instance >> is jammed. >> >> When we enclose the 'data-ex-apikey' script in comments, the instance >> re-loads correctly; Thumbnail View and the Table View work as expected. >> >> In Chrome Developer Tools, the only message we receive is: >> Google Maps API error: MissingKeyMapError >> js?callback=Exhibit.MapExtension.gmapCallback:37 >> >> https://developers.google.com/maps/documentation/javascript/error-messages#missing-key-map-error >> >> The next approach DOES work in non-Exhibit apps: >> <script async defer >> src='https://maps.googleapis.com/maps/api/js?key=OUR-KEY&callback=initMap'></script> >> >> For example, we have several geoJSON maps that run correctly using >> 'OUR-KEY' above. >> >> Can you help us out with getting either of the gmapKey methods to work >> with HTTPS? >> Many thanks. >> >> /jay >> >> >> >> On Monday, November 14, 2016 at 8:04:46 AM UTC-6, David Karger wrote: >>> >>> no need to go to github; it's right here: >>> >>> >>> http://www.simile-widgets.org/exhibit3/examples/other-versions/HEAD/italian-soccer/italian-soccer.html >>> >>> >>> On 11/14/2016 8:39 AM, Jay Gray wrote: >>> >>> OK, we'll experiment with this mode: >>> >>> https://raw.githubusercontent.com/simile-widgets/exhibit/master/scripted/demos/italian-soccer/italian-soccer.html >>> >>> /j >>> >>> On Monday, November 14, 2016 at 6:38:26 AM UTC-6, Jay Gray wrote: >>>> >>>> Thanks for the suggestion David. >>>> Would you point me to the documentation? >>>> We'll test it and report back. >>>> The Google changes are breaking many folks' maps - we need to get our >>>> Exhibit maps back online. >>>> Our problems began when we changed our domain name, and the Google Maps >>>> 'grandfathering' no longer applied. >>>> >>>> /jay >>>> >>>> >>>> On Monday, November 14, 2016 at 6:28:04 AM UTC-6, David Karger wrote: >>>>> >>>>> Instead of adding a ?gmapkey parameter to the url, use the >>>>> data-ex-apikey attribute in the tag where you load the extention. >>>>> >>>>> >>>>> On 11/14/2016 6:41 AM, Jay Gray wrote: >>>>> >>>>> Yes, Luis, it is your Exhibit. >>>>> You original used Exhibit 2; we have not updated it, although have >>>>> learned from it. >>>>> The reason I featured it in this post is because it uses your Gmap ID. >>>>> While it may work for you (because Google "grandfathered existing sites >>>>> that do not use a Gmap ID), it does not work on our IP address. >>>>> >>>>> We've encountered what may be a conflict between the Exhibit 3 method >>>>> of loading a Google Map ID and the Google Processor. We described it here: >>>>> https://groups.google.com/forum/#!topic/simile-widgets/_SXCaMfLi7g >>>>> >>>>> Google changed their policies on June 22. See discussion here: >>>>> https://churchthemes.com/page-didnt-load-google-maps-correctly/ >>>>> >>>>> So my question to you is: >>>>> How do you assign your Gmap ID to an Exhibit 3 "../map-extension.js" >>>>> and have it correctly processed by Google (where you can verify in Google >>>>> Chrome dev tools that it has been properly parsed)? >>>>> >>>>> Perhaps we should be using: >>>>> >>>>> https://api.simile-widgets.org/exhibit/HEAD/extensions/map/scripts/google-maps-v2-view.js >>>>> >>>>> My thought was to ask you to 'debug' is issue because you have >>>>> successfully used the Gmap ID in the past. >>>>> Would you be willing to update one of your Exhibits that use Google >>>>> Maps, apply your Google MAP API Key, and show use an implementation that >>>>> works? >>>>> >>>>> We'll then use your implementation, replace your API key with ours, and >>>>> test it. >>>>> >>>>> FYI, the Chrome platform basically requires HTTPS: >>>>> All Exhibit libraries are HTTPS active, but you may also have to update >>>>> your Bootstrap libraries. >>>>> >>>>> Tell me if I need to do something to help with your testing. >>>>> >>>>> Many thanks for your continuing help. >>>>> >>>>> /jay >>>>> >>>>> >>>>> >>>>> >>>>> On Monday, November 14, 2016 at 4:50:05 AM UTC-6, Luis Miguel Morillas >>>>> wrote: >>>>>> >>>>>> Hi, Jay, >>>>>> >>>>>> What map are you talking about? Is it mine? >>>>>> >>>>>> I think you are mixing exhibit2 and exhibit3 code. >>>>>> >>>>>> Saludos, >>>>>> >>>>>> -- luismiguel (@lmorillas) >>>>>> >>>>>> >>>>>> 2016-11-14 11:15 GMT+01:00 Jay Gray <[email protected]>: >>>>>> > Hey Luis >>>>>> > >>>>>> > May I ask you about your use of Google Maps? >>>>>> > We've looked at your map and timeline with the data type "Ciências, >>>>>> > Artes e >>>>>> > Humanidades" >>>>>> > That Exhibit contains 117 items >>>>>> > >>>>>> > You use: >>>>>> > >>>>>> > href=" >>>>>> > >>>>>> > http://api.simile-widgets.org/exhibit/3.1.0rc/extensions/map/map-extension.js?service=google2&gmapKey=ABQIAAAA5JLLfCE9c7HAtg25QM2KCRRyiP6mHEsQpwvxB19-hS9Kgd8RYhSXEtJVAXDUCZPqwtZZi7-HUYUYrw"; >>>>>> > >>>>>> > We can't load your map using the string: >>>>>> > "service=google2&gmapKey=YOUR-ID" >>>>>> > >>>>>> > If you used the latest Exhibit lib: >>>>>> > >>>>>> > <script rel='exhibit-extension' type='text/javascript' >>>>>> > >>>>>> > src='https://api.simile-widgets.org/exhibit/HEAD/extensions/map/map-extension.js'></script> >>>>>> > >>>>>> > how would you assign your gmapKey to "../map-extension.js"? >>>>>> > Can you implement an update that runs in Chrome? >>>>>> > >>>>>> > Thanks for your help here. >>>>>> > >>>>>> > /jay >>>>>> > >>>>>> > >>>>>> > On Monday, September 19, 2016 at 2:23:59 AM UTC-5, Luis Miguel >>>>>> > Morillas >>>>>> > wrote: >>>>>> >> >>>>>> >> Hi all >>>>>> >> >>>>>> >> What's the reason exhibit 3 only supports Google Maps? An easy >>>>>> >> maintenance? >>>>>> >> >>>>>> >> Could it be interesting to work integrating osm, leaflet or other? >>>>>> >> >>>>>> >> >>>>>> >> Best, >>>>>> >> >>>>>> >> -- luismiguel (@lmorillas) >>>>>> > >>>>>> > -- >>>>>> > You received this message because you are subscribed to the Google >>>>>> > Groups >>>>>> > "SIMILE Widgets" group. >>>>>> > To unsubscribe from this group and stop receiving emails from it, >>>>>> > send an >>>>>> > email to [email protected]. >>>>>> > To post to this group, send email to [email protected]. >>>>>> > Visit this group at https://groups.google.com/group/simile-widgets. >>>>>> > For more options, visit https://groups.google.com/d/optout. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "SIMILE Widgets" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To post to this group, send email to [email protected]. >>>>> Visit this group at https://groups.google.com/group/simile-widgets. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "SIMILE Widgets" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at https://groups.google.com/group/simile-widgets. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "SIMILE Widgets" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/simile-widgets. >> For more options, visit https://groups.google.com/d/optout. >> >> > -- > You received this message because you are subscribed to the Google Groups > "SIMILE Widgets" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/simile-widgets. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "SIMILE Widgets" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/simile-widgets. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "SIMILE Widgets" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/simile-widgets. For more options, visit https://groups.google.com/d/optout.
