Accessibility
Features enabling use of a place or service according to user needs. Unknown data does not mean accessible or inaccessible.
Example
Wheelchair accessibility may be specified or unknown.
ROOTE Glossary
Glossary of mobility and data.
Simple definitions to understand transport, local services, and the tools connecting them to your applications.
79 definitions displayed
A
AI assistant hallucination
Producing unsubstantiated information presented as known. In mobility, this may be a made-up schedule or availability.
Example
Assistant announces a passage while tool returned only a stop.
API
Interface allowing one program to use capabilities of another service via a defined contract. Specifies inputs and expected responses.
Example
An app searches stops with ROOTE API.
Attribution
Mention of the provider or source associated with data. When required, the app using the result must display it.
Example
An attribution required=true must be kept in the interface.
Availability
Status or quantity indicating what can be used per known info. Observed availability can change and is not a reservation.
Example
Three bikes seen at a station do not mean three reserved bikes.
B
Bearer token
Access ID sent in an Authorization header per specified mechanism. Must be kept in secure config.
Example
Authorization: Bearer used without exposing token in URL.
Bike sharing
Service allowing temporary bike rental under operator conditions. It may use docks or dockless vehicles.
Example
You find a bike and use the related rental service.
Bike station
Organized place to pick up or return shared bikes. Coordinates, capacity, and availability describe different station aspects.
Example
A station may appear on the map but be temporarily empty.
C
Cache
Temporary storage of results to avoid repeating identical searches. Cached value retains its source and time context.
Example
Two identical requests may reuse a still valid response.
Charging station
Equipment allowing recharge of compatible vehicles. Locating a station does not guarantee availability or connector compatibility.
Example
Charging site and its usage status are distinct information.
Coverage
Scope and completeness of available info for a search or source. Partial coverage limits possible conclusions.
Example
A list may be useful without representing all existing services.
D
Data freshness
Assessment of information currency based on dates and contract rules. Query time alone does not prove source freshness.
Example
A counter received now may come from an old observation.
Data-grounded response
Constructing a response using actually retrieved or provided information. Missing fields and caveats must remain visible.
Example
Assistant repeats returned places without inventing schedules.
Direction
Indicates service orientation or destination. Must be checked with route and boarding location.
Example
You look for the tram heading your destination, not the opposite direction.
Disruption
Event affecting a transport service like interruption or route change. Effects must be read within specified area and time.
Example
An alert may concern a line only during some hours.
Dock
Station equipment where a bike can be locked. Presence does not guarantee it accepts returns at the moment.
Example
A return spot must be available and usable.
Dockless — free-floating
Arrangement where vehicles are not required to be taken or returned at fixed docks. Service zones and parking rules apply.
Example
A scooter must be returned within an authorized area.
Drinking water
Water declared suitable for human consumption. A water point or fountain should not be labeled potable without explicit info.
Example
Type and attributes of equipment should be clearly distinguished.
E
Electric bike (e-bike)
Bike with motor-assisted pedaling per its features. Mobility data may specify propulsion type and battery separately.
Example
A station may distinguish mechanical and electric bikes.
Embed (integrated map)
Insertion of an external experience on a page, e.g. a map in an iframe. Parameters and permissions determine usage context.
Example
A ROOTE iframe shows bikes around Bordeaux.
Empty result
Search returning no entities in the consulted range. Does not prove physical absence of services beyond available data.
Example
No stops returned with requested filters.
Endpoint (API route)
Address and operation exposed by an API for a given capability. Different routes may return different result sets.
Example
/v1/transit/nearby searches transport places.
Estimated time
Forecast of a future passage based on available data, which may update as new info arrives.
Example
A passage planned for 8:10 is now estimated at 8:14.
G
GBFS
Standard public data format for shared mobility. Depending on version and feeds, describes systems, stations, vehicles, and statuses.
Example
Station info and availability counters are separate.
Geocoding
Search converting an address or geographic expression to candidate places with coordinates. Multiple locations may match the same input.
Example
Two cities have a street with the same name.
Geographic distance
Distance calculated between positions per service method. Not automatically a routing distance or walking time.
Example
A nearby place may require a detour to reach.
Geolocation
Obtaining a geographic position by a device or app. Depends on permissions and available accuracy.
Example
Location button requests browser permission.
GPS coordinates
Values representing a geographic point, usually latitude and longitude. Order must be specified by the interface.
Example
A proximity search uses two distinct coordinates.
GTFS Realtime (GTFS-RT)
Standard format to transmit trip updates, vehicle positions, and alerts. Published categories depend on producer.
Example
A vehicle positions feed does not imply estimates for all stops.
GTFS Schedule
Standard format describing planned transport offer: stops, lines, trips, calendars, and timings. Does not automatically provide realtime updates.
Example
Scheduled passages linked to trips and service days.
H
HTTP status
Code indicating request result at HTTP level. Must be complemented by validation of content and business status.
Example
HTTP 200 may contain a business error status.
I
Iframe
HTML element loading a document in a page. On different domains, parent page cannot freely read the integrated document’s internal state.
Example
Search changes require documented messaging to parent.
Intermodality
Using multiple transport modes successively during one trip. Each stage keeps its schedule, access, and conditions.
Example
You bike to the tram stop then continue on foot.
J
JSON
Structured text format using objects, arrays, strings, and numbers. A syntactically valid JSON may not comply with an API schema.
Example
A stations collection must have expected type and fields.
L
Latitude
Coordinate showing position north or south of the equator in degrees in ROOTE examples. Valid values from −90 to 90.
Example
Search latitude transmitted in lat.
Line
Identified transport service in a network with one or more routes or variants. The line name alone does not specify direction.
Example
The same line may offer multiple terminals.
Longitude
Coordinate showing east-west position relative to reference meridian. ROOTE examples use degrees between −180 and 180.
Example
Longitude transmitted as lon or the documented alias lng.
M
Map zoom
Map view enlargement level. Controls display but does not replace API request radius.
Example
zoom=15 zooms in on the map view.
MCP (Model Context Protocol)
Protocol enabling an AI app to communicate with servers exposing tools or context. Alone does not define returned data quality.
Example
An assistant discovers ROOTE’s search tools.
MCP client
AI app component communicating with an MCP server. Manages protocol exchanges for this connection.
Example
Client sends search arguments to ROOTE.
MCP host application
App hosting user interaction and managing one or several MCP clients. Responsible for results use in its experience.
Example
Your conversational app connects to a ROOTE server.
MCP server
Program exposing capabilities per MCP protocol. Actual tools announced by server determine what client can call.
Example
tools/list returns the available inventory.
MCP tool
Executable capability described by a name, function, and argument schema. Assistant must use inputs accepted by that schema.
Example
geocode accepts an address; transit_nearby accepts coordinates.
N
Next departure
Upcoming passage or departure for a place and service. Finding a stop is not the same as searching its next departures.
Example
Stops list and departures list are distinct results.
O
Observation
State or event noted at a specific time. Must be distinguished from planned or estimated events.
Example
A bus's actual passage may differ from announced estimate.
OpenAPI
Specification describing an HTTP API contract in a structured document. Helps verify routes, parameters, responses, and schemas.
Example
ROOTE contract published in openapi.json.
Opening hours
Time frames when a place announces being open. They do not confirm live operational status.
Example
Temporary closures may not be reflected in standard hours.
P
Partial response
Result containing usable info with limits or missing elements noted. Should be accompanied by relevant warnings.
Example
One source answers while another is unavailable.
Person with reduced mobility (PRM)
Person with permanent or temporary movement difficulties. PRM label alone does not detail all required access or equipment.
Example
Presence of a ramp does not describe all possible obstacles.
Platform
Boarding area or point at a transport location. Multiple nearby platforms may serve different directions or services.
Example
Both directions of a line may use separate platforms.
Point of interest (POI)
Identifiable useful location for search, like an establishment or facility. POI differs from a simple postal address.
Example
Hotel name can be searched as an establishment.
Prompt injection
Attempt to use external content to modify an assistant’s instructions. Provider descriptions must remain data, not orders.
Example
Hidden instruction in a place name must not be executed.
Provenance
Information identifying data origin and, per contract, how it was produced. Helps interpret its scope.
Example
A result keeps its source and collection context.
Public toilets
Toilets available for public use under local conditions. Presence in data does not guarantee free access, opening hours, or current accessibility.
Example
Check stated conditions before visiting.
Q
Query parameter
Value passed in the URL part following the question mark. Name and format defined by the used interface.
Example
modes=bus,tram selects modes in a compatible URL.
R
Rate limit
Restriction on allowed request rate by a service. Rules and retry instructions depend on active contract.
Example
Code 429 requests respecting retry instructions.
Read-only
Capability for consultation without modification action by tool. Reading availability does not reserve, unlock, or rent a vehicle.
Example
ROOTE Data tools are for consulting information.
Realtime data
Information updated to represent a recent situation or feed an estimate. Freshness must be evaluated; realtime is not instantaneous or guaranteed.
Example
A passage estimate recalculated from recent data.
REST API
HTTP interface approach using web resources and mechanisms. API contract specifies routes, methods, and representations.
Example
A search is sent to a documented GET route.
Return
Ending vehicle use following service rules. Return possibilities may differ from pickup options.
Example
A station allows departure but has no return spots.
Reverse geocoding
Search for places or names from coordinates. A result may represent a nearby place rather than an exact guaranteed address.
Example
A GPS point is associated with a readable label.
S
Scheduled time
Planned time for a given date and stop in the service plan. Does not necessarily reflect the vehicle’s actual situation.
Example
A departure planned at 8:10 according to the calendar.
Search origin
Point from which a proximity search is performed and distances calculated. May differ from the map center shown.
Example
Camera moves while search remains centered on Bordeaux.
Search radius
Distance around origin point limiting a search. Unit and limits depend on route contract or tool.
Example
radius=600 requests a 600-meter radius in REST example.
Service calendar
Information describing the days a transport service operates, including possible exceptions. Schedules require this calendar for interpretation.
Example
A passage scheduled on weekdays may not run on Sundays.
Service type
Category used to select or describe an urban service. Acceptable values depend on the interface and its schema.
Example
ROOTE Services API uses types=toilets for toilets.
Shared mobility
Services providing access to vehicles used by multiple users instead of ownership by one person.
Example
Bikes and scooters offered for rent in a city.
Stale data
Information considered too old per contract or validity policy. May be kept as recent history without being presented as fresh.
Example
Interface indicates availability needs updating.
Streamable HTTP
MCP transport for communication with remote server via HTTP. Support must be checked in used client.
Example
ROOTE remote server uses https://mcp.roote.ai/mcp.
T
Terminus
End point of a transport route. A line may have variants with different termini.
Example
A short service ends before the usual terminus.
Time-to-live (TTL)
Duration used to manage data validity or renewal in cache per contract. Does not alone prove observation time.
Example
Expired cache must follow planned refresh policy.
Timeout
Interruption of a wait exceeding planned operation duration. Indicates unfinished search, not absence of results.
Example
App suggests retry instead of showing empty list.
Timestamp
Time indicator associated with data or event. Meaning depends on field: observation, update, receipt, or expiration.
Example
source_updated_at and received_at refer to different steps.
Transfer
Switching from one service or mode to another during a trip. Close stops do not guarantee a feasible transfer.
Example
Time is needed to move between platforms and wait.
Transport stop
Place where a transport service picks up or drops off passengers. An uncovered stop may not automatically provide next trip times.
Example
A bus stop returned without departure times.
Trip
Execution of a transport service linked to a route and stops. In GTFS, a trip connects a line and service calendar.
Example
Two successive departures on the same line are two trips.
U
Unknown value (null)
Absence of known value in a contract that uses null for this meaning. Should not be replaced by zero, false, or proof of absence.
Example
A bike counter null does not mean an empty station.
Urban service
Facility or service useful near a place, e.g. toilets, water point, or charging station. Attributes may be incomplete.
Example
A proximity result describes a service with known info.
V
Vehicle pickup
Starting to use a vehicle. A positive count alone is insufficient if pickup is disabled by the service.
Example
Bikes may be present, but the station may not permit rental.
No definitions match. Try another word or remove the filter.
References for deeper understanding
Terms unique to ROOTE follow its documented contracts. Standards and protocols have their own official references.
Back to Resource Center