As per the issue I added, here's a solution that allows you to set "bounded: false" on a location if you don't want the location to be used in the getBounds() calculation.
show the whole world if no data points are available
don't cache metadata so that dynamically changed place data will get …
Merge remote branch 'upstream/master'
fixed documentation of default value for metadata_options
added the 'bounded' attribute to the data object so that a place can …
…be excluded from the bounds calculation