Re: [Geojson] [Technical Errata Reported] RFC7946 (5069)

James Winterbottom <a.james.winterbottom@gmail.com> Fri, 14 July 2017 17:57 UTC

Return-Path: <a.james.winterbottom@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 2EF8B126DD9 for <geojson@ietfa.amsl.com>; Fri, 14 Jul 2017 10:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_NONE=-0.0001, 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 R6czhRXg1UlW for <geojson@ietfa.amsl.com>; Fri, 14 Jul 2017 10:57:19 -0700 (PDT)
Received: from mail-pf0-x243.google.com (mail-pf0-x243.google.com [IPv6:2607:f8b0:400e:c00::243]) (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 CAC9B131756 for <geojson@ietf.org>; Fri, 14 Jul 2017 10:57:12 -0700 (PDT)
Received: by mail-pf0-x243.google.com with SMTP id e199so11725255pfh.0 for <geojson@ietf.org>; Fri, 14 Jul 2017 10:57:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=NXQKI7vyvKoKz5pqykBtnRPPhcuR/J/3C9JD7pHzVp4=; b=QExPjdcMhLM9aOiwonrMgQvARiJAfEPIUl3Rz69Jo3UGA6M16cJV2rfmFoJoDiz5nQ aqPFxg9CbxwE585eoVhEb5I3tQ+0NRnNeh9BRJHMTYhCEAdAI6L9TS+oBWGcEyi5FYTk MIPBoM5fGFjPiKnypxzceP6n7pjJiQPiGRuffGf1i8+0mV6QmMPsuGk9p/3rzYybKnDi Z0AN2j+eP0mydU0CZoqC1TMk+b7QT8xu12HW7xWnAJtLWfThALvC46VUrNdehPgn3iP5 uCjIotjbvUhVWhQFVN6hu2pW2EZasT1w/ttWn1OnL6bCbGk1q6NVCUTbujy4q1ugwLCN w31Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=NXQKI7vyvKoKz5pqykBtnRPPhcuR/J/3C9JD7pHzVp4=; b=X7Pc8wU5t0bm3qoM84Sj7k2PYbu3gxpAppn8JSbBuoFSA6JzIpRaWkbYRwnf0gyja/ E0F64fQsqCiE4SkELfm6fFQt7ZnFB2MyI/Y5ZPzMRfxUJOIwcYRYZN45Rw6YzNYtT5wk y0kb5FePZsBNki7rqsLNZp+tOO2QT0J3Oc0or+fbKDq58OXNjrYxEN8tmRI8NLTP6Sw8 YdaVLtGf3AS0l6Sx9HNKfqADhlCnhhMxJrnacy4QuZQzhKO1LsGCeijuP2vPotEPiBzo nGRyTu85VjK51+GxgswklBFqjauvdplTZpJ/pOpePuDIGyXGKlPKqNX2yDgbJ4AnUNlS fkZA==
X-Gm-Message-State: AIVw111E0fxhjCetyClycHWSveErcl7z1+W7KKpueDgWGaRCD4gVRNOR Ef2+4HUTCbxddg==
X-Received: by 10.84.224.15 with SMTP id r15mr16991722plj.78.1500055032278; Fri, 14 Jul 2017 10:57:12 -0700 (PDT)
Received: from [192.168.0.9] (n1-43-214-154.mas2.nsw.optusnet.com.au. [1.43.214.154]) by smtp.gmail.com with ESMTPSA id u194sm15164803pgb.24.2017.07.14.10.57.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Jul 2017 10:57:11 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: James Winterbottom <a.james.winterbottom@gmail.com>
X-Mailer: iPhone Mail (14F89)
In-Reply-To: <CABkgnnWZnCB0mkrxgeXE4+8KsjYTG-JcSLBDi0aNj=9=rcDxVA@mail.gmail.com>
Date: Sat, 15 Jul 2017 03:57:08 +1000
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, Tim Schaub <tim.schaub@gmail.com>, Howard Butler <howard@hobu.co>, Adam Roach <adam@nostrum.com>, Erik Wilde <erik.wilde@dret.net>, Ben Campbell <ben@nostrum.com>, Alexey Melnikov <aamelnikov@fastmail.fm>, Sean Gillies <sean.gillies@gmail.com>, Stefan Hagen <stefan@hagen.link>, geojson@ietf.org, Martin Daly <martin.daly@cadcorp.com>, carcher@drillinginfo.com, Allan Doyle <adoyle@intl-interfaces.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <781224D8-6E6C-4A2D-B020-9D30852DECCC@gmail.com>
References: <20170714154433.DD8A3B80157@rfc-editor.org> <CABkgnnWZnCB0mkrxgeXE4+8KsjYTG-JcSLBDi0aNj=9=rcDxVA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/geojson/EmsEDgJOOewfqSBXW6gEgM5o2QA>
X-Mailman-Approved-At: Fri, 14 Jul 2017 11:07:53 -0700
Subject: Re: [Geojson] [Technical Errata Reported] RFC7946 (5069)
X-BeenThere: geojson@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 14 Jul 2017 17:57:28 -0000

+1 for Martin's position

Sent from my iPhone

> On 15 Jul 2017, at 3:42 am, Martin Thomson <martin.thomson@gmail.com> wrote:
> 
> My understanding is that the polygon definition follows the accepted
> norms for point order. GML defines the shape this way.  Section 5.1 of
> RFC 5491: https://tools.ietf.org/html/rfc5491#section-5.1 also uses
> counter-clockwise point order: the upward normal points up!  See also
> Appendix B of RFC 7459 https://tools.ietf.org/html/rfc7459#appendix-B
> 
> My understanding of the right hand rule being curled fingers on the
> right hand follow the points and the thumb becomes the upward normal.
> 
> I think that we should reject this erratum, but can someone else
> double-check that I'm not off base?
> 
>> On 15 July 2017 at 01:44, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
>> The following errata report has been submitted for RFC7946,
>> "The GeoJSON Format".
>> 
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata/eid5069
>> 
>> --------------------------------------
>> Type: Technical
>> Reported by: Clark Archer <carcher@drillinginfo.com>
>> 
>> Section: 3.1.6
>> 
>> Original Text
>> -------------
>> 3.1.6.  Polygon
>> 
>>   To specify a constraint specific to Polygons, it is useful to
>>   introduce the concept of a linear ring:
>> 
>>   o  A linear ring is a closed LineString with four or more positions.
>> 
>>   o  The first and last positions are equivalent, and they MUST contain
>>      identical values; their representation SHOULD also be identical.
>> 
>>   o  A linear ring is the boundary of a surface or the boundary of a
>>      hole in a surface.
>> 
>>   o  A linear ring MUST follow the right-hand rule with respect to the
>>      area it bounds, i.e., exterior rings are counterclockwise, and
>>      holes are clockwise.
>> 
>>   Note: the [GJ2008] specification did not discuss linear ring winding
>>   order.  For backwards compatibility, parsers SHOULD NOT reject
>>   Polygons that do not follow the right-hand rule.
>> 
>>   Though a linear ring is not explicitly represented as a GeoJSON
>>   geometry type, it leads to a canonical formulation of the Polygon
>>   geometry type definition as follows:
>> 
>>   o  For type "Polygon", the "coordinates" member MUST be an array of
>>      linear ring coordinate arrays.
>> 
>>   o  For Polygons with more than one of these rings, the first MUST be
>>      the exterior ring, and any others MUST be interior rings.  The
>>      exterior ring bounds the surface, and the interior rings (if
>>      present) bound holes within the surface.
>> 
>> 
>> Corrected Text
>> --------------
>> 3.1.6.  Polygon
>> 
>>   To specify a constraint specific to Polygons, it is useful to
>>   introduce the concept of a linear ring:
>> 
>>   o  A linear ring is a closed LineString with four or more positions.
>> 
>>   o  The first and last positions are equivalent, and they MUST contain
>>      identical values; their representation SHOULD also be identical.
>> 
>>   o  A linear ring is the boundary of a surface or the boundary of a
>>      hole in a surface.
>> 
>>   o  A linear ring MUST follow the right-hand rule with respect to the
>>      area it bounds, i.e., exterior rings are clockwise, and holes are
>>      counterclockwise.
>> 
>>   Note: the [GJ2008] specification did not discuss linear ring winding
>>   order.  For backwards compatibility, parsers SHOULD NOT reject
>>   Polygons that do not follow the right-hand rule.
>> 
>>   Though a linear ring is not explicitly represented as a GeoJSON
>>   geometry type, it leads to a canonical formulation of the Polygon
>>   geometry type definition as follows:
>> 
>>   o  For type "Polygon", the "coordinates" member MUST be an array of
>>      linear ring coordinate arrays.
>> 
>>   o  For Polygons with more than one of these rings, the first MUST be
>>      the exterior ring, and any others MUST be interior rings.  The
>>      exterior ring bounds the surface, and the interior rings (if
>>      present) bound holes within the surface.
>> 
>> 
>> Notes
>> -----
>> This is only for the bullet point describing the right-hand rule for linear rings. It seems like the clockwise/counterclockwise descriptions are the opposite of the right-hand rule. Walking an exterior ring in a counterclockwise direction would have the exterior of the ring to the right of the observer.
>> 
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party
>> can log in to change the status and edit the report, if necessary.
>> 
>> --------------------------------------
>> RFC7946 (draft-ietf-geojson-04)
>> --------------------------------------
>> Title               : The GeoJSON Format
>> Publication Date    : August 2016
>> Author(s)           : H. Butler, M. Daly, A. Doyle, S. Gillies, S. Hagen, T. Schaub
>> Category            : PROPOSED STANDARD
>> Source              : Geographic JSON
>> Area                : Applications and Real-Time
>> Stream              : IETF
>> Verifying Party     : IESG
> 
> _______________________________________________
> GeoJSON mailing list
> GeoJSON@ietf.org
> https://www.ietf.org/mailman/listinfo/geojson