
From Chris.Goodman@objectconsulting.com.au  Tue May 23 00:19:15 2017
Return-Path: <Chris.Goodman@objectconsulting.com.au>
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 B52F41294CD for <geojson@ietfa.amsl.com>; Tue, 23 May 2017 00:19:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Level: 
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=objectconsultingau.onmicrosoft.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 kj40ktZFi0L8 for <geojson@ietfa.amsl.com>; Tue, 23 May 2017 00:19:14 -0700 (PDT)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-hk2apc01on0137.outbound.protection.outlook.com [104.47.124.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 451C6127601 for <geojson@ietf.org>; Tue, 23 May 2017 00:19:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=objectconsultingau.onmicrosoft.com; s=selector1-objectconsulting-com-au; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=c40yKTmWg3wXrRZd7EoK8HNUGu5kbkwWelLEQg9pd24=; b=Xdx+8Ud5RiZK0yPjvLRoIcoujgwwWJhkihGfJrzpp49JsuQjaMmCejy7MNafmNplZHnmCx5ty7zhN128ce5CX1IbalCqzom2JH/+itfE2EHJ2/gBgo147OwZpO+d0x839juJK+uB3murcppuM3CDBHyPAM+mlERucKywtIR0mis=
Received: from PS1PR06MB1241.apcprd06.prod.outlook.com (10.169.63.153) by PS1PR06MB1242.apcprd06.prod.outlook.com (10.169.63.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1101.14; Tue, 23 May 2017 07:19:06 +0000
Received: from PS1PR06MB1241.apcprd06.prod.outlook.com ([fe80::7c39:f800:9a58:fef1]) by PS1PR06MB1241.apcprd06.prod.outlook.com ([fe80::7c39:f800:9a58:fef1%14]) with mapi id 15.01.1101.019; Tue, 23 May 2017 07:19:06 +0000
From: Chris Goodman <Chris.Goodman@objectconsulting.com.au>
To: "geojson@ietf.org" <geojson@ietf.org>
Thread-Topic: Question regarding RFC 7946: Interior and Exterior Linear Rings
Thread-Index: AdLTlNsJfTfwJuR/TfadPHgLQ5NxCQ==
Date: Tue, 23 May 2017 07:19:06 +0000
Message-ID: <PS1PR06MB1241E7092910654915B99732AAF90@PS1PR06MB1241.apcprd06.prod.outlook.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Chris.Goodman@objectconsulting.com.au; 
x-originating-ip: [61.69.102.70]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; PS1PR06MB1242; 7:u0xxWmkC8ASxvwpeRbjw8Q9aQbRF6IWdcNuegEQWiYJv2WmQNeTXxEyMae/zVcY1l+2yTyE+Yrj87DygvNOKMqvP8EuQJEmdtMTTXSfszXgoNVfEvqc4+J68FbzTkCjGkuQeB+IAMyD9ZKvu+XDngKP5A5c9f1l0gA4c9GAHOZkArTu6IQAt50ycUvvPFWc8MhZYCz2tGTW4oHxaCOwqML1Knxs1TPTaFLKaDLIU5p6D5+rZ/JvWtV4cMt1QurETaWMYFPUwjcgKY5kLe/u8Ij0MGC4WrzgUaMvZRMfSOovQEQW1DLYRQR3cO4tCmSFuOWYyYxK9isijnsYf75o4wQ==
x-ms-traffictypediagnostic: PS1PR06MB1242:
x-ms-office365-filtering-correlation-id: f3fff4bc-8ae0-4401-ce44-08d4a1abffcb
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:PS1PR06MB1242; 
x-microsoft-antispam-prvs: <PS1PR06MB1242B207D19D7B560E1C2229AAF90@PS1PR06MB1242.apcprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(46150409022019)(21748063052155)(17755550239193); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(6041248)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123562025)(20161123558100)(20161123555025)(6072148); SRVR:PS1PR06MB1242; BCL:0; PCL:0; RULEID:; SRVR:PS1PR06MB1242; 
x-forefront-prvs: 0316567485
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39410400002)(39400400002)(39450400003)(39830400002)(252514010)(38730400002)(110136004)(3280700002)(86362001)(53936002)(2900100001)(8936002)(2906002)(7736002)(74316002)(6506006)(5640700003)(33656002)(6436002)(6306002)(72206003)(54896002)(3660700001)(55016002)(99286003)(9686003)(66066001)(236005)(2501003)(5630700001)(2351001)(478600001)(790700001)(6116002)(3846002)(102836003)(5250100002)(25786009)(74482002)(97736004)(8676002)(81166006)(1730700003)(189998001)(50986999)(42882006)(54356999)(5660300001)(6916009)(7696004); DIR:OUT; SFP:1102; SCL:1; SRVR:PS1PR06MB1242; H:PS1PR06MB1241.apcprd06.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
received-spf: None (protection.outlook.com: objectconsulting.com.au does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_PS1PR06MB1241E7092910654915B99732AAF90PS1PR06MB1241apcp_"
MIME-Version: 1.0
X-OriginatorOrg: objectconsulting.com.au
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2017 07:19:06.4605 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 627874b3-5313-4155-9129-9f7f680869ac
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PS1PR06MB1242
Archived-At: <https://mailarchive.ietf.org/arch/msg/geojson/1JEWEhDbzWszDVsIXbOY5FPdP28>
X-Mailman-Approved-At: Tue, 23 May 2017 01:18:36 -0700
Subject: [Geojson] Question regarding RFC 7946: Interior and Exterior Linear Rings
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: Tue, 23 May 2017 07:20:15 -0000

--_000_PS1PR06MB1241E7092910654915B99732AAF90PS1PR06MB1241apcp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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.


Q1. If an interior linear ring (hole) is not completely inside the exterior=
 ring (border) of a polygon, is it an illegal polygon?

GeoJson.io allows such an interior ring to be imported. Perhaps it is a bug=
.

Q2. If the interior ring is not clockwise, then what is the expected behavi=
our of the polygon?

Q3. Should 'interior linear ring' and 'exterior linear ring' be formally de=
fined in the RFC?

Q4. If two interior linear rings overlap, then is the result the union of t=
he two holes?


Regards, Chris
Chris Goodman
Supervising Consultant
M:  +61 419 482 620
Office:  +61 3 8615 4500
Web: www.objectconsulting.com.au
Email: chris.goodman@objectconsulting.com.au<mailto:chris.goodman@objectcon=
sulting.com.au>


--_000_PS1PR06MB1241E7092910654915B99732AAF90PS1PR06MB1241apcp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";
	mso-fareast-language:EN-AU;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-AU" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black;mso-fareast-language:EN-AU">Polygons with more =
than one of these rings, the first MUST be<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black;mso-fareast-language:EN-AU">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; the exterior ring, and any others MUST be interior rings.&nbsp;=
 The<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black;mso-fareast-language:EN-AU">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; exterior ring bounds the surface, and the interior rings (if<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black;mso-fareast-language:EN-AU">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; present) bound holes within the surface.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Q1. If an interior linear ring (hole) is not complet=
ely inside the exterior ring (border) of a polygon, is it an illegal polygo=
n?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">GeoJson.io allows such an interior ring to be import=
ed. Perhaps it is a bug.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Q2. If the interior ring is not clockwise, then what=
 is the expected behaviour of the polygon?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Q3. Should &#8216;interior linear ring&#8217; and &#=
8216;exterior linear ring&#8217; be formally defined in the RFC?<o:p></o:p>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Q4. If two interior linear rings overlap, then is th=
e result the union of the two holes?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards, Chris<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt;text-autospace:none"><b>=
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Arial&quot;=
,sans-serif;color:#3D9440;mso-fareast-language:EN-AU">Chris Goodman</span><=
/b><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Arial&qu=
ot;,sans-serif;color:#3D9440;mso-fareast-language:EN-AU"><o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt;text-autospace:none"><sp=
an lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Arial&quot;,sa=
ns-serif;color:#404040;mso-fareast-language:EN-AU">Supervising Consultant<b=
r>
M:&nbsp; &#43;61 419 482 620<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt;text-autospace:none"><sp=
an lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Arial&quot;,sa=
ns-serif;color:#404040;mso-fareast-language:EN-AU">Office:&nbsp; &#43;61 3 =
8615 4500<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:12.0pt;text-autospace:none"><sp=
an lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Arial&quot;,sa=
ns-serif;color:#404040;mso-fareast-language:EN-AU">Web:</span><span lang=3D=
"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Arial&quot;,sans-serif;m=
so-fareast-language:EN-AU">
<u><span style=3D"color:#3D9440"><a href=3D"www.objectconsulting.com.au"><s=
pan style=3D"color:#3D9440">www.objectconsulting.com.au</span></a></span></=
u><span style=3D"color:#058734"><o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-f=
amily:&quot;Arial&quot;,sans-serif;color:#404040;mso-fareast-language:EN-AU=
">Email:</span><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&q=
uot;Arial&quot;,sans-serif;mso-fareast-language:EN-AU">
<span style=3D"color:#3D9440"><a href=3D"mailto:chris.goodman@objectconsult=
ing.com.au"><span style=3D"color:blue">chris.goodman@objectconsulting.com.a=
u</span></a></span></span><span style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,serif;mso-fareast-language:EN-AU"><o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_PS1PR06MB1241E7092910654915B99732AAF90PS1PR06MB1241apcp_--


From nobody Tue May 23 03:16:26 2017
Return-Path: <sean.gillies@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 9CFB2126CE8 for <geojson@ietfa.amsl.com>; Tue, 23 May 2017 03:16:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 o4NxruLayrtF for <geojson@ietfa.amsl.com>; Tue, 23 May 2017 03:16:24 -0700 (PDT)
Received: from mail-yb0-x22c.google.com (mail-yb0-x22c.google.com [IPv6:2607:f8b0:4002:c09::22c]) (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 CEB57124C27 for <geojson@ietf.org>; Tue, 23 May 2017 03:16:23 -0700 (PDT)
Received: by mail-yb0-x22c.google.com with SMTP id 130so18542030ybl.3 for <geojson@ietf.org>; Tue, 23 May 2017 03:16:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=wYHp8R/XdbQON/lby2VATb8TstYrAGEl1MLpMotWnpk=; b=m9dLyzwLTxWGEqqnWLmJY5OOzA/0ym+/5jLKAtlx9xSyI7OJ6ypu9qnR6mpYUg+ZTv XKnYgpDgr4g2PsKNFyjigq8N+HyLQb+tWllHhaiio3MM68Bg4JBewuyRIMYZSVieOujI If/KrF5/hX184yWCUBlVTB2nOXuTdCMTtLNKxEvKEV9Xo2sbEOczj7T9KGcmO4bO46hH 9IOkqBDGeiU1EBKbWv8WqLLZwz3fPNzVtrkWchrgCAP8DZuXnKBGspuHA9vf+OReV6Gn 6E66AmHEyojBQzuq7aPSOI5DP3YBJGErGwwBD7Dr2AA+IDPBqBkWkuNqyv/htNdczc4C 6jIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=wYHp8R/XdbQON/lby2VATb8TstYrAGEl1MLpMotWnpk=; b=RJqBHN2r5xrWyz8PlyYsrZ7DKmyKlcC+suMrYDNd2eV+xTA64luyrMTnnNPRu1rlda xcW+8F6usiHdKbY9GWjz5IOhXbfRCsLAXIICN01Um+pH+hcaYl5EcdD2Cw7U0MzT/akg yinCjzxIbBoN+PttjNA2BhMU/YiOQl02KPRX+BRyZPDugCknKmGNoTzXXcM2z91k2lr9 JDacvqJI6kQ/Xbw9bfP9Jt5SqQHcvkf5UDc5soeP8blK8hTwj+IuxhDRlnlvup8Cw/sr aFV0cgZGLaLQVvQeub3RCeZ6qsnG+o0dgi9Xgs2fPolaZxzHSBnRawpoklrhShzB0a3g MUEA==
X-Gm-Message-State: AODbwcDqzy8/NIBY6Ny1DPqf8Zg+7tI2iyfFzcYIE/u34FkaO8zM0J5a Dsv2sFAf9wzs9SwZtguQlkI4MRdlwR68T3U=
X-Received: by 10.37.30.135 with SMTP id e129mr11599290ybe.71.1495534583026; Tue, 23 May 2017 03:16:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.138.2 with HTTP; Tue, 23 May 2017 03:16:22 -0700 (PDT)
In-Reply-To: <PS1PR06MB1241E7092910654915B99732AAF90@PS1PR06MB1241.apcprd06.prod.outlook.com>
References: <PS1PR06MB1241E7092910654915B99732AAF90@PS1PR06MB1241.apcprd06.prod.outlook.com>
From: Sean Gillies <sean.gillies@gmail.com>
Date: Tue, 23 May 2017 12:16:22 +0200
Message-ID: <CAOodmJp6g_HWBaz53ZkWnA8QLPg1eFSbknV6S7=mDqo79YsZbQ@mail.gmail.com>
To: Chris Goodman <Chris.Goodman@objectconsulting.com.au>
Cc: "geojson@ietf.org" <geojson@ietf.org>
Content-Type: multipart/alternative; boundary="001a1143f2f29225b305502e470c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/geojson/oO_bQbhJ048UQG4KumHjr7vFAck>
Subject: Re: [Geojson] Question regarding RFC 7946: Interior and Exterior Linear Rings
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: Tue, 23 May 2017 10:16:26 -0000

--001a1143f2f29225b305502e470c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Chris,

On Tue, May 23, 2017 at 9:19 AM, Chris Goodman <
Chris.Goodman@objectconsulting.com.au> wrote:

> 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.
>
>
>
>
>
> Q1. If an interior linear ring (hole) is not completely inside the
> exterior ring (border) of a polygon, is it an illegal polygon?
>

>
> GeoJson.io allows such an interior ring to be imported. Perhaps it is a
> bug.
>

It would be invalid from an OGC simple features perspective but is not
invalid GeoJSON.


>
>
> Q2. If the interior ring is not clockwise, then what is the expected
> behaviour of the polygon?
>

The same.


>
>
> Q3. Should =E2=80=98interior linear ring=E2=80=99 and =E2=80=98exterior l=
inear ring=E2=80=99 be formally
> defined in the RFC?
>

The WG didn't find this necessary. Are you saying it would improve the
spec? How so?


>
>
> Q4. If two interior linear rings overlap, then is the result the union of
> the two holes?
>

Geometric operations are outside the scope of the GeoJSON. The format only
describes a serialization for polygons. Exterior ring comes first, interior
rings follow.

>From a OGC simple features perspective a polygon with overlapping holes is
invalid, but I've found that GIS software often has fault-tolerant modes
that can deal with these kinds of invalid shapes. PostGIS's buffer(0.0),
for example, which I expect would indeed replace the overlapping holes with
a single hole that is their union, and not create any "anti-holes" or new
positive areas.

--=20
Sean Gillies

--001a1143f2f29225b305502e470c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Chris,<br><div><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">On Tue, May 23, 2017 at 9:19 AM, Chris Goodman <span dir=
=3D"ltr">&lt;<a href=3D"mailto:Chris.Goodman@objectconsulting.com.au" targe=
t=3D"_blank">Chris.Goodman@objectconsulting.com.au</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-AU">
<div class=3D"gmail-m_-1626441234470666864WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;;color:black">Polygons with more than one of these rings, the =
first MUST be<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;;color:black">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the exterior ring=
, and any others MUST be interior rings.=C2=A0 The<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;;color:black">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 exterior ring bou=
nds the surface, and the interior rings (if<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;;color:black">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 present) bound ho=
les within the surface.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Q1. If an interior linear ring (hole) is not complet=
ely inside the exterior ring (border) of a polygon, is it an illegal polygo=
n? <br></p></div></div></blockquote><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div lang=3D"EN-AU"><div class=3D"gmail-m_-1626441234470666864Wo=
rdSection1"><p class=3D"MsoNormal"><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">GeoJson.io allows such an interior ring to be import=
ed. Perhaps it is a bug.</p></div></div></blockquote><div><br>It would be i=
nvalid from an OGC simple features perspective but is not invalid GeoJSON.<=
br>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang=
=3D"EN-AU"><div class=3D"gmail-m_-1626441234470666864WordSection1">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Q2. If the interior ring is not clockwise, then what=
 is the expected behaviour of the polygon?</p></div></div></blockquote><div=
><br></div><div>The same.<br></div><div>=C2=A0</div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div lang=3D"EN-AU"><div class=3D"gmail-m_-16264=
41234470666864WordSection1"><p class=3D"MsoNormal"><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Q3. Should =E2=80=98interior linear ring=E2=80=99 an=
d =E2=80=98exterior linear ring=E2=80=99 be formally defined in the RFC?</p=
></div></div></blockquote><div><br></div><div>The WG didn&#39;t find this n=
ecessary. Are you saying it would improve the spec? How so?<br></div><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang=3D"=
EN-AU"><div class=3D"gmail-m_-1626441234470666864WordSection1"><p class=3D"=
MsoNormal"><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Q4. If two interior linear rings overlap, then is th=
e result the union of the two holes?</p></div></div></blockquote><div><br><=
/div><div>Geometric operations are outside the scope of the GeoJSON. The fo=
rmat only describes a serialization for polygons. Exterior ring comes first=
, interior rings follow.<br><br></div><div>From a OGC simple features persp=
ective a polygon with overlapping holes is invalid, but I&#39;ve found that=
 GIS software often has fault-tolerant modes that can deal with these kinds=
 of invalid shapes. PostGIS&#39;s buffer(0.0), for example, which I expect =
would indeed replace the overlapping holes with a single hole that is their=
 union, and not create any &quot;anti-holes&quot; or new positive areas.<br=
></div></div><br>-- <br><div class=3D"gmail_signature">Sean Gillies</div>
</div></div></div>

--001a1143f2f29225b305502e470c--


From nobody Tue May 23 06:33:40 2017
Return-Path: <carl.n.reed@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 DCBAF129527 for <geojson@ietfa.amsl.com>; Tue, 23 May 2017 06:33:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 KqOObfyH28Kf for <geojson@ietfa.amsl.com>; Tue, 23 May 2017 06:33:37 -0700 (PDT)
Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (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 B1963129B16 for <geojson@ietf.org>; Tue, 23 May 2017 06:33:35 -0700 (PDT)
Received: by mail-lf0-x230.google.com with SMTP id 99so48752074lfu.1 for <geojson@ietf.org>; Tue, 23 May 2017 06:33:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=wk/5zIPC6OTaqGoQgXKGWouu8RXO1o7K8y2ZEuJblJ0=; b=JTkdeegUPluMXd2ej4Uah8hplqQjsAQ3urk3mXqIfcoz193LAjq8KulndvChpPi7Ww OcL/dWAlJCeNDhNDRcVJi8JfBze6limrte7a7viz/HH7mcfOewE+3+hcFUdMLSZV036m 5vMg5Wg8tFkMW97Nwvh5zGHC1VPgCc5r7yfM8oZauw9WJVZua5qg3tvVz1FJHc9BuT/d pxYcHYub09CEcfOcyguJjt2XBs0JGGdxcmOvN432bOksvCAZ16kz2Cp6lY1cPj/Lz1ab PbCM4ZMILjQQk0vRoga84XrgiiIe5j7wRwhe7DY1M88D+OGQZf3fjQayzTe+U09qCUiy dEkQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=wk/5zIPC6OTaqGoQgXKGWouu8RXO1o7K8y2ZEuJblJ0=; b=F5cSz9B8TeuaZIrYO7qY8KzflwWXBmrPDS5v4yOrpAsgWYqLaCwmFTsqb532wSdxKk C27/Z71/Lh3EcYBcQNgSoaCRTuHlKKk+PR+SOYMus1P3HRBJEz0HA8AOZO7lwCNxF36L aCtRX7G+XgLuTheJfGsXCy26gogDzX7CqjbjMwasxWJOPejRUc+iBKhrFoLXh2OMPRTz FcIS13vHkO7AJMvqvXM/66Sof2mnrzyZo5FBtTPe27c07EH4+NBjA701K2Of3mMEp5/J rM4dORejibngEj7d2TqKb2zxlqDHNhXr30u9oOK0K6A2pDlShT91QmHsxijsy4N+I46x dObg==
X-Gm-Message-State: AODbwcAfNbDJCalVOkIoYIcicPsAF+1refKVdEXZ8ZGNAg6LGuNuCugy C3hroBrR49nSyrHHPPFrHeq/twFalw==
X-Received: by 10.46.22.86 with SMTP id 22mr8372478ljw.126.1495546414025; Tue, 23 May 2017 06:33:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.1.81 with HTTP; Tue, 23 May 2017 06:33:33 -0700 (PDT)
In-Reply-To: <CAOodmJp6g_HWBaz53ZkWnA8QLPg1eFSbknV6S7=mDqo79YsZbQ@mail.gmail.com>
References: <PS1PR06MB1241E7092910654915B99732AAF90@PS1PR06MB1241.apcprd06.prod.outlook.com> <CAOodmJp6g_HWBaz53ZkWnA8QLPg1eFSbknV6S7=mDqo79YsZbQ@mail.gmail.com>
From: Carl Reed <carl.n.reed@gmail.com>
Date: Tue, 23 May 2017 07:33:33 -0600
Message-ID: <CAJcQiLfytmPEysA88zpLRj4tp_GbES9UZ+Uf22D+xMnhmwc60g@mail.gmail.com>
To: Sean Gillies <sean.gillies@gmail.com>
Cc: Chris Goodman <Chris.Goodman@objectconsulting.com.au>,  "geojson@ietf.org" <geojson@ietf.org>
Content-Type: multipart/alternative; boundary="f403045fb462c0d5ed05503108de"
Archived-At: <https://mailarchive.ietf.org/arch/msg/geojson/BXgJGOkz8q9ar-xmoB7zX4DwImQ>
Subject: Re: [Geojson] Question regarding RFC 7946: Interior and Exterior Linear Rings
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: Tue, 23 May 2017 13:33:39 -0000

--f403045fb462c0d5ed05503108de
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Chris -

With regard to

Q1. If an interior linear ring (hole) is not completely inside the exterior
ring (border) of a polygon, is it an illegal polygon?

Whether an encoding allows this case of not, decades of GIS best practice
suggests validation software should throw an error and state that an
interior ring that crosses the exterior ring is invalid.

Regards

Carl Reed, PhD


On Tue, May 23, 2017 at 4:16 AM, Sean Gillies <sean.gillies@gmail.com>
wrote:

> Hi Chris,
>
> On Tue, May 23, 2017 at 9:19 AM, Chris Goodman <Chris.Goodman@
> objectconsulting.com.au> wrote:
>
>> 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.
>>
>>
>>
>>
>>
>> Q1. If an interior linear ring (hole) is not completely inside the
>> exterior ring (border) of a polygon, is it an illegal polygon?
>>
>
>>
>> GeoJson.io allows such an interior ring to be imported. Perhaps it is a
>> bug.
>>
>
> It would be invalid from an OGC simple features perspective but is not
> invalid GeoJSON.
>
>
>>
>>
>> Q2. If the interior ring is not clockwise, then what is the expected
>> behaviour of the polygon?
>>
>
> The same.
>
>
>>
>>
>> Q3. Should =E2=80=98interior linear ring=E2=80=99 and =E2=80=98exterior =
linear ring=E2=80=99 be formally
>> defined in the RFC?
>>
>
> The WG didn't find this necessary. Are you saying it would improve the
> spec? How so?
>
>
>>
>>
>> Q4. If two interior linear rings overlap, then is the result the union o=
f
>> the two holes?
>>
>
> Geometric operations are outside the scope of the GeoJSON. The format onl=
y
> describes a serialization for polygons. Exterior ring comes first, interi=
or
> rings follow.
>
> From a OGC simple features perspective a polygon with overlapping holes i=
s
> invalid, but I've found that GIS software often has fault-tolerant modes
> that can deal with these kinds of invalid shapes. PostGIS's buffer(0.0),
> for example, which I expect would indeed replace the overlapping holes wi=
th
> a single hole that is their union, and not create any "anti-holes" or new
> positive areas.
>
> --
> Sean Gillies
>
> _______________________________________________
> GeoJSON mailing list
> GeoJSON@ietf.org
> https://www.ietf.org/mailman/listinfo/geojson
>
>


--=20
Carl Reed, PhD
Carl Reed and Associates

Mobile: 970-402-0284

=E2=80=9COur liberty depends on the freedom of the press, and that cannot b=
e
limited without being lost.=E2=80=9D

=E2=80=94 Thomas Jefferson, U.S. Founding Father

--f403045fb462c0d5ed05503108de
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div>Chris -<br><br></div>With regard to <b=
r><br>Q1. If an interior linear ring (hole) is not completely inside the=20
exterior ring (border) of a polygon, is it an illegal polygon?<br><br></div=
>Whether an encoding allows this case of not, decades of GIS best practice =
suggests validation software should throw an error and state that an interi=
or ring that crosses the exterior ring is invalid. <br><br></div>Regards<br=
><br></div>Carl Reed, PhD<br><br></div><div class=3D"gmail_extra"><br><div =
class=3D"gmail_quote">On Tue, May 23, 2017 at 4:16 AM, Sean Gillies <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:sean.gillies@gmail.com" target=3D"_blank">=
sean.gillies@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div dir=3D"ltr">Hi Chris,<br><div><div class=3D"gmail_extra"><br><div =
class=3D"gmail_quote">On Tue, May 23, 2017 at 9:19 AM, Chris Goodman <span =
dir=3D"ltr">&lt;<a href=3D"mailto:Chris.Goodman@objectconsulting.com.au" ta=
rget=3D"_blank">Chris.Goodman@<wbr>objectconsulting.com.au</a>&gt;</span> w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-AU">
<div class=3D"m_-7525259051167760105gmail-m_-1626441234470666864WordSection=
1">
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;;color:black">Polygons with more than one of these rings, the =
first MUST be<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;;color:black">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the exterior ring=
, and any others MUST be interior rings.=C2=A0 The<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;;color:black">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 exterior ring bou=
nds the surface, and the interior rings (if<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;;color:black">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 present) bound ho=
les within the surface.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Q1. If an interior linear ring (hole) is not complet=
ely inside the exterior ring (border) of a polygon, is it an illegal polygo=
n? <br></p></div></div></blockquote><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div lang=3D"EN-AU"><div class=3D"m_-7525259051167760105gmail-m_=
-1626441234470666864WordSection1"><p class=3D"MsoNormal"><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">GeoJson.io allows such an interior ring to be import=
ed. Perhaps it is a bug.</p></div></div></blockquote><div><br>It would be i=
nvalid from an OGC simple features perspective but is not invalid GeoJSON.<=
br>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang=
=3D"EN-AU"><div class=3D"m_-7525259051167760105gmail-m_-1626441234470666864=
WordSection1">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Q2. If the interior ring is not clockwise, then what=
 is the expected behaviour of the polygon?</p></div></div></blockquote><div=
><br></div><div>The same.<br></div><div>=C2=A0</div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div lang=3D"EN-AU"><div class=3D"m_-75252590511=
67760105gmail-m_-1626441234470666864WordSection1"><p class=3D"MsoNormal"><u=
></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Q3. Should =E2=80=98interior linear ring=E2=80=99 an=
d =E2=80=98exterior linear ring=E2=80=99 be formally defined in the RFC?</p=
></div></div></blockquote><div><br></div><div>The WG didn&#39;t find this n=
ecessary. Are you saying it would improve the spec? How so?<br></div><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang=3D"=
EN-AU"><div class=3D"m_-7525259051167760105gmail-m_-1626441234470666864Word=
Section1"><p class=3D"MsoNormal"><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Q4. If two interior linear rings overlap, then is th=
e result the union of the two holes?</p></div></div></blockquote><div><br><=
/div><div>Geometric operations are outside the scope of the GeoJSON. The fo=
rmat only describes a serialization for polygons. Exterior ring comes first=
, interior rings follow.<br><br></div><div>From a OGC simple features persp=
ective a polygon with overlapping holes is invalid, but I&#39;ve found that=
 GIS software often has fault-tolerant modes that can deal with these kinds=
 of invalid shapes. PostGIS&#39;s buffer(0.0), for example, which I expect =
would indeed replace the overlapping holes with a single hole that is their=
 union, and not create any &quot;anti-holes&quot; or new positive areas.<sp=
an class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></div></div><=
span class=3D"HOEnZb"><font color=3D"#888888"><br>-- <br><div class=3D"m_-7=
525259051167760105gmail_signature">Sean Gillies</div>
</font></span></div></div></div>
<br>______________________________<wbr>_________________<br>
GeoJSON mailing list<br>
<a href=3D"mailto:GeoJSON@ietf.org">GeoJSON@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/geojson" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/geojson</a><=
br>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail=
_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div><div d=
ir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr=
">Carl Reed, PhD<br></div><div>Carl Reed and Associates<br></div><div><br><=
/div><div>Mobile: 970-402-0284</div></div><div><p>=E2=80=9COur liberty depe=
nds on the freedom of the press, and that cannot be limited without being l=
ost.=E2=80=9D</p>
<p>=E2=80=94 Thomas Jefferson, U.S. Founding Father</p></div></div></div></=
div></div></div></div></div></div>
</div>

--f403045fb462c0d5ed05503108de--

