> 1. It might be better to organize the skipped features as hash rather than a collection.

This is what we're envisioning having:

```js
map.getSkippedFeatures().push(feature);
```

Then, when a render frame comes, we pass the uids to the features to skip to the renderer through the frame state.

```js

var frameState = {
   // ...
   skippedFeatureUids: goog.array.map(
       this.getSkippedFeatures().toArray(), function(feature) { return goog.getUid(feature); }),
   // ...
};
```

> 2. The map renderer is probably a better place to keep the hash than the map.

But we may want to expose the `getSkippedFeatures` function in the future, for users to be able to indicate the features that should be skipped in the layers.

> So I do not anticipate big changes once your branch is in.

Our impression is all of your code will need to be changed for @tonio's work, that is the reason we're not to inclined to merge this work.