
From u.schochtert@gmail.com  Tue Apr 25 05:31:12 2017
Return-Path: <u.schochtert@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 74E8812EB50 for <geojson@ietfa.amsl.com>; Tue, 25 Apr 2017 05:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, URIBL_BLOCKED=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 X5MBSuo6rbNb for <geojson@ietfa.amsl.com>; Tue, 25 Apr 2017 05:31:11 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (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 D927412EC80 for <geojson@ietf.org>; Tue, 25 Apr 2017 05:31:07 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id r16so207799458ioi.2 for <geojson@ietf.org>; Tue, 25 Apr 2017 05:31:07 -0700 (PDT)
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=pA8tn7mcJ4GGfOmh/jVGqIEtnmrgxJBjOXa44R29JP0=; b=gQM2eG07J1I38kvy8S3dx2fksETyjvIL9IVc/VotJ3d40oh3ZQHJhYC+TB6duuVL5Z hcvV+6FzT8Hj7FZ3l2kQ9JsoZDWtU0CsF4VRNG6czPrRNeOupkeknSrw5clbjd/7wlOy Iv96/d+C9EIKDkOVEUqH+daBS67T7G7Xjk5nz2RZI6fSoZE47LY0B3nWu3I1aUIPJkqP olYdAMXLFPLHzryDmIRnDdpx//vNHDbMftpZ/pO9UgO4aVG3crunIRHDnmcmdPv71INw zKXSdoIIXPEWytBtv1U5Gp5w0nQffa+3BCN1wt7sUXaHQt7nfSBX9Cz03yJsiA0/A+H6 7cmQ==
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=pA8tn7mcJ4GGfOmh/jVGqIEtnmrgxJBjOXa44R29JP0=; b=Bk/8g8wYw1ihXc1b+z3xJiP/+9d+ASnuxDsQZX7ocDe3Aqw6OqxUroSP6JTO3+AYPp NvyODo0DTdWjrCnsnvTVzj/DkLgOm+ry4YCSyY7r+Ge3b+o0Rt3nVwhdhvlJATWiupDg UAUTXePEQTMOzKreB0cQqz2s+Htt4/TiesyyvKkXD9FIxmownRWha8AZyx5UlLEdAWlb YKvJgshGoyJnKKaBVTe/sy5wxcc6B9OgcREHSFAzfrXXKLNOquSmnUZWeJ0xfJQJ1+AA gGdOybvfpqccMoD5IpiKxmI7Sbg7uQEOjyEe95/gvVA92Csa9sX148XYWPPlP8L/tEBg sTQA==
X-Gm-Message-State: AN3rC/7MEiL7hKBDwgXDxfseNpDgYBdn+rHxUFeK1L8cHQXM2KlV7gCT 5ZLkjJoNF7JR2cIWRXB5Xz+Br6aYgMdD
X-Received: by 10.107.26.1 with SMTP id a1mr14340588ioa.72.1493123466865; Tue, 25 Apr 2017 05:31:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.113.200 with HTTP; Tue, 25 Apr 2017 05:31:06 -0700 (PDT)
From: Udo Schochtert <u.schochtert@gmail.com>
Date: Tue, 25 Apr 2017 14:31:06 +0200
Message-ID: <CAENDquxrvzBNRa_doW2TprbE=OQfu9RJRs7RpT29zSLtye9_jg@mail.gmail.com>
To: geojson@ietf.org
Content-Type: multipart/alternative; boundary=001a113fe2d8d93345054dfce50c
Archived-At: <https://mailarchive.ietf.org/arch/msg/geojson/7d_Mpv0mVbsjZmB1KMW4-899tdI>
X-Mailman-Approved-At: Tue, 25 Apr 2017 23:19:36 -0700
Subject: [Geojson] RFC 7946 - composing geometry objects with "mixed" positions
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, 25 Apr 2017 12:37:34 -0000

--001a113fe2d8d93345054dfce50c
Content-Type: text/plain; charset=UTF-8

hi,

I have a quick question regarding RFC 7946 specs.

according
  https://tools.ietf.org/html/rfc7946#section-3.1.1
a position is an array of numbers which MUST have 2 elements and SHOULD not
extend beyond 3 elements.

so a valid Point (containing 2 elements) is
{
  "type": "Point",
  "coordinates": [100.0, 0.0]
}
and one containing 3 elements
{
  "type": "Point",
  "coordinates": [101.0, 1.0, 1.0]
}
is valid as well.

my question is if the following MultiPoint (composed by"mixed" positions)
would be valid as well

{
  "type": "MultiPoint",
  "coordinates": [
    [100.0, 0.0],
    [101.0, 1.0, 1.0]
  ]
}


that would also apply to other geometries composed by"mixed" positions as
well (e.g. LineString, Polygon, etc.). correct?

thanks, udo

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

<div dir=3D"ltr">hi,<div><br></div><div>I have a quick question regarding R=
FC 7946 specs.<br><div><br></div><div>according</div><div>=C2=A0=C2=A0<a hr=
ef=3D"https://tools.ietf.org/html/rfc7946#section-3.1.1">https://tools.ietf=
.org/html/rfc7946#section-3.1.1</a></div><div>a position is an array of num=
bers which MUST have 2 elements and SHOULD not extend beyond 3 elements.</d=
iv><div><br></div><div>so a valid Point (containing 2 elements) is</div><di=
v>{<br>=C2=A0 &quot;type&quot;: &quot;Point&quot;,<br>=C2=A0 &quot;coordina=
tes&quot;: [100.0, 0.0]<br>}<br></div><div>and one containing 3 elements<br=
></div><div>{<br>=C2=A0 &quot;type&quot;: &quot;Point&quot;,<br>=C2=A0 &quo=
t;coordinates&quot;: [101.0, 1.0, 1.0]<br>}<br></div><div>is valid as well.=
</div><div><br></div><div>my question is if the following MultiPoint (compo=
sed by&quot;mixed&quot; positions) would be valid as well</div><div><pre cl=
ass=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bo=
ttom:0px;color:rgb(0,0,0)">{
  &quot;type&quot;: &quot;MultiPoint&quot;,
  &quot;coordinates&quot;: [
    [100.0, 0.0],
    [101.0, 1.0, 1.0]
  ]
}</pre></div><div><br></div></div><div>that would also apply to other geome=
tries composed by&quot;mixed&quot; positions as well (e.g. LineString, Poly=
gon, etc.). correct?</div><div><br></div><div>thanks, udo</div><div><br></d=
iv></div>

--001a113fe2d8d93345054dfce50c--


From nobody Wed Apr 26 08:59:40 2017
Return-Path: <erik.wilde@dret.net>
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 0F20313147B for <geojson@ietfa.amsl.com>; Wed, 26 Apr 2017 08:59:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.391
X-Spam-Level: 
X-Spam-Status: No, score=-0.391 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=dret.net
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 yb9tGnQqDKnY for <geojson@ietfa.amsl.com>; Wed, 26 Apr 2017 08:59:37 -0700 (PDT)
Received: from postoffice.gristmillmedia.com (postoffice.gristmillmedia.com [96.30.18.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B425212F9A8 for <geojson@ietf.org>; Wed, 26 Apr 2017 08:59:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dret.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=2K9+izOVSIxtC03RNTSdH5RM0kIUg7yAHMI7tG1BFOg=; b=JADTHNI7uPScOGKgjPlZikSBPi xxc3mJ6AI1F+hZ8E014IjFloHoKaGAS4bfALe96j34mqLfBEWfXqrs4W//a8P7BoGclRsCh/PRMGg mqc16SXpTLpOEpJTCfc8UwAy6KCYVc9Qg9MldiQR12xSOQsxOF/r8T8/c/sMxZ4LJ78VXnUdMWmln v3UoOJTIwfScHnx2QyRKF7mS+DuxSNuu6aZcmTD8G14/QoS/AbjGM8/qkddmQbAzlv1G7TTtmlb9A HwqVJQqv5SzPJn2mdi/g0JhK3/e2B0PZ9ePKzKFsn0zG3Wvr4SdlSOdhw00fuCjRQEFzdYYY6Hy7s jL5Ntm5Q==;
Received: from [194.75.229.113] (port=29987 helo=dretpro.ca.com) by postoffice.gristmillmedia.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <erik.wilde@dret.net>) id 1d3PLs-00022B-NH; Wed, 26 Apr 2017 11:59:36 -0400
To: Udo Schochtert <u.schochtert@gmail.com>, geojson@ietf.org
References: <CAENDquxrvzBNRa_doW2TprbE=OQfu9RJRs7RpT29zSLtye9_jg@mail.gmail.com>
From: Erik Wilde <erik.wilde@dret.net>
Message-ID: <b25f82c9-c10a-40a1-5e32-13ac778f0195@dret.net>
Date: Wed, 26 Apr 2017 17:59:35 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAENDquxrvzBNRa_doW2TprbE=OQfu9RJRs7RpT29zSLtye9_jg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - postoffice.gristmillmedia.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dret.net
X-Get-Message-Sender-Via: postoffice.gristmillmedia.com: authenticated_id: birdhouse@dret.net
X-Authenticated-Sender: postoffice.gristmillmedia.com: birdhouse@dret.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/geojson/zbm8BBOWMQKK6_N1GP9SKF3nPUw>
Subject: Re: [Geojson] RFC 7946 - composing geometry objects with "mixed" positions
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: Wed, 26 Apr 2017 15:59:39 -0000

hello udo.

On 2017-04-25 14:31, Udo Schochtert wrote:
> my question is if the following MultiPoint (composed by"mixed"
> positions) would be valid as well
>
> {
>   "type": "MultiPoint",
>   "coordinates": [
>     [100.0, 0.0],
>     [101.0, 1.0, 1.0]
>   ]
> }
>
> that would also apply to other geometries composed by"mixed" positions
> as well (e.g. LineString, Polygon, etc.). correct?

that's a good question. afaict, there is nothing in the spec language 
that keeps you from doing this. however, the semantics are unspecified. 
it is not clear if positions without elevations should have elevation 
zero or "inherit" the elevation of the last elevation-labeled position. 
my suggestion would be to not use this "mixed model", but that's just my 
personal opinion.

cheers,

dret.

-- 
erik wilde | mailto:erik.wilde@dret.net |
            | http://dret.net/netdret    |
            | http://twitter.com/dret    |


From nobody Wed Apr 26 09:12:12 2017
Return-Path: <tim.schaub@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 63FFB1314A0 for <geojson@ietfa.amsl.com>; Wed, 26 Apr 2017 09:12:10 -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 tc7VFRJGoMls for <geojson@ietfa.amsl.com>; Wed, 26 Apr 2017 09:12:08 -0700 (PDT)
Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::234]) (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 4D169131498 for <geojson@ietf.org>; Wed, 26 Apr 2017 09:12:08 -0700 (PDT)
Received: by mail-wr0-x234.google.com with SMTP id w50so2987858wrc.0 for <geojson@ietf.org>; Wed, 26 Apr 2017 09:12:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=kERXZ2Ax6yN9raMO8J2Xjz9tcieVU2/383YqNCaegmY=; b=GRLWaDL63XgAHfYK3UBpV5aeZ0WYVf2n6UCHuGN6VW5SapluuiNU4Nuyr8JtshvrvO GlzqWtzRwRFb2ywbJlcct7/gworNrCTSZF4b+Bsl3xqoXOBk6lutxdBMq4ZU8FSz4Yb/ zBTDZOrAB6DT/RnUd4Ds0LMOnWtxopbEiVbuYBjnCNLN2po0C1v0zBWuziikg1yWgDfR ce+BzPSw/7uEAKlb0c0aY9v5OHgyw1cuhQHcSI8gjZXfgYhJbJ7qdGTtrjrb9r2MWcx6 JipeS0DVHIezFN277GzNI+GSqhhyB2g4qiBjsCYDW4m4IIdMR/DVEkCAllUcEayHpJlb Smbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=kERXZ2Ax6yN9raMO8J2Xjz9tcieVU2/383YqNCaegmY=; b=jp/mtrX20VP/LQD9REEIQPh5q3vqsECsC1U3x5ew2QJroX1PDLCFzlqcpinqzmxnn+ GQIeCvKTHzfL6ujvEIewB3095vP0tLIR6kwcOgkxrmlU7Rp+ncTQjuBtu9e+9QHuHG2g OOLeiKBxi13s7j20+XICwchP1ILq46t3OMYrNGPjtpwHVKvzoOxj01DuLsJAMqMzKG1T BHusRRk5sR8lwZFPs8U0ymC0hGh+Yql8IjCTzg3hF7NJFuG94rIGGFbdr6AXC1YwRtKC OEvlCjHeufskMFuw4ykamGsTwQi38pG11SXj8V0XJkBNmbVhqp66Onz6vqBGriD4oR+L 8c2w==
X-Gm-Message-State: AN3rC/41ngC0AT4/IFNW88j7WJYfs2f0MVwbZbxeib9wdtV/F2ypx8og kC0WLLLSfVA0lGF1NKKzWQE1X+xzag==
X-Received: by 10.223.164.13 with SMTP id d13mr376586wra.37.1493223126526; Wed, 26 Apr 2017 09:12:06 -0700 (PDT)
MIME-Version: 1.0
References: <CAENDquxrvzBNRa_doW2TprbE=OQfu9RJRs7RpT29zSLtye9_jg@mail.gmail.com> <b25f82c9-c10a-40a1-5e32-13ac778f0195@dret.net>
In-Reply-To: <b25f82c9-c10a-40a1-5e32-13ac778f0195@dret.net>
From: Tim Schaub <tim.schaub@gmail.com>
Date: Wed, 26 Apr 2017 16:11:55 +0000
Message-ID: <CAKdrn+e2ddGdc=w82hV7mveF=f_HF5nDi86J0JzmMqoLDpONHQ@mail.gmail.com>
To: Erik Wilde <erik.wilde@dret.net>, Udo Schochtert <u.schochtert@gmail.com>,  geojson@ietf.org
Content-Type: multipart/alternative; boundary=f403045f21d006fb60054e141abf
Archived-At: <https://mailarchive.ietf.org/arch/msg/geojson/6b64mMcP3dwsNh1Ul2HIzgQOBMc>
Subject: Re: [Geojson] RFC 7946 - composing geometry objects with "mixed" positions
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: Wed, 26 Apr 2017 16:12:10 -0000

--f403045f21d006fb60054e141abf
Content-Type: text/plain; charset=UTF-8

There will be parsers that make assumptions about the consistency of
dimensions. So while not strictly invalid, you'll likely sacrifice
interoperability if you plan to share data with inconsistent dimensions.

Tim

On Wed, Apr 26, 2017 at 8:59 AM Erik Wilde <erik.wilde@dret.net> wrote:

> hello udo.
>
> On 2017-04-25 14:31, Udo Schochtert wrote:
> > my question is if the following MultiPoint (composed by"mixed"
> > positions) would be valid as well
> >
> > {
> >   "type": "MultiPoint",
> >   "coordinates": [
> >     [100.0, 0.0],
> >     [101.0, 1.0, 1.0]
> >   ]
> > }
> >
> > that would also apply to other geometries composed by"mixed" positions
> > as well (e.g. LineString, Polygon, etc.). correct?
>
> that's a good question. afaict, there is nothing in the spec language
> that keeps you from doing this. however, the semantics are unspecified.
> it is not clear if positions without elevations should have elevation
> zero or "inherit" the elevation of the last elevation-labeled position.
> my suggestion would be to not use this "mixed model", but that's just my
> personal opinion.
>
> cheers,
>
> dret.
>
> --
> erik wilde | mailto:erik.wilde@dret.net |
>             | http://dret.net/netdret    |
>             | http://twitter.com/dret    |
>
> _______________________________________________
> GeoJSON mailing list
> GeoJSON@ietf.org
> https://www.ietf.org/mailman/listinfo/geojson
>

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

There will be parsers that make assumptions about the consistency of dimens=
ions.  So while not strictly invalid, you&#39;ll likely sacrifice interoper=
ability if you plan to share data with inconsistent dimensions.<br><br>Tim<=
br><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Wed, Apr 26, 2017 at =
8:59 AM Erik Wilde &lt;<a href=3D"mailto:erik.wilde@dret.net">erik.wilde@dr=
et.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hello udo.<br=
>
<br>
On 2017-04-25 14:31, Udo Schochtert wrote:<br>
&gt; my question is if the following MultiPoint (composed by&quot;mixed&quo=
t;<br>
&gt; positions) would be valid as well<br>
&gt;<br>
&gt; {<br>
&gt;=C2=A0 =C2=A0&quot;type&quot;: &quot;MultiPoint&quot;,<br>
&gt;=C2=A0 =C2=A0&quot;coordinates&quot;: [<br>
&gt;=C2=A0 =C2=A0 =C2=A0[100.0, 0.0],<br>
&gt;=C2=A0 =C2=A0 =C2=A0[101.0, 1.0, 1.0]<br>
&gt;=C2=A0 =C2=A0]<br>
&gt; }<br>
&gt;<br>
&gt; that would also apply to other geometries composed by&quot;mixed&quot;=
 positions<br>
&gt; as well (e.g. LineString, Polygon, etc.). correct?<br>
<br>
that&#39;s a good question. afaict, there is nothing in the spec language<b=
r>
that keeps you from doing this. however, the semantics are unspecified.<br>
it is not clear if positions without elevations should have elevation<br>
zero or &quot;inherit&quot; the elevation of the last elevation-labeled pos=
ition.<br>
my suggestion would be to not use this &quot;mixed model&quot;, but that&#3=
9;s just my<br>
personal opinion.<br>
<br>
cheers,<br>
<br>
dret.<br>
<br>
--<br>
erik wilde | mailto:<a href=3D"mailto:erik.wilde@dret.net" target=3D"_blank=
">erik.wilde@dret.net</a> |<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | <a href=3D"http://dret.net/netd=
ret" rel=3D"noreferrer" target=3D"_blank">http://dret.net/netdret</a>=C2=A0=
 =C2=A0 |<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | <a href=3D"http://twitter.com/d=
ret" rel=3D"noreferrer" target=3D"_blank">http://twitter.com/dret</a>=C2=A0=
 =C2=A0 |<br>
<br>
_______________________________________________<br>
GeoJSON mailing list<br>
<a href=3D"mailto:GeoJSON@ietf.org" target=3D"_blank">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/listinfo/geojson</a><br>
</blockquote></div>

--f403045f21d006fb60054e141abf--


From nobody Wed Apr 26 11:53:45 2017
Return-Path: <u.schochtert@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 F0BF0127444 for <geojson@ietfa.amsl.com>; Wed, 26 Apr 2017 11:53:40 -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 CaQbME2fUtrX for <geojson@ietfa.amsl.com>; Wed, 26 Apr 2017 11:53:38 -0700 (PDT)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (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 C81D412944C for <geojson@ietf.org>; Wed, 26 Apr 2017 11:53:38 -0700 (PDT)
Received: by mail-it0-x22f.google.com with SMTP id f187so8607079ite.1 for <geojson@ietf.org>; Wed, 26 Apr 2017 11:53:38 -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=mJoR7Pyig6OUEQBjgMD47zDuDcF0eUAZ1csd41hAwTY=; b=hba3tT6jhGvaC7oYKgwS5crSOH7LxO84e0glndl6pSbNn6i8MCApLfj9Bln4Jn7f5O 6MdLPXzmIHQA6TnaET74P03ydFeZzPL3NAmSiBv3/rCkxg/y8R8kjLHU8OI787hMEQdL qtNCzZFmiwL/PMU8R1vQhEmrfv2LO3WOrUW4kQlLQwcoVWG/KgZpav4F36+5EIB+lg9P Mw6yR/X7qXv7K79bwi2cVHNZTyZGY9BtAHR6JtPgvDq5+sSPy/d8O0uK30vgrfk77iCb nz+X/9uVajCwOUXBOTqXiHeNWVbeXLFWANAHef/o/oEQbLqrx5sqeoxUKenyrlLBWr2g +BQA==
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=mJoR7Pyig6OUEQBjgMD47zDuDcF0eUAZ1csd41hAwTY=; b=qyapqwyzNADJii9pON2hmG4arhHKlHWnlvxhmZhnVOGO/WtbfnldkWwqgEBkcZDVzO FeToKZENirnxaOFOfgjE3L9xxDwq1WuujCJA4BW0WqLy3vlso5rUCI1tEfTrkNsUd+dR qT+ck2PON7zsmSpAMtJaQao/FQC/ANl51TiqpRi0fp6ZWHeqZOp9igzZkHqtMe4siwet pBhszQsjQZGIkl0PCCURQrH2lfsMR5thV3jHXvBTuSy/DMp5cIn4sjLQI43/aMpNly4y bj6XqSrhPbCPRNN7R74HVPcFTHCfuUxaHUInevQsfKMgw5MYNXYDJ33rEPP6hTOyLwql 8n1g==
X-Gm-Message-State: AN3rC/7Ybq6w30RV7K8LIZUFTsArA7GfEXZwPuUZTfTrlx89qv7nnhXo 01E8y1MsBYo+/Ok92fdud7CcIqxybQ==
X-Received: by 10.36.95.144 with SMTP id r138mr12341592itb.11.1493232818051; Wed, 26 Apr 2017 11:53:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.113.200 with HTTP; Wed, 26 Apr 2017 11:53:37 -0700 (PDT)
In-Reply-To: <CAKdrn+e2ddGdc=w82hV7mveF=f_HF5nDi86J0JzmMqoLDpONHQ@mail.gmail.com>
References: <CAENDquxrvzBNRa_doW2TprbE=OQfu9RJRs7RpT29zSLtye9_jg@mail.gmail.com> <b25f82c9-c10a-40a1-5e32-13ac778f0195@dret.net> <CAKdrn+e2ddGdc=w82hV7mveF=f_HF5nDi86J0JzmMqoLDpONHQ@mail.gmail.com>
From: Udo Schochtert <u.schochtert@gmail.com>
Date: Wed, 26 Apr 2017 20:53:37 +0200
Message-ID: <CAENDquxAi9EdTa1LmmtyzQTuJhtv0mfrc_B=8GSsUMVCeb0ssw@mail.gmail.com>
To: Tim Schaub <tim.schaub@gmail.com>, Erik Wilde <erik.wilde@dret.net>
Cc: geojson@ietf.org
Content-Type: multipart/alternative; boundary=001a1144bdb4afe606054e165b8e
Archived-At: <https://mailarchive.ietf.org/arch/msg/geojson/8C_ilVbZD3Y2HY2DFfQn0IwmKKE>
Subject: Re: [Geojson] RFC 7946 - composing geometry objects with "mixed" positions
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: Wed, 26 Apr 2017 18:53:41 -0000

--001a1144bdb4afe606054e165b8e
Content-Type: text/plain; charset=UTF-8

erik, tim, thanks for your feedback.

I was thinking about this because I contributed to the python-geojson
project to help fix issue
  https://github.com/frewsxcv/python-geojson/issues/79
with pull request
  https://github.com/frewsxcv/python-geojson/pull/92/files
which now supports processing of positions containing 3 elements (the
altitude/elevation being the 3rd element).

I was wondering how the validation should treat the "mixed" scenario and
what the specs would recommend.

I understand that having "mixed" geojson data is not good and should be
avoided.

for me the question is answered.

thanks, udo


On Wed, Apr 26, 2017 at 6:11 PM, Tim Schaub <tim.schaub@gmail.com> wrote:

> There will be parsers that make assumptions about the consistency of
> dimensions. So while not strictly invalid, you'll likely sacrifice
> interoperability if you plan to share data with inconsistent dimensions.
>
> Tim
>
> On Wed, Apr 26, 2017 at 8:59 AM Erik Wilde <erik.wilde@dret.net> wrote:
>
>> hello udo.
>>
>> On 2017-04-25 14:31, Udo Schochtert wrote:
>> > my question is if the following MultiPoint (composed by"mixed"
>> > positions) would be valid as well
>> >
>> > {
>> >   "type": "MultiPoint",
>> >   "coordinates": [
>> >     [100.0, 0.0],
>> >     [101.0, 1.0, 1.0]
>> >   ]
>> > }
>> >
>> > that would also apply to other geometries composed by"mixed" positions
>> > as well (e.g. LineString, Polygon, etc.). correct?
>>
>> that's a good question. afaict, there is nothing in the spec language
>> that keeps you from doing this. however, the semantics are unspecified.
>> it is not clear if positions without elevations should have elevation
>> zero or "inherit" the elevation of the last elevation-labeled position.
>> my suggestion would be to not use this "mixed model", but that's just my
>> personal opinion.
>>
>> cheers,
>>
>> dret.
>>
>> --
>> erik wilde | mailto:erik.wilde@dret.net |
>>             | http://dret.net/netdret    |
>>             | http://twitter.com/dret    |
>>
>> _______________________________________________
>> GeoJSON mailing list
>> GeoJSON@ietf.org
>> https://www.ietf.org/mailman/listinfo/geojson
>>
>

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

<div dir=3D"ltr">erik, tim, thanks for your feedback.<div><br></div><div>I =
was thinking about this because I contributed to the python-geojson project=
 to help fix issue<div>=C2=A0 <a href=3D"https://github.com/frewsxcv/python=
-geojson/issues/79">https://github.com/frewsxcv/python-geojson/issues/79</a=
></div><div>with pull request</div><div>=C2=A0 <a href=3D"https://github.co=
m/frewsxcv/python-geojson/pull/92/files">https://github.com/frewsxcv/python=
-geojson/pull/92/files</a></div><div>which now supports processing of posit=
ions containing 3 elements (the altitude/elevation being the 3rd element).<=
/div><div><br></div><div>I was wondering how the validation should treat th=
e &quot;mixed&quot; scenario and what the specs would recommend.</div><div>=
<br></div><div>I understand that having &quot;mixed&quot; geojson data is n=
ot good and should be avoided.</div><div><br></div><div>for me the question=
 is answered.</div><div><br></div><div>thanks, udo<div><br></div></div></di=
v></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, A=
pr 26, 2017 at 6:11 PM, Tim Schaub <span dir=3D"ltr">&lt;<a href=3D"mailto:=
tim.schaub@gmail.com" target=3D"_blank">tim.schaub@gmail.com</a>&gt;</span>=
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">There will be parsers that make a=
ssumptions about the consistency of dimensions.  So while not strictly inva=
lid, you&#39;ll likely sacrifice interoperability if you plan to share data=
 with inconsistent dimensions.<br><br>Tim<br><br><div class=3D"gmail_quote"=
><div><div class=3D"h5"><div dir=3D"ltr">On Wed, Apr 26, 2017 at 8:59 AM Er=
ik Wilde &lt;<a href=3D"mailto:erik.wilde@dret.net" target=3D"_blank">erik.=
wilde@dret.net</a>&gt; wrote:<br></div></div></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex"><div><div class=3D"h5">hello udo.<br>
<br>
On 2017-04-25 14:31, Udo Schochtert wrote:<br>
&gt; my question is if the following MultiPoint (composed by&quot;mixed&quo=
t;<br>
&gt; positions) would be valid as well<br>
&gt;<br>
&gt; {<br>
&gt;=C2=A0 =C2=A0&quot;type&quot;: &quot;MultiPoint&quot;,<br>
&gt;=C2=A0 =C2=A0&quot;coordinates&quot;: [<br>
&gt;=C2=A0 =C2=A0 =C2=A0[100.0, 0.0],<br>
&gt;=C2=A0 =C2=A0 =C2=A0[101.0, 1.0, 1.0]<br>
&gt;=C2=A0 =C2=A0]<br>
&gt; }<br>
&gt;<br>
&gt; that would also apply to other geometries composed by&quot;mixed&quot;=
 positions<br>
&gt; as well (e.g. LineString, Polygon, etc.). correct?<br>
<br>
that&#39;s a good question. afaict, there is nothing in the spec language<b=
r>
that keeps you from doing this. however, the semantics are unspecified.<br>
it is not clear if positions without elevations should have elevation<br>
zero or &quot;inherit&quot; the elevation of the last elevation-labeled pos=
ition.<br>
my suggestion would be to not use this &quot;mixed model&quot;, but that&#3=
9;s just my<br>
personal opinion.<br>
<br>
cheers,<br>
<br>
dret.<br>
<br>
--<br>
erik wilde | mailto:<a href=3D"mailto:erik.wilde@dret.net" target=3D"_blank=
">erik.wilde@dret.net</a> |<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | <a href=3D"http://dret.net/netd=
ret" rel=3D"noreferrer" target=3D"_blank">http://dret.net/netdret</a>=C2=A0=
 =C2=A0 |<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | <a href=3D"http://twitter.com/d=
ret" rel=3D"noreferrer" target=3D"_blank">http://twitter.com/dret</a>=C2=A0=
 =C2=A0 |<br>
<br></div></div>
______________________________<wbr>_________________<br>
GeoJSON mailing list<br>
<a href=3D"mailto:GeoJSON@ietf.org" target=3D"_blank">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>
</blockquote></div>
</blockquote></div><br></div>

--001a1144bdb4afe606054e165b8e--


From nobody Thu Apr 27 13:17:41 2017
Return-Path: <wwwrun@rfc-editor.org>
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 951C8129C5C; Thu, 27 Apr 2017 13:17:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 XX2GtKya7JWC; Thu, 27 Apr 2017 13:17:33 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80350129C5F; Thu, 27 Apr 2017 13:13:22 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DDB3AB80E84; Thu, 27 Apr 2017 13:12:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, geojson@ietf.org
Message-Id: <20170427201257.DDB3AB80E84@rfc-editor.org>
Date: Thu, 27 Apr 2017 13:12:57 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/geojson/kOHPA3XM2PpE1obSSf7HWxEhd8A>
Subject: [Geojson] RFC 8142 on GeoJSON Text Sequences
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: Thu, 27 Apr 2017 20:17:35 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8142

        Title:      GeoJSON Text Sequences 
        Author:     S. Gillies
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2017
        Mailbox:    sean.gillies@gmail.com
        Pages:      5
        Characters: 9063
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-geojson-text-sequence-05.txt

        URL:        https://www.rfc-editor.org/info/rfc8142

        DOI:        10.17487/RFC8142

This document describes the GeoJSON text sequence format and
"application/geo+json-seq" media type.  This format is based on
JavaScript Object Notation (JSON) text sequences and GeoJSON, and it
makes arbitrarily large geographic datasets incrementally parseable
without restricting the form of GeoJSON texts within a sequence.

This document is a product of the Geographic JSON Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


