I see Google Maps support geojson. Looking at the docs here: https://developers.google.com/maps/documentation/javascript/datalayer#load_geojson
Given the last exampl
As a follow-up to @mensi's answer, it can be important to keep track of different sets of features loaded from different data sources. You could do that by adding a property to each feature:
feature.setProperty('kind', 'region');
feature.setProperty('kind', 'lake');
However, it may be easier to create multiple data layers. A Google Map by default starts out with a single data layer, but you are not limited to that. You can do:
var datalayer = new google.maps.Data({ map: mymap });
(It's important to set a map
option, or your data layer will not show up.)
This way, it's easier to group features by layer, and turn entire layers on or off.
This worked for me:
map.data.forEach(function(feature) {
// filter...
map.data.remove(feature);
});
You are correct in that the Data Layer is a single layer. However, if you manually retrieve the GeoJSON and use the addGeoJson
function instead of loadGeoJson
you will get the added features returned. You can remove these later on.
So instead of
map.data.loadGeoJson('https://storage.googleapis.com/maps-devrel/google.json');
You can do something like this (this example uses jQuery to get the data and assumes there is a button with the ID removeBtn):
// Load the GeoJSON manually (works cross-origin since google sets the required HTTP headers)
$.getJSON('https://storage.googleapis.com/maps-devrel/google.json', function (data) {
var features = map.data.addGeoJson(data);
// Setup event handler to remove GeoJSON features
google.maps.event.addDomListener(document.getElementById('removeBtn'), 'click', function () {
for (var i = 0; i < features.length; i++)
map.data.remove(features[i]);
});
});
(See this JSbin for a working example you can play around with)
In more complex circumstances, you probably have to keep track of which datasource the user loaded and the features that got created because of that so you can delete them when requested.
While map.data
is designed as a placeholder for the common case of a single datasource, you can have multiple, and still use addGeoJSon
using something like:
// load data - do the same for data2, data3 or whatever
data1 = new google.maps.Data();
data1.loadGeoJson(url1);
// create some layer control logic for turning on data1
data1.setMap(map) // or restyle or whatever
// turn off data1 and turn on data2
data1.setMap(null) // hides it
data2.setMap(map) // displays data2