From a53217bb797362e1b9130b2cfee338d96f3acb40 Mon Sep 17 00:00:00 2001 From: tschaub Date: Sat, 23 Mar 2013 10:31:43 -0700 Subject: [PATCH] Updated Use cases (markdown) --- Use-cases.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Use-cases.md b/Use-cases.md index 7445f17..54505f8 100644 --- a/Use-cases.md +++ b/Use-cases.md @@ -27,8 +27,8 @@ var vector = new ol.layer.Vector({ }); var map = new ol.Map({ - layers: [raster, vector], target: 'map', + layers: [raster, vector], view: new ol.View2D({ projection: 'EPSG:1234', center: ol.projection.transform( @@ -38,4 +38,4 @@ var map = new ol.Map({ }); ``` -This alternative can be implemented if the layer knows the map projection. The vector layer would be responsible for calling `source.protocol.read({success: callback})` where the callback would call `source.parser.parseFeatures(data, {projection: projection})` (`data` is supplied to the callback and `projection` comes from the map's view). +This alternative can be implemented if the layer knows the map projection. The vector layer would be responsible for calling `source.protocol.read({success: callback})` where the callback would call `source.parser.parseFeatures(data, {projection: projection})` (`data` is supplied to the callback and `projection` comes from the map's view). The layer would maintain a cache of features in the map view's projection, and these would be provided on demand to layer's the renderer.