[Interop-dev] NetJSON + geographic coordinates

[Henning Rogge]

The fact that we have the "NetworkCollection" Object makes the "different
Geo Object" approach much more flexible.

You want to deliver Coordinates AND Graph at the same time (e.g. because of
a hack in the routing agent that transports coordinates)? Just return a
Network Collection with both.

You have two different agents who supply Graph and Geo data? Just use a
small "webserver" that plays multiplexer for the two queries...

Henning
On Thu, May 10, 2018 at 11:56 AM nemesis <(spam-protected)> wrote:

>   On Tue, 08 May 2018 13:29:16 +0000, Henning Rogge <(spam-protected)>
>   wrote:
> > Hi,
> >
> > I don't think this should be a part of the network graph...

>   Why not? Geographic coordinates can be optional but are important if
>   you want to create a network graph with pre-determined positions on a
>   geographic map or on a background image (imagine a floorplan).

>   By adding them so they would be optional we'd also maintain backward
>   compatibility.

> > we could easily use the same "node-id" values and just post it with a
> > different netjson command.
> >
> > something like this:
> >
> > {
> >      "type": "GeoPosition",
> >      "nodes": [
> >          {
> >              "id": "172.16.40.24",
> >              "geometry": {
> >                  "type": "Point",
> >                  "coordinates": [
> >                      13.7457753718,
> >                      43.2589744573
> >                  ]
> >              },
> >      },
> > }

>   There's no need to reinvent a GeoJSON collection:
>   http://wiki.geojson.org/GeoJSON_draft_version_6#GeometryCollection

>   We need a network graph that has also GeoJSON coordinates, if we don't
>   offer a standard way to do this developers will again reinvent their own
>   incompatible way.

>   Fed

> > On Tue, May 8, 2018 at 2:59 PM nemesis <(spam-protected)> wrote:
> >
> >>   Many people have asked for a way to show geographic coordinates in
> >>   NetJSON.
> >
> >>   I'm proposing a simple solution based on GeoJSON that should work
> >> well,
> >>   you can find it here:
> >>   https://github.com/netjson/netjson/issues/62
> >
> >>   Note: I've been working a lot on NetJSON implementations in
> >> OpenWISP
> >>   (monitoring and configuration in particular) and I have not had a
> >> lot of
> >>   time to write here nor update the spec but the work is moving
> >> forward.
> >>   I'm at the meshup event in Berlin right now and I've been told by
> >> Axel
> >>   Neumann that Bmx7 now has a netjson plugin.
> >
> >>   Cheers
> >>   Federico