[Geojson] PR #199: CRS

Martin Thomson <martin.thomson@gmail.com> Thu, 21 April 2016 03:23 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: geojson@ietfa.amsl.com
Delivered-To: geojson@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1128612D90D for <geojson@ietfa.amsl.com>; Wed, 20 Apr 2016 20:23:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.194
X-Spam-Level:
X-Spam-Status: No, score=-1.194 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, SUBJ_ALL_CAPS=1.506] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xBdlnFpCPp0s for <geojson@ietfa.amsl.com>; Wed, 20 Apr 2016 20:23:51 -0700 (PDT)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F2B812DEF8 for <geojson@ietf.org>; Wed, 20 Apr 2016 20:23:51 -0700 (PDT)
Received: by mail-ig0-x231.google.com with SMTP id g8so69393458igr.0 for <geojson@ietf.org>; Wed, 20 Apr 2016 20:23:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=Vc1HgMd23hlxINGmJaLqzAqCtwZrqDmrjX7DWFO5P50=; b=HN7duB/3sSFPS8uDZBbJ5nq6dvPuvcBePlNt6Q4+A7kOdvTSxwQWGT/YqnI0J50VZN mKcJsGwDii9pHp2/0xDd9fEjgJ6aBt0s9sPNCyx5wkeVvDyP9Y6qNyDaUo6lv6oH/9bU c6EyScI7zqhiuoMEscHp5dKOTTP8hO95799+jjFYxSbnDVHAYPp+avOJ0giGF7DDS59d 1tdXhU/nYBKtvYDNyg4eOxM4BtdN85B9pH4QnlowyRRI9xWFdMflV5NvCS++t3SXpMNX L9Cvi6qq52bwRgssHkKvg+NLf2e0QIFS30+x6gxRDpqXR5XUKC4XlMLoH0Y4QTlGAYC4 LEtw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=Vc1HgMd23hlxINGmJaLqzAqCtwZrqDmrjX7DWFO5P50=; b=Zonic7WxMpzJFwsL3UDiPgQ2rZaDIw0SzV1Vm3iNXkrrIG6QJMzmRLPYbWCWdphkIr HZuoSzpkdQAP/X50bHsGGlIQ6CJN5wrrVZPcpyJ2x41M/nxr9dwwe6wF9O2lNczYw9PA PuqpA6qiQwbQbnYZ9XRDlRJk+dK8obtlUV7OV1RUxcnHPnO4bztj+fTLHKG28JQKsTq4 PxYfx1Wgcxgz6wM5rMCGB7rdkOvqzFZ6JMEXTc80vJwwRgiRc5fvA452WbO1tZnZ858o n3DVEsscXOrNOYgbL0ZubWDBNyAPxLxyhlf2psCIHCue+0jfQSaWAbd/m6tolfb7x4Hz PrXg==
X-Gm-Message-State: AOPr4FXvvQPGHXR1EU9e9bzdxT0xSVkeK0vqxv/pNCdxSkY5Cz2WUccMpirhxvESRHwAbPqX6CQSkL+yaw69ZA==
MIME-Version: 1.0
X-Received: by 10.50.59.211 with SMTP id b19mr813827igr.58.1461209030388; Wed, 20 Apr 2016 20:23:50 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Wed, 20 Apr 2016 20:23:50 -0700 (PDT)
Date: Thu, 21 Apr 2016 13:23:50 +1000
Message-ID: <CABkgnnWUzLhitZkqahnk-EMwcp5LXS6+=-oUOkd6nzOTjRJEpA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: geojson@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/geojson/LgYV2TbKeUqTWK9e51_jE4GhvwA>
Subject: [Geojson] PR #199: CRS
X-BeenThere: geojson@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF GeoJSON WG <geojson.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/geojson>, <mailto:geojson-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/geojson/>
List-Post: <mailto:geojson@ietf.org>
List-Help: <mailto:geojson-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geojson>, <mailto:geojson-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Apr 2016 03:23:52 -0000

Surprising no one, this issue turns out to be tricky.

If I understand the discussion this is the intended statements we want to make:

1. Using a different CRS is not advised.
2. Using a different CRS with lat, long ordering of coordinates is prohibited.
3. Anyone using a different CRS is responsible for ensuring that their
GeoJSON-like data is properly understood by all potential recipients.
They can do that by limiting the set of recipients.

The second point is one I'd like to get some clarity on.  It seems
that there is a fuzzy line here and I think we could be crisper about
where that line is.

I get that this particular error has caused interoperability problems,
but what about other sorts of confusion.  Is the problem specific to
an inversion of lat/lng?

Specifically, would the same sort of problem occur for a ECEF
Cartesian CRS?  Would the same problem occur for a CRS with a
dramatically different prime meridian (such as one that passes through
Mundubbera, or Vienna)?

If the former is a problem, but not the latter, then point 2 might
become "Using a CRS that uses a form other than long, lat or long,
lat, alt is prohibited."

Whereas if both issues are a concern, then it looks like we're
creating a rule that is based on some sort of subjective similarity to
WGS84.  Isn't it better to prohibit the use of alternative coordinate
reference systems entirely?  If we accept that, then people doing
their own thing, like Sean's UTM-based pipeline, are simply using
GeoJSON-like structures.