Re: [Geojson] Question regarding position definition in RFC 7946 vs. ISO 6709 / RFC 5870
Florian Wolff <Flori@nWolff.de> Mon, 04 May 2020 14:12 UTC
Return-Path: <Flori@nWolff.de>
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 6CE053A08F6 for <geojson@ietfa.amsl.com>; Mon, 4 May 2020 07:12:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=nwolff.de
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 DaHKF_VbwkWJ for <geojson@ietfa.amsl.com>; Mon, 4 May 2020 07:12:19 -0700 (PDT)
Received: from mail.flocom.net (h2778126.flocom.net [81.169.209.235]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C68663A091C for <geojson@ietf.org>; Mon, 4 May 2020 07:12:02 -0700 (PDT)
X-Virus-Scanned: Yes
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nwolff.de; s=mail; t=1588601519; bh=POZl4/5HqCeRfwpKCYsuygRLimW64/PjnT6KB81mL3s=; h=Subject:To:References:Cc:From:In-Reply-To; b=qUKwoM3z1MshxVL2QGqNWIJIouV2BWBn1vSLDlN4cI0Zbg6E7QHjULRK4FqXxwhoI 0M5ZU6x28Exg0CVY8mgyp0KquIm3VwLtyJ+k899pwry/XCQZflcMeOq8xDXSWIKAko sJyx38XrIAWpGZk1JGLx3nsS8UkCYB7jk9OD0w7uv6gLP+LYs5gtn6vIc/aeyXtVir YzBpotW2bc4ylRnbac+A/OcmXN7nIY/ofG02Y/2qayP9c7UfX8fwYDvML4aqVPZqju SX2PLlwqy0waVuV0r/FJoh8d8xPEFyKVB0TuWvfGyHHYxxOCHPEAzTFgi7Vy72NBd4 H8qLD5MD5t+bOMQHtJdWTojcXMp+KhHUYpSe9HSuCyZExqQOeXyOBX8r7pHfE7XhQv G5cFYZzmp95TZDPgS8pj1teru772+V6iNqGuKpirU8pwbPIvRzP1mX/65yUudf+tgi REWavi9vnsUXkzQLHyGklRl+eoOESE3zyKB8gqbbm6gIhpvnvCI4huXVKWPrClaEr8 7E7MUnhdIxxxoTC6n90XeczG/7/Fka3aboHGFqFCK5IoFtzmbALzN3mhLx+hRtW77l sXN1sbzvc+eXrNLaBFANcMv8lW/B5YZc5WoQ8jCeBc+phiUbhmBg7IOC2gQqqF3m64 GFrrTru1S/H9EnoDQe9mZHJc=
To: Martin Daly <Martin.Daly@cadcorp.com>
References: <8c171ca6-94cd-de3e-0891-5b96c2609aab@nWolff.de> <08ba31ce277f43dc8f6cb76e98733f92@SRV016VEX.cadcorp.net>
Cc: "geojson@ietf.org" <geojson@ietf.org>
From: Florian Wolff <Flori@nWolff.de>
Message-ID: <80b51fcc-b84a-a9d0-616d-15ee742dfbe6@nWolff.de>
Date: Mon, 04 May 2020 16:11:58 +0200
Mime-Version: 1.0
In-Reply-To: <08ba31ce277f43dc8f6cb76e98733f92@SRV016VEX.cadcorp.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/geojson/tv4PALmqMcwMxD0CjkD4t8aIK3s>
Subject: Re: [Geojson] Question regarding position definition in RFC 7946 vs. ISO 6709 / RFC 5870
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: Mon, 04 May 2020 14:12:22 -0000
Hi Martin, thank you very much for guessing and answering my question. This was exactly what I was looking for - the "good old philosophical" discussions if a point should be expressed as x,y or y,x (which in turn translates into y=lat/x=long). Florian. Am 01.05.2020 um 10:28 schrieb Martin Daly: > Hi Florian, > > Assuming that your question is “why does GeoJSON coordinate order > contradict ISO 6709 coordinate order?”, then the answer is: because it does. > > The decision was taken in full possession of the facts, not lightly, or > without regard to the consequences. There are **extensive** email > exchanges on lists.geojson.org, if you like that kind of thing. This > response, from Howard, is more or less definitive (albeit replying to > slightly different questions): > > http://lists.geojson.org/pipermail/geojson-geojson.org/2013-April/000707.html > > Martin > > *From:*GeoJSON [mailto:geojson-bounces@ietf.org] *On Behalf Of *Florian > Wolff > *Sent:* 30 April 2020 16:52 > *To:* geojson@ietf.org > *Subject:* [Geojson] Question regarding position definition in RFC 7946 > vs. ISO 6709 / RFC 5870 > > I stumbled across this definitions years after publication, however > please excuse the following question as GeoJSON specifies > > A position is an array of numbers. There MUST be two or more|| > > elements. The first two elements are longitude and latitude, or|| > > easting and northing, precisely in that order and using decimal|| > > numbers. > > while according to ISO 6709 Standard representation of geographic point > location by coordinate and RFC 5870 the order of coordinates is > > 1. First horizontal coordinate (y), such as latitude (negative number > south of equator and positive north of equator) > 2. Second horizontal coordinate (x), such as longitude (negative values > west of Prime Meridian and positive values east of Prime Meridian) > > With best regards, > > Florian. >
- [Geojson] Question regarding position definition … Florian Wolff
- Re: [Geojson] Question regarding position definit… Martin Daly
- Re: [Geojson] Question regarding position definit… Florian Wolff