[Geojson] "coordSys" member extension?

Lorand Kedves <lorand.kedves@gmail.com> Tue, 01 December 2020 07:10 UTC

Return-Path: <lorand.kedves@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 A23B23A0D03 for <geojson@ietfa.amsl.com>; Mon, 30 Nov 2020 23:10:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 A4Q4d9FThATC for <geojson@ietfa.amsl.com>; Mon, 30 Nov 2020 23:10:05 -0800 (PST)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 EE1793A0CFE for <geojson@ietf.org>; Mon, 30 Nov 2020 23:10:04 -0800 (PST)
Received: by mail-lf1-x12b.google.com with SMTP id s30so2065937lfc.4 for <geojson@ietf.org>; Mon, 30 Nov 2020 23:10:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=EUD2g7xZsPZx8ctuMI/VHMWy8FwON5LpvMvY08oD70E=; b=CkylZoUHCHxExUH912IvSX4lrpze/qQ/OOlwScid8jTvQYqJLa3OdarBDIsTHgExmk Hu2q242I87WDpQSIxoFkoeEHFmslKfBoQkYfkfQNv0A5dNazc7dDi+WulIt/7wFTMfRA wNEATVMcu5sLuhvFAXIyz0GHMK1ObwAvdebxITNq7tUJXPIi3VA8c7ZgjEwVftFVcSq2 b6vJwlqyhtm4yhGBCyYJtOHSWNONC2rxjPlQTbhfftFxFBzzGHZeqaY9uY7AGhsttldy ekQSEGgaB5J0VdoKZOwh9FURj83jxuIEJkyYEUejmv9olWqRLxvaAUWQDPfKRUU4mmnO E/Ng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=EUD2g7xZsPZx8ctuMI/VHMWy8FwON5LpvMvY08oD70E=; b=ue0/2B0Xsy0t2U/6ytNjwFMynPMuJt9WO448QBZFkK/KuZGLIeTvtSc+Hw89KMfD6b YUqzt57t1UWaN5zyoNl9GPNrOPXtc/hucNhgDuOHQLD9w0O8SH8ZkF/ij81PpLxZSdWJ BZNK98HrtS2OqvrkNZMU8LiaF3/gPSYiWnD8mumHiMSFt/0CS6B8H/Bi8kuN5K2QOQE0 a1oXnhWzVD3YPdxnNn05gjC87I3Wi/BHzvLADaiECvXogUkDxlMTALjpNi9nIWFk6yDR oYZcw1UFlLXHnB4TZ/18q652MSqK9Av2S/R+A7R82gMnBqsP58r41pOxLqL7ZHpeYJ+t 8/AA==
X-Gm-Message-State: AOAM531khNhr+gloyC831zJjKShR0MOgqUrBBZa3mGLXSci5SOucrED7 MOoaD1X+H8UfFc5gpWyST5F7rwMlwbeXEd7823m4z9g5vwC6Aw==
X-Google-Smtp-Source: ABdhPJzZhPL7WVXwaKivf2dHaviURqQSQddqGUNpcB1YQfqsdcZBrWxLZtyLMU16nvvG7K9WA30kUunLOcAVRcrRd/s=
X-Received: by 2002:ac2:443a:: with SMTP id w26mr621604lfl.460.1606806602427; Mon, 30 Nov 2020 23:10:02 -0800 (PST)
MIME-Version: 1.0
From: Lorand Kedves <lorand.kedves@gmail.com>
Date: Tue, 01 Dec 2020 08:09:50 +0100
Message-ID: <CAJrogBG1OygMxgPo343QSA=rU+A9iFLpLgafdhxEAjqnyxwf2w@mail.gmail.com>
To: geojson@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c2b2eb05b561d010"
Archived-At: <https://mailarchive.ietf.org/arch/msg/geojson/7DSrK_3KyCO0r9wLqGfKNl-f9Hk>
X-Mailman-Approved-At: Tue, 01 Dec 2020 13:52:44 -0800
Subject: [Geojson] "coordSys" member extension?
X-BeenThere: geojson@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 01 Dec 2020 07:13:27 -0000

Dear GeoJSON Board,


We created a management interface to a system with ~1GB of data, using
GeoJSON to server-client interaction and integration I/O was very
convenient and we could rely on sophisticated tools. (Thank you!)

However, the system used a different native coordinate system. Converting
all data to WGS84 and back all the time was not feasible (displaying and
saving data should be done in the system native coordinate system). We
decided to still use GeoJSON as a transfer format, although the actual
values were invalid. At the UI, the display component required this
conversion to get valid GeoJSON. I added a "coordSys" member to the GeoJSON
Object, set it to the native id on the server and used a stock tool to
in-place convert the received coordinates data on load.

I think this optional extension is useful: allows systems to use their
coordinate systems, they are responsible for the conversion but still can
produce valid GeoJSON. I am quite sure you had already considered and
rejected this idea. What was the problem with it?

Thank you
  Lorand Kedves