<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<br>
<div>
<div>On Jun 13, 2013, at 7:04 PM, Sean Gillies <<a href="mailto:sean.gillies@gmail.com">sean.gillies@gmail.com</a>></div>
<div> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>Stefan, all:<br>
<br>
</div>
I think we should continue with your proposal, but I hear that other authors are having second thoughts about removing CRS after all. Allan? Howard?<br>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
Second thoughts:</div>
<div><br>
</div>
<div>Item 1. People are using CRS. We know of one, Michael Geary. Based on the tweets below, it looks like there's another in the works, Ben Balter. We have to assume there are others.</div>
<div><br>
</div>
<div>Item 2. Assume we remove 'crs' from the spec. Then what happens when someone else makes a GeoJSON file with a 'crs' element that works differently from the one we had. Now we have the people in item one with different use of 'crs' than people in item two.
Not only is that a Bad Thing, it seems very unfair to those people in item one.</div>
<div><br>
</div>
<div>Let's do this. Keep it in. Keep the documentation pretty much as is. Add a note that says we know this is not optimal, and that interoperability is better served if it's not used, but that if people are going to use 'crs' they have to use what's here as
a starting point. If they want to add a different element, e.g. 'srs' or 'allans-excellent-reference-element', they can do that. But they do that will full knowledge that it's not part of the spec.</div>
<div><br>
</div>
<div>Philosophical version: Essentially, there are two namespaces for elements in GeoJSON. The standard namespace is the set of names we define in the spec. The non-standard namespace is everything else. If someone uses something in the standard namespace,
they have to use it as described. If they use something in the non-standard namespace, they can do whatever they want.</div>
<div><br>
</div>
<div>Further second thoughts: We put together GeoJSON 1.0 and it's been out for a long time. I don't think we can cross the line of making a subsequent version that decreases interoperability, and I think that's what removing 'crs' or changing its definition
would do.</div>
<div><br>
</div>
<div>Final thoughts: I admit I was one of the people originally advocating dropping crs. I've changed my mind. We screwed it up, but it would be worse to compound the error.</div>
<div><br>
</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>Allan</div>
<div><br>
<blockquote type="cite">
<div dir="ltr">
<div>
<div><br>
GitHub's new maps for .geojson files is revealing a lot about how people perceive the format. Here, Ben Balter (of GitHub) says support for other CRS is being considered:<br>
<br>
<a href="https://twitter.com/BenBalter/status/345280641715298305">https://twitter.com/BenBalter/status/345280641715298305</a><br>
<br>
</div>
I assume he doesn't mean different map tiles, but reprojection of Illinois State Plane X to Web Mercator. They'll need CRS in the file to accomplish this across all repositories. I'd rather the City of Chicago and everyone else did their GeoJSON in CRS84, but
it seems we'll have to get GitHub on board to do so.<br>
<br>
</div>
And here's someone who didn't realize that GeoJSON covered CRS at all:<br>
<div>
<div><br>
<a href="https://twitter.com/iandees/status/345281028132315137">https://twitter.com/iandees/status/345281028132315137</a><br>
<br>
</div>
<div>IMO, this is because we didn't do it well and good examples never appeared.<br>
<br>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, May 21, 2013 at 11:23 AM, Stefan Drees <span dir="ltr">
<<a href="mailto:stefan@drees.name" target="_blank">stefan@drees.name</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hi Tim,<br>
<br>
yes I know, that there are partial clean-up attempts with focus on a specific topic (like your patch #6 removing crsURN) but not transporting the document into a consistent state, which is ok, but I think as time goes by not the best we can achieve. As I had
to base my clean-up patch on some revision and repo, I picked the latest you merged, to be on the safe side.
<br>
<br>
In the light of the latest somehow diverging discussions, I thought a minimal consensus edition might help remain patient and have a clear view on the remanining tasks before entering the public comment phase, that will start when submitting the first revision
to IETF I-D queue. The submission will just be the beginning :-)<br>
<br>
So applying the patch #10 as wrap-up gives us all the advantage of a clean start for the finish and if many of the authors meet in person during this north american conference in Minneapolis, MN, USA all the better, to start placing the final golden minimal
CRS statements into the cleaned-up consistent document as close as possible to a broad consensus (in my understanding of the exchanged messages).<br>
<br>
My proposal is thus: <br>
a) Apply #10, <br>
b) some discuss the final statements about the relation of Coordinate Reference Systems and GeoJSON during the conference,
<br>
c) short discussion on concrete pull request based on the outcome of b) then <br>
d) merge and<br>
...) <br>
r) ready for submission we are :-).<br>
<br>
Good idea? Not so good idea? Please share your thoughts.<span class="HOEnZb"><font color="#888888"><br>
<br>
Stefan.</font></span>
<div>
<div class="h5"><br>
<br>
On 21.05.13 18:57, Tim Schaub wrote:<br>
</div>
</div>
</div>
<div>
<div class="h5">
<blockquote type="cite">
<div dir="ltr">Note also that I have a pull request outstanding to remove crsURN:
<div><a href="https://github.com/GeoJSONWG/draft-geojson/pull/6" target="_blank">https://github.com/GeoJSONWG/draft-geojson/pull/6</a></div>
<div><br>
</div>
<div>I think we'd all agree that there needs to be some discussion of CRS in the spec. This is missing from your pull request. Minor work to add it in, but it needs to be there.</div>
<div><br>
</div>
<div>I imagine a number of us will be at the FOSS4G-NA conference through the end of the week. So while discussion on this list might stagnate, we could have some in-person discussion about this.</div>
<div><br>
</div>
<div>Tim</div>
<div><br>
<div><br>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, May 20, 2013 at 7:31 AM, Stefan Drees <span dir="ltr">
<<a href="mailto:stefan@drees.name" target="_blank">stefan@drees.name</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dear all,<br>
<br>
I snet a pull request, where I:<br>
<br>
* simply removed the CRS (and any crsURI stuff),<br>
* also removed my intermediate notes,<br>
* and removed the now unused references to HTTP, TLS, URx RFCs,<br>
* rephrased the Polygon section for readability,<br>
* edited some lines to remain inside line length limit,<br>
* updated the date to May 2013,<br>
* enhanced the security considerations section (using the JSON Patch<br>
RFC as role model) to somehow delegate security back to JSON where it<br>
belongs, as we do not add anything security relevant on top<br>
* and sync'ed the section number for the bounding box references inside<br>
our document.<br>
<br>
The pull request #10 is at<br>
<br>
<a href="https://github.com/GeoJSONWG/draft-geojson/pull/10" target="_blank">https://github.com/GeoJSONWG/draft-geojson/pull/10</a><br>
<br>
If one likes to se the outcome of merging it, maybe<br>
<br>
<a href="http://sdrees.github.io/draft-geojson/draft.html" target="_blank">http://sdrees.github.io/draft-geojson/draft.html</a><br>
<br>
is a good place or<br>
<br>
<a href="http://sdrees.github.io/draft-geojson/draft.txt" target="_blank">http://sdrees.github.io/draft-geojson/draft.txt</a><br>
<br>
This patch should merge the essence of our latests planned changes for the to be submitted draft (as far as I understood the ideas of most on this list).<br>
<br>
Am I right? Not so right? What do you think?<br>
<br>
PS: If you read an archived version of this mail, some links stated in above text may result in HTTP 404 Not found as these mostly point to intermediate working material.<br>
<br>
All the best,<br>
Stefan Drees.<br>
_______________________________________________<br>
GeoJSON mailing list<br>
<a href="mailto:GeoJSON@lists.geojson.org" target="_blank">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>
</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>
</blockquote>
<br>
</div>
</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">
<br>
-- <br>
Sean Gillies </div>
_______________________________________________<br>
GeoJSON mailing list<br>
<a href="mailto:GeoJSON@lists.geojson.org">GeoJSON@lists.geojson.org</a><br>
http://lists.geojson.org/listinfo.cgi/geojson-geojson.org<br>
</blockquote>
</div>
<br>
</body>
</html>