<div dir="ltr">Hey Frank,<div><br></div><div style>Yes, adding a "schema" member to a FeatureCollection would still be valid, and clients should ignore it if they don't know how to deal with it.</div><div style>
<br></div><div style>Regarding bbox, you can add a bbox to a FeatureCollection if it is an array of length 2*dim (see <a href="http://geojson.org/geojson-spec.html#bounding-boxes">http://geojson.org/geojson-spec.html#bounding-boxes</a>).</div>
<div style><br></div><div style>It would be great to have more of your thoughts on the "crs" member discussion.</div><div style><br></div><div style>Really cool to see the Maps Engine usage.</div><div style><br>
</div><div style>Tim</div><div style><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 16, 2013 at 12:38 PM, Frank Warmerdam <span dir="ltr"><<a href="mailto:warmerdam@pobox.com" target="_blank">warmerdam@pobox.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Folks,<div><br></div><div>I think I already know the answer to this, but I'm checking in just in case. </div>
<div><br></div><div>In reading the GeoJSON doc it says:</div><div><br></div><div>"<br clear="all">
<div><div>2. GeoJSON Objects</div><div>GeoJSON always consists of a single object. This object (referred to as the GeoJSON object below) represents a geometry, feature, or collection of features.</div><div><br></div><div>
The GeoJSON object may have any number of members (name/value pairs).</div></div><div>..."</div><div><br></div><div>Can I construe this to mean that it is acceptable to extra fields not in the spec in GeoJSON objects under the assumption that baseline clients will just ignore them?</div>
<div><br></div><div>I'm thinking of adding schema, bounding box and other stuff info feature collections and I want to know if it is still legitimate to define it as type: FeatureCollection.</div><div>
<br></div><div>BTW, in case it hadn't been noted before the newly published Google Maps Engine API uses GeoJSON as the feature exchange format. </div><div><br></div><div> <a href="https://developers.google.com/maps-engine/documentation" target="_blank">https://developers.google.com/maps-engine/documentation</a><br>
</div><div><br></div><div>PS. as you might guess I wish the CRS was preserved but I obviously lean towards paleolithic complexity, so I'm not objecting to a slim and trim specification.</div><div><br>
</div><div>Best regards,</div><span class="HOEnZb"><font color="#888888">-- <br>---------------------------------------+--------------------------------------<br>I set the clouds in motion - turn up | Frank Warmerdam, <a href="mailto:warmerdam@pobox.com" target="_blank">warmerdam@pobox.com</a><br>
light and sound - activate the windows | <a href="http://pobox.com/~warmerdam" target="_blank">http://pobox.com/~warmerdam</a><br>and watch the world go round - Rush | Geospatial Software Developer<br>
</font></span></div></div>
<br>_______________________________________________<br>
GeoJSON mailing list<br>
<a href="mailto:GeoJSON@lists.geojson.org">GeoJSON@lists.geojson.org</a><br>
<a href="http://lists.geojson.org/listinfo.cgi/geojson-geojson.org" target="_blank">http://lists.geojson.org/listinfo.cgi/geojson-geojson.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Tim Schaub<br>OpenGeo <a href="http://opengeo.org/" target="_blank">http://opengeo.org/</a><br>Expert service straight from the developers.<br>
</div>