Bart van den Eijnden
|
7b31ec26ea
|
fix up build
|
2013-08-04 15:10:08 +02:00 |
|
ahocevar
|
5a3ac559be
|
Merge pull request #733 from ahocevar/fid
Store the feature's commonly used id. r=@fredj,@bartvde
|
2013-05-24 06:15:00 -07:00 |
|
ahocevar
|
8c0f1f979a
|
Store the feature's commonly used id
To not clobber the feature's attributes, this is a separate
member property.
|
2013-05-23 11:16:17 -05:00 |
|
Bart van den Eijnden
|
93b067b6bc
|
Write support for ol.parser.GeoJSON
Also add some convenience with static read and write methods based on the
singleton.
|
2013-05-23 15:57:11 +02:00 |
|
Tom Payne
|
4be8c991f7
|
Add missing Closure Library requires
|
2013-04-06 14:28:12 +02:00 |
|
ahocevar
|
389b8d14d7
|
Support GeoJSON as parsed object
With this change, we can programmatically create
GeoJSONFeatureCollection objects programmatically, without
reading a GeoJSON file.
|
2013-03-08 16:25:23 +01:00 |
|
Tim Schaub
|
8c8ddce290
|
GeoJSON parser implements StringFeatureParser
|
2013-03-04 20:31:01 +01:00 |
|
Tim Schaub
|
b247031fe2
|
Test reading with shared vertices
|
2013-03-03 15:51:24 +01:00 |
|
Tim Schaub
|
69b6fae744
|
Parser base class
GeoJSON is now a parser. The idea is that we'll want to pass parsers to sources or protocols and want a known type.
|
2013-03-03 11:50:51 +01:00 |
|
Tim Schaub
|
9cac8ec2f6
|
Moving GeoJSON into parser package
Need to discuss whether we want all to require constructing a new parser. I liked the simple `ol.io.geojson.read` function.
|
2013-02-20 00:09:38 -07:00 |
|