From a3e231fba804696843321c5cc497ad0940dffcc3 Mon Sep 17 00:00:00 2001 From: ahocevar Date: Tue, 9 Jul 2013 06:51:08 -0700 Subject: [PATCH] Ticket link --- Minimal-Vector-API.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Minimal-Vector-API.md b/Minimal-Vector-API.md index 28964c4..cfc982e 100644 --- a/Minimal-Vector-API.md +++ b/Minimal-Vector-API.md @@ -26,7 +26,7 @@ Initially, we can style data with a subset of CartoCSS or SLD, without exposing ## Edit Vector Data -Features can already be accessed with `ol.Map#getFeatures`. #850 adds event handling for added and removed features, so the renderer can keep the view up to date. The CHANGE event could also be used to keep track of feature modifications, but it imposes significant overhead to register a change listener on every single feature. So preferably, the feature modification workflow will be provided by controls that move features to a sketch layer for editing and register CHANGE listeners for these features only. After editing, the sketch features can be moved back to their original layer. This workflow can also be used for attribute modifications. +Features can already be accessed with `ol.Map#getFeatures`. [#850](http://github.com/openlayers/ol3/isues/850) adds event handling for added and removed features, so the renderer can keep the view up to date. The CHANGE event could also be used to keep track of feature modifications, but it imposes significant overhead to register a change listener on every single feature. So preferably, the feature modification workflow will be provided by controls that move features to a sketch layer for editing and register CHANGE listeners for these features only. After editing, the sketch features can be moved back to their original layer. This workflow can also be used for attribute modifications. ## Persist Edits