Re: [netmod] I-D Action: draft-chopps-netmod-geo-location-00.txt

Christian Hopps <> Thu, 28 February 2019 17:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 574DB130EBE for <>; Thu, 28 Feb 2019 09:10:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3O5b109df46P for <>; Thu, 28 Feb 2019 09:10:26 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 0D712130EB2 for <>; Thu, 28 Feb 2019 09:10:26 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by (Postfix) with ESMTPS id 348C3604F4; Thu, 28 Feb 2019 12:10:25 -0500 (EST)
References: <> <> <>
User-agent: mu4e 1.1.0; emacs 26.1
From: Christian Hopps <>
To: Kent Watsen <>
Cc: Christian Hopps <>, NETMOD Working Group <>
In-reply-to: <>
Date: Thu, 28 Feb 2019 12:10:24 -0500
Message-ID: <>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Archived-At: <>
Subject: Re: [netmod] I-D Action: draft-chopps-netmod-geo-location-00.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 28 Feb 2019 17:10:30 -0000

Kent Watsen <> writes:

> This is a neat draft.   Reminds me of when I worked on the Virtual Reality and
> real-time simulations.    I once wrote a class to convert locations, vectors, and
> orientations to and from WGS84 geocentric coordinate space and topocentric
> coordinate space systems.   I was fresh out of college with a Math degree, so
> of course they gave it to the new guy (me) to figure out  ;)

Thanks. :)

> Anyway, while WGS84 appears to still be applicable, it looks like a lot of other
> standards work has occurred since.   I'd have to dig into it to provide a deeper
> comment.   From a gap-perspective, it seems that this module covers locations,
> but not vectors or orientations (intentional?) Note: "heading" defines a value in
> just a single dimension, so doesn't work for VR.   From an add-perspective, I'm
> surprised to see "speed" included here, at least we always had 1st (and 2nd)
> order temporal information defined elsewhere.

So yeah, there seems to be limitless amounts of work going on at least related or involving this topic.

Regarding WGS84, the WGS84 geoid has been updated multiple times that's what the EGM96 and EGM08 are all about. Each one getting better at handling local gravitational variance, which affects actual sea levels. The original WGS84 was actually very inaccurate. The EGM (earth gravitational model) updates have been fixing this based on data from various satellite missions.

Regarding movement: The point here is to define a geographical location -- so there is a concept of stability involved. It seemed reasonable to include relatively stable movement as well, key thing being stable (e.g., continental drift). Once you start trying to describe motion, all bets are off and we aren't really talking about geographical locations anymore. The text specifically mentions it's not trying to handle 2nd and further derivative motion (or I thought it did :)

I do think I may need to add a second value to the velocity vector to handle 3d movement though as continents are actually moving in 3 dimensions (rising and sinking as well as moving on the globe).

I may also need to add something to indicate the height value being relative to ground (or more). At first I thought this could be captured by a variation of the geodeditc-datum value, but on further thought I think that might not be the right solution -- we also may want to be able to specify multiple different things the height could be relative too (e.g., the ground floor or basement of a building), not just the ground itself.

Orientation (e.g., the way a camera is pointed or what it's focal length is, etc) seems out of scope -- those aren't attributes of location they are describing something else. Orientation, etc, are covered with KML though.


> Kent // contributor
>> On Feb 27, 2019, at 9:39 PM, Christian Hopps <> wrote:
>> FYI.
>>> Begin forwarded message:
>>> From: <>
>>> Subject: I-D Action: draft-chopps-netmod-geo-location-00.txt
>>> Date: February 26, 2019 at 3:59:23 PM EST
>>> To: < <>>
>>> Reply-To: <>
>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>>        Title           : YANG Geo Location
>>>        Author          : Christian Hopps
>>> 	Filename        : draft-chopps-netmod-geo-location-00.txt
>>> 	Pages           : 17
>>> 	Date            : 2019-02-26
>>> Abstract:
>>>   This document defines a generic geographical location object YANG
>>>   grouping.  The geographical location grouping is intended to be used
>>>   in YANG models for specifying a location on or in reference to the
>>>   Earth or any other astronomical object.
>>> The IETF datatracker status page for this draft is:
>>> <>
>>> There are also htmlized versions available at:
>>> Please note that it may take a couple of minutes from the time of submission
>>> until the htmlized version and diff are available at
>>> Internet-Drafts are also available by anonymous FTP at:
>>> _______________________________________________
>>> I-D-Announce mailing list
>>> Internet-Draft directories:
>>> or
>> _______________________________________________
>> netmod mailing list