Re: [dispatch] GeoJSON question

Sean Gillies <> Fri, 24 July 2015 08:13 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 6B0C21B302C for <>; Fri, 24 Jul 2015 01:13:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
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, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id eTIJBNOy5FkO for <>; Fri, 24 Jul 2015 01:13:01 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F3CFC1B3024 for <>; Fri, 24 Jul 2015 01:13:00 -0700 (PDT)
Received: by wibxm9 with SMTP id xm9so17544834wib.0 for <>; Fri, 24 Jul 2015 01:12:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=LXdtBkYyNnJKsl+qTZ8vjmlCqdzOPVUkVK+Jbo8pqCs=; b=qW1TT6QH+z035aK9X5OstZZCer7OFBP54BEaZ8cR8dS/YBfmf9fdohPvpXQGZkmGLv 1SCwbepjU/YsRp6eeZOknpAFki/8nv69bQyceV+qG1kcBoK/uB0DMZTEgLOjuZerWSE2 Jkp87XekJ2KQ5O/g1eDOCZbObDSKjFjDsZLEs1aAUr/IPBRJ8GrkmUe9Gb8q5MX6QvFv Wt5pI4jdUvdewWdR8x5QAKLjPiPagJnIpSRlipxg8cEqV74v2xbJFpIbW3J4L/SRYD8C STk05Ye03hsujUyuKqeSlkg2sXXn7Jad3rD2O1uHCEfgEuz4rAZTXoEgVYZpsIOdXztN tl3A==
MIME-Version: 1.0
X-Received: by with SMTP id ec4mr24300142wjb.3.1437725579440; Fri, 24 Jul 2015 01:12:59 -0700 (PDT)
Received: by with HTTP; Fri, 24 Jul 2015 01:12:59 -0700 (PDT)
In-Reply-To: <>
References: <>
Date: Fri, 24 Jul 2015 10:12:59 +0200
Message-ID: <>
From: Sean Gillies <>
To: DISPATCH list <>
Content-Type: multipart/alternative; boundary="047d7bf0ef187276a4051b9a92f0"
Archived-At: <>
Subject: Re: [dispatch] GeoJSON question
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 24 Jul 2015 08:13:02 -0000

On Wed, Jul 22, 2015 at 10:09 AM, James Winterbottom <> wrote:

> It feels like the question is the target of the location ever going to be
> conveyed with the location information?

Are you asking if it's possible to convey, say, phone numbers and locations
of the the phones and the semantics needed to track the devices and their
users together in GeoJSON? This would require a protocol or framework
external to the GeoJSON format. GeoJSON specifies that Features should have
an "id" property and that it should uniquely identify the feature within
its collection. There's no requirement or implication that the id
identifies the thing described by the Feature. GeoJSON's "id" is no more
than Atom's Entry "id" (RFC 4287 has had a major influence on GeoJSON).
Semantics such as what it would mean to use, eg, "tel:867-5309" as a
feature id are not defined by GeoJSON.

Sean Gillies