Route statistics

Table of contents

• Goal
• Format and access
  • Example
• Content

Goal

The route statistics field is a dynamic set of metadata linked to a route. This metadata originates from different automatic procedures or manual input.

Format and access

The route statistics are stored in a json object with one or more key-value pairs or properties and can be accessed through the route webservice.

Example

{
    "match": 1,
    "routing": {
        "mtbFlandersNetwork": 0.7887323943662
    },
    "roadCondition": {
        "paved": {
            "good": 0.57795110913297,
            "bad": 0
        },
        "unpaved": {
            "good": 0.076817325002343,
            "bad": 0.1774807307714
        },
        "unknown": 0.16775083509328,
        "google": "??o|HA{~x@EwtN@}bBB}ez@E}eLD_wt@CsqBBk|GE{fCDszJC{zMAarEDk`@Ei`JDwnV@sb@GgvDD}xB@}||@GgwVDcp`DEysk@@sqAAwh[@iaNBchiB@gwFGcbx@FmgWAyql@CcwHBmnsACwb@BmrX@m_n@AueX@umVAkxS@}aHG}aRDqpLEskEFwiBAs`YCun`@Dwkz@Eq{_@B{}u@@qbRGwlg@F{hr@Amx~CEetSDssUCqkWDqaDGmhQ@i{DD}yCAopBCugBBgkeBEmmNDkhw@Ea_OF"
    },
    "cobblestone": {
        "score": 0
    },
    "singletrack": {
        "score": 0.3747783,
        "google": "?AaoaO@mRAysmk@@w]A}kM@"
    },
    "cycleway": {
        "score": 0.35225558481226,
        "google": "??k|bAAwtN@ieGAwxD@gmYA{f@@usSA}eL@qhHAktB@ewEA_a@@yfIAavU@_oKA{fC@ovYAarE@k`@A_aQ@uqPAgvD@{v`AAgwV@cp`DAoryA@k`qBAcbx@@c_[Agrr@@k}hAAapI@gdlAAaxT@_jt@A}aR@qpLAkvH@s`YAun`@@cqSAevfA@okOAkqe@@qbRAwlg@@ibrEAetS@ssUAycS@iiHAwdW@qgv@A_d@@yrx@AmmN@qfKAo}@@yoBA{~T@sqOAa_O@"
    },
    "carFree": {
        "score": 0.29386418699782,
        "google": "??k|bAAwtN@img@A{f@@usSA}eL@_gaAA{fC@ovYAarE@k`@AsyE@ay[AgvD@{v`AAgwV@cp`DAoryA@k`qBAcbx@@c_[Agrr@@k}hAAapI@gdlAAaxT@_jt@A}aR@qpLAkvH@s`YAun`@@cqSAevfA@maiAAwlg@@ibrEAetS@ssUAycS@iiHAmhQ@u|vBAmmN@khw@Aa_O@"
    },
    "urban": {
        "score": 0.36849068191202,
        "google": "?AsetH@wxiVAkto@@gqAAqv~A@krr@Aahh@@_hnLAimnA@_d@AujpC@"
    },
    "nature": {
        "score": 0.65014256722606,
        "google": "??setHAwxiV@kto@AgqA@qv~AAkrr@@ahh@Amq`M@{c|@A_d@@ywtBAcbQ@"
    },
    "water": {
        "score": 0.049339074331742,
        "google": "??m|rQC}vF@ynNAemEBu}_BAwoe@@wkza@CarG@omYAe_HB"
    },
    "traffic": {
        "score": 0.042041275887919,
        "google": "??ynPAieP@a|}@Cw}KB}xs@CsaDBmgx^AavE@avwCCkqe@B{zeLA_d@@igvAEidHD"
    },
    "noise": {
        "score": 0.33016939658314
    },
    "accessibility": {
        "score": 0.98423062646557,
        "google": "?AcrrA@}bBA{d}B@sqBA}_xI@gqf@A_e|J@wb@Aovh]@"
    },
    "bearing": "southeast",
    "colaScore": 1
}

Content

Aside from the score the relative distance of features along the route is also stored as encoded google linestring (read more about that here). For example:

1. From 0 to 0.23 => paved good condition
2. From 0.23 to 0.60 => unpaved bad condition
3. From 0.60 to 0.65 => paved good condition
4. From 0.65 to 1.0 => unpaved good condition

Back to RouteYou