Answers.Body: <p>As Graham has noted in a comment, the change in map reflects a change in <a href="https://operations.osmfoundation.org/policies/tiles/" rel="nofollow noreferrer">terms of use</a> and <a href="https://lists.openstreetmap.org/pipermail/talk/2016-June/076106.html" rel="nofollow noreferrer">distribution methods</a> in July 2016 that necessitated the <a href="https://issues.civicrm.org/jira/browse/CRM-19400" rel="nofollow noreferrer">removal of direct links</a> to MapQuest tiles. </p>
  
  <ul>
  <li><a href="https://civicrm.stackexchange.com/questions/14433">MapQuest Issue - Direct Tile Access No Longer Supported?</a></li>
  <li><a href="https://stackoverflow.com/q/38315300">mapquest direct tile access discontinued</a> (SO)</li>
  </ul>
  
  <p>The plain map you are seeing is the <a href="https://carto.com/location-data-services/basemaps/" rel="nofollow noreferrer">Carto Light</a> basemap from Carto, which was adopted as of 4.7.19.</p>
  
  <p>On our sites, we do not use the built-in maps for the public, but a <a href="http://leafletjs.com/" rel="nofollow noreferrer">Leaflet</a> implementation for Drupal Views. Thus, this change only affected internal users who use the mapping, which does not occur often in our use cases. But for those who do, you can override this choice by adding a custom <code>OpenStreetMaps.tpl</code> template, with the URLs appropriate to your tile provider of choice.</p>
  
  <p><a href="https://i.sstatic.net/zi9fZ.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/zi9fZ.png" alt="Carto Light All"></a> <a href="https://i.sstatic.net/not6t.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/not6t.png" alt="Carto Dark Nolabels"></a></p>
  
  <p>I am not sure if any Carto tiles other than the basic light and dark (with or without labels) are licensed for this kind of use, however. The OSM wiki does provide a <a href="http://wiki.openstreetmap.org/wiki/Tiles" rel="nofollow noreferrer">list of tile servers</a> where you can explore alternatives.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-12T16:41:10.317Z
Answers.Text: Thanks for this information. Maybe I missed the men on this. Essentially what you're saying is that the CiviCRM mapping implementation using OSM data is now at best severely hobbled.
Answers.UserDisplayName: Graham
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-12T16:48:10.543Z
Answers.Text: LOL, I didn't see that you'd commented on your own question. But yes, I suppose if you prefer the old MapQuest tiles, this is a downgrade. See http://wiki.openstreetmap.org/wiki/Tiles for some other alternatives.
Answers.UserDisplayName: choster
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-12T16:59:40.793Z
Answers.Text: What I don't understand - yet - is why a Civi/Drupal site that I have running an older version of Civi is still able to render OSM maps perfectly well. According to the information I've read I should be seeing an alert message instead to tell me that it's all been switched off?
Answers.UserDisplayName: Graham
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-12T14:48:50.573Z
Answers.LastActivityDate: 2017-09-12T16:49:23.647Z
Answers.LastEditDate: 2017-09-12T16:49:23.647Z
Answers.UserDisplayName: choster
Body: <p>I've just upgraded a site that was running Civi 4.6.30 to 4.7.24. I use OpenStreetMaps as the Mapping provider. My maps are now appearing as featureless grey maps rather than what I'd expect. </p>
  
  <p>The same seems to be true when I test it on <a href="http://dmaster.demo.civicrm.org" rel="nofollow noreferrer">http://dmaster.demo.civicrm.org</a></p>
  
  <p>My old site continues to render the map in full colour.</p>
  
  <p>The template concerned (CRM/Contact/Form/Task/Map/OpenStreetMaps.tpl) certainly looks very different between the two versions of Civi that I've upgraded from/to.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-09-12T13:43:34.817Z
Comments.Text: This issue: https://issues.civicrm.org/jira/browse/CRM-19400 - explains at least some of the rationale for recent changes to the OpenStreetMaps mapping option.
Comments.UserDisplayName: Graham
Tags: <map>
Title: Why is OpenStreetMaps in Civi 4.7.24 rendering a featureless grey map?
ThreadText: # Why is OpenStreetMaps in Civi 4.7.24 rendering a featureless grey map?
  
  (Asked by: username_0 on 2017-09-12)
  
  I've just upgraded a site that was running Civi 4.6.30 to 4.7.24. I use OpenStreetMaps as the Mapping provider. My maps are now appearing as featureless grey maps rather than what I'd expect.
  
  The same seems to be true when I test it on <http://dmaster.demo.civicrm.org>
  
  My old site continues to render the map in full colour.
  
  The template concerned (CRM/Contact/Form/Task/Map/OpenStreetMaps.tpl) certainly looks very different between the two versions of Civi that I've upgraded from/to.
  
  **Tags:** map
  
  > **Comments:**
  > **username_0**: This issue: https://issues.civicrm.org/jira/browse/CRM-19400 - explains at least some of the rationale for recent changes to the OpenStreetMaps mapping option.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-09-12. Score: 2
  
  As username_0 has noted in a comment, the change in map reflects a change in [terms of use](https://operations.osmfoundation.org/policies/tiles/) and [distribution methods](https://lists.openstreetmap.org/pipermail/talk/2016-June/076106.html) in July 2016 that necessitated the [removal of direct links](https://issues.civicrm.org/jira/browse/CRM-19400) to MapQuest tiles.
  
  * [MapQuest Issue - Direct Tile Access No Longer Supported?](https://civicrm.stackexchange.com/questions/14433)
  * [mapquest direct tile access discontinued](https://stackoverflow.com/q/38315300) (SO)
  
  The plain map you are seeing is the [Carto Light](https://carto.com/location-data-services/basemaps/) basemap from Carto, which was adopted as of 4.7.19.
  
  On our sites, we do not use the built-in maps for the public, but a [Leaflet](http://leafletjs.com/) implementation for Drupal Views. Thus, this change only affected internal users who use the mapping, which does not occur often in our use cases. But for those who do, you can override this choice by adding a custom `OpenStreetMaps.tpl` template, with the URLs appropriate to your tile provider of choice.
  
  [![Carto Light All](https://i.sstatic.net/zi9fZ.png)](https://i.sstatic.net/zi9fZ.png) [![Carto Dark Nolabels](https://i.sstatic.net/not6t.png)](https://i.sstatic.net/not6t.png)
  
  I am not sure if any Carto tiles other than the basic light and dark (with or without labels) are licensed for this kind of use, however. The OSM wiki does provide a [list of tile servers](http://wiki.openstreetmap.org/wiki/Tiles) where you can explore alternatives.
  
  > **Comments:**
  > **username_0**: Thanks for this information. Maybe I missed the men on this. Essentially what you're saying is that the CiviCRM mapping implementation using OSM data is now at best severely hobbled.  
  > **username_1**: LOL, I didn't see that you'd commented on your own question. But yes, I suppose if you prefer the old MapQuest tiles, this is a downgrade. See http://wiki.openstreetmap.org/wiki/Tiles for some other alternatives.  
  > **username_0**: What I don't understand - yet - is why a Civi/Drupal site that I have running an older version of Civi is still able to render OSM maps perfectly well. According to the information I've read I should be seeing an alert message instead to tell me that it's all been switched off?  
  
  ---
  
  