track-annotation-int.routing.mbition.de
Open in
urlscan Pro
2001:41d0:700:6908::2
Public Scan
Submitted URL: https://track-annotation-int.routing.mbition.de/
Effective URL: https://track-annotation-int.routing.mbition.de/v1/swagger
Submission: On August 30 via automatic, source certstream-suspicious — Scanned from DE
Effective URL: https://track-annotation-int.routing.mbition.de/v1/swagger
Submission: On August 30 via automatic, source certstream-suspicious — Scanned from DE
Form analysis 1 forms found in the DOM
<form class="download-url-wrapper"><input class="download-url-input" type="text" value="/v1/swagger.json"><button class="download-url-button button">Explore</button></form>Text Content
Explore
MBITION TRACK ANNOTATION SERVICE (INTEGRATION)
1.0.0
OAS 3.0
/v1/swagger.json
The Track Annotation Service annotates tracks with open data from Wikidata,
Wikipedia, and Wikimedia Commons.
VERSION CHANGES
Compared to the v0 interface, v1 introduced the following breaking changes have
been made:
* Enums are now given in capital letters. This affects the landmark_type and
sources properties.
* Sources are now given as an array instead of a string.
* All images (from Wikimedia Commons, and Yelp) are now collected in an array
stored in the media property. Each entry has a type and a role property
denoting the kind of the medium. Furthermore, copyrights are given per
medium.
* The wikipedia property has been overworked and now contains the pageviews
property.
* The service currently only supports the languages de, en, and fr.
* The input parameters includeAnnotations and includeRoute have been removed.
These exclusions can now be achieved by setting the landmark_types property
in the config payload.
The following additions have been made since v0:
* Stable feature ids: Instead of using UUIDs for the features, feature ids are
now stable (unless the geometry or name changes). An example is
1-de-23320000-08636285319ea164-brandenburger_to.
* Add option exclude_poi_ids to exclude POIs by feature id.
* External data sources (Yelp, Wikipedia, Wikimedia Commons) are now cached
such that subsequent calls to the service are faster.
* Each feature is annotated with a route_side property that indicates whether
the feature is left or right of the route or if it is crossing the route.
* A /meta endpoint was added to show information on the configuration and used
data sources.
* Added wikivoyage property with links and excerpts to Wikivoyage.
* Added wikimedia_category property with the Wikimedia Commons category name
(WIP).
* Added wikimedia_gallery property with the Wikimedia Commons gallery name
(WIP).
* Mappo has been dropped as data source.
* Added NATURAL landmark type for forests, national parks, lakes, etc.
* Added /v1/boundingbox endpoint was added to query POIs in a bounding box
(WIP).
* Added source WIKIVOYAGE for content from Wikivoyage.
* Made configuration desired_border_crossings nullable to display all border
crossings of all types.
* Changed default clustering algorithm to use_administrative_area_clustering.
* Added add_route_profile boolean to config to allow switching off route
profiles.
* Added poi_search_use_segments and poi_search_number_segments to search for
POIs in multiple segments of the route rather than with a single search for
the whole route. Note that the limit poi_search_limit is used per segment
which can return up to poi_search_limit * poi_search_number_segments POIs.
* Added route_projection property with the coordinates of the closest point on
the route to the respective feature.
* Added cluster_usage_type property to cluster features to denote the intended
frontend (e.g., SPEECH or WEBSITE, and ADDITIONAL)
* Added rank property modeling a 5-star rating for POIs (not yet used for
sorting).
* Added split_large_administrative_area_clusters option to replace too large
administrative area clusters (larger than
maximal_administrative_area_cluster_size_square_kilometers) with a dilated
hull of the POIs in the administrative area. With create_dilated_hull, the
same dilated hull is also used for geometric clusters.
* Overworked clustering approach. Can be disabled with new config key
"use_new_clustering_approach": false.
* Added landmark type VISIBILITY to provide a geometry where each POI is
visible. This landmark type is disabled by default.
* Added property cluster_shape_type to cluster features to denote the nature of
the cluster's shape.
* Adjusted property route_projection to features with route_side CROSS to
denote the entry point of the route to the feature instead of an arbitrary
projection point.
CONFIGURATION
The default configuration can be found in the /meta endpoint (see config key).
Individual keys can be overridden by adding them to the request like this:
{
"polyline": "uqq_IwpzpA|JaY|J~MzFfO`KzMvLxNbNtStDtHzB~k@`@`Kr@fMgFfAsMjAc@mR",
"precision": 5,
"config": {
"poi_search_limit": 10,
"maximal_route_distance_for_pois_meters": 100.0
}
}
SCHEMA
The schema described below is authoritative.
Contact Niels Lohmann
Servers
https://track-annotation-dev.routing.mbition.de - MBition dev
serverhttps://track-annotation-int.routing.mbition.de - MBition int
serverhttps://track-annotation.routing.mbition.de - MBition prod server
DEFAULT
POST
/v1/api/annotate
Return a route in GeoJSON format
POST
/v1/api/boundingbox
Return POIs in a bounding box.
POST
/v1/api/conversions/from_gpx
POST
/v1/api/generate
Generate a route in GeoJSON format
GET
/v1/api/generate_tour/{qid}
Create tour
POST
/v1/api/match
Return a route in GeoJSON format
GET
/v1/api/relevance/{qid}
Show relevance information
GET
/v1/meta
Show meta information
SCHEMAS
Audio
BoundingBoxInput
ClusterShapeType
ClusterType
ClusterUsageType
Config
Copyright
ElevationProfile
Error
Feature
FeatureCollection
GenerationInput
Gpx
Image
ImageRole
LandmarkType
MediaType
Meta
Properties
RelevanceInformation
RouteInput
RouteMetaData
RouteProfile
RouteSide
Source
TrafficProfile
Video
WikipediaArticle
Yelp