Open APIs

Expand all | Collapse all

TMF 675 location and Geojson

  • 1.  TMF 675 location and Geojson

    TM Forum Member
    Posted Dec 18, 2018 11:42
    Dear community,

    Is there a way to have the TMF 675 GeographicLocation using GeoJSON standard (RFC7946) for encoding geographic data ? Do you have experience with this?



    Alexis de Peufeilhoux
    Deutsche Telekom AG

  • 2.  RE: TMF 675 location and Geojson

    TM Forum Member
    Posted Jan 18, 2019 10:30
    Edited by Vance Shipley Jan 19, 2019 02:01
    TMF675 is fairly compatible with RFC7946 although it doesn't use exactly the same encoding:
    geometryType:  point, line, graph, ring, polygon
    geometry:    [{X, Y, Z},...]
    GeoJSON (RFC7946)
    type:  Point, MultiPoint, LineString, MultiLineString, Polygon, MultiPolygon, GeometryCollection
    coordinates:  [X, Y] or [X, Y, Z] or [[X, Y], ...] or [[X, Y, Z],...]

    So it's very easy to map between the two representations.  The way I see it though they have different use cases. GeoJSON is most commonly used as an interchange format for large data sets such as plotting data sets onto maps, or the maps themselves (feature collections), whereas TMF675 is intended to provide a single location or feature.

    At SigScale we use publicly available GeoJSON encoded geographical maps however those are then re-encoded using the TopoJSON format which yields far smaller file sizes. Then we use the D3 JavaScript library to display country/region/city maps and plot geographic locations (e.g. cell sites) in our web components. A web application may download a TopoJSON map on loading and on later retrieving a location ({X,Y,Z}) via TMF675 display it on a map such as presenting a view of all the critical alarm locations. D3 creates amazing visualizations with a tiny amount of code as it uses a functional programming (FP) style and as an FP programmer myself I find it a joy to work with.

    Vance Shipley
    SigScale Global Inc.