# Glossary of mobility and data.

Simple definitions to understand transport, local services, and the tools connecting them to your applications.

Source: https://www.roote.ai/en/mobility-glossary/
Language: en
Author: ROOTE

## 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.

Learn more in the guide : [How to find a bike-share bicycle near you?](https://www.roote.ai/en/guides/find-bike-sharing-near-you/)

## 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.

Learn more in the guide : [How to find a bike-share bicycle near you?](https://www.roote.ai/en/guides/find-bike-sharing-near-you/)

## 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.

Learn more in the guide : [Empty or full bike station: what to do?](https://www.roote.ai/en/guides/bike-sharing-station-empty-or-full/)

## 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.

Learn more in the guide : [Empty or full bike station: what to do?](https://www.roote.ai/en/guides/bike-sharing-station-empty-or-full/)

## 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.

Learn more in the guide : [Bike with docking or dockless: what’s the difference?](https://www.roote.ai/en/guides/station-based-vs-dockless-bike-sharing/)

## 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.

Learn more in the guide : [Real-Time Bike Availability: How to Display It in an Application?](https://www.roote.ai/en/guides/real-time-bike-availability-display/)

## 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.

Learn more in the guide : [Real-Time Bike Availability: How to Display It in an Application?](https://www.roote.ai/en/guides/real-time-bike-availability-display/)

## Return

Ending vehicle use following service rules. Return possibilities may differ from pickup options.

Example : A station allows departure but has no return spots.

Learn more in the guide : [Empty or full bike station: what to do?](https://www.roote.ai/en/guides/bike-sharing-station-empty-or-full/)

## 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.

Learn more in the guide : [Real-Time Bike Availability: How to Display It in an Application?](https://www.roote.ai/en/guides/real-time-bike-availability-display/)

## 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.

Learn more in the guide : [how to combine a bike with public transport daily?](https://www.roote.ai/en/guides/combine-bike-sharing-and-public-transport/)

## 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.

Learn more in the guide : [How to find the nearest bus or tram stop?](https://www.roote.ai/en/guides/find-the-nearest-bus-or-tram-stop/)

## 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.

Learn more in the guide : [how to find the right bus stop and direction?](https://www.roote.ai/en/guides/find-the-right-bus-stop-and-direction/)

## 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.

Learn more in the guide : [how to find the right bus stop and direction?](https://www.roote.ai/en/guides/find-the-right-bus-stop-and-direction/)

## 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.

Learn more in the guide : [GTFS, GTFS-RT et GBFS : quelles différences ?](https://www.roote.ai/en/guides/gtfs-gtfs-realtime-and-gbfs-differences/)

## 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.

Learn more in the guide : [how to find the right bus stop and direction?](https://www.roote.ai/en/guides/find-the-right-bus-stop-and-direction/)

## Terminus

End point of a transport route. A line may have variants with different termini.

Example : A short service ends before the usual terminus.

Learn more in the guide : [how to find the right bus stop and direction?](https://www.roote.ai/en/guides/find-the-right-bus-stop-and-direction/)

## 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.

Learn more in the guide : [how to read a bus, tram or metro map?](https://www.roote.ai/en/guides/how-to-read-a-bus-tram-or-metro-map/)

## 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.

Learn more in the guide : [Bus schedules: what's the difference between theoretical and real-time?](https://www.roote.ai/en/guides/scheduled-vs-real-time-transit-departures/)

## 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.

Learn more in the guide : [Bus schedules: what's the difference between theoretical and real-time?](https://www.roote.ai/en/guides/scheduled-vs-real-time-transit-departures/)

## 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.

Learn more in the guide : [How to search for nearby transit stops with an API?](https://www.roote.ai/en/guides/find-nearby-transit-stops-with-an-api/)

## 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.

Learn more in the guide : [How to Create an Assistant That Finds Mobility Options Around an Address?](https://www.roote.ai/en/guides/how-to-create-an-assistant-that-finds-mobility-near-an-address/)

## 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.

Learn more in the guide : [GTFS, GTFS-RT et GBFS : quelles différences ?](https://www.roote.ai/en/guides/gtfs-gtfs-realtime-and-gbfs-differences/)

## 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.

Learn more in the guide : [How to search for nearby transit stops with an API?](https://www.roote.ai/en/guides/find-nearby-transit-stops-with-an-api/)

## 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.

Learn more in the guide : [How to find free public toilets near you](https://www.roote.ai/en/guides/find-free-public-toilets-near-you/)

## 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.

Learn more in the guide : [Accessible public toilets: what to check before you go?](https://www.roote.ai/en/guides/find-accessible-public-toilets/)

## 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.

Learn more in the guide : [Accessible public toilets: what to check before you go?](https://www.roote.ai/en/guides/find-accessible-public-toilets/)

## 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.

Learn more in the guide : [How to find free public toilets near you](https://www.roote.ai/en/guides/find-free-public-toilets-near-you/)

## 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.

Learn more in the guide : [How to search for nearby transit stops with an API?](https://www.roote.ai/en/guides/find-nearby-transit-stops-with-an-api/)

## 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.

Learn more in the guide : [How to search for nearby transit stops with an API?](https://www.roote.ai/en/guides/find-nearby-transit-stops-with-an-api/)

## 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.

Learn more in the guide : [How to search for nearby transit stops with an API?](https://www.roote.ai/en/guides/find-nearby-transit-stops-with-an-api/)

## Geolocation

Obtaining a geographic position by a device or app. Depends on permissions and available accuracy.

Example : Location button requests browser permission.

Learn more in the guide : [How to integrate a mobility map into your website?](https://www.roote.ai/en/guides/how-to-integrate-a-mobility-map-into-your-website/)

## 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.

Learn more in the guide : [How to search for nearby transit stops with an API?](https://www.roote.ai/en/guides/find-nearby-transit-stops-with-an-api/)

## 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.

Learn more in the guide : [How to search for nearby transit stops with an API?](https://www.roote.ai/en/guides/find-nearby-transit-stops-with-an-api/)

## 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.

Learn more in the guide : [How to search for nearby transit stops with an API?](https://www.roote.ai/en/guides/find-nearby-transit-stops-with-an-api/)

## 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.

Learn more in the guide : [How to Create an Assistant That Finds Mobility Options Around an Address?](https://www.roote.ai/en/guides/how-to-create-an-assistant-that-finds-mobility-near-an-address/)

## 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.

Learn more in the guide : [What is an MCP server and what is it used for?](https://www.roote.ai/en/guides/what-is-an-mcp-server-and-what-is-it-used-for/)

## 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.

Learn more in the guide : [How to Create an Assistant That Finds Mobility Options Around an Address?](https://www.roote.ai/en/guides/how-to-create-an-assistant-that-finds-mobility-near-an-address/)

## 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.

Learn more in the guide : [How to integrate a mobility map into your website?](https://www.roote.ai/en/guides/how-to-integrate-a-mobility-map-into-your-website/)

## 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.

Learn more in the guide : [How to search for nearby transit stops with an API?](https://www.roote.ai/en/guides/find-nearby-transit-stops-with-an-api/)

## 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.

Learn more in the guide : [How to search for nearby transit stops with an API?](https://www.roote.ai/en/guides/find-nearby-transit-stops-with-an-api/)

## Map zoom

Map view enlargement level. Controls display but does not replace API request radius.

Example : zoom=15 zooms in on the map view.

Learn more in the guide : [How to integrate a mobility map into your website?](https://www.roote.ai/en/guides/how-to-integrate-a-mobility-map-into-your-website/)

## 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.

Learn more in the guide : [Bus schedules: what's the difference between theoretical and real-time?](https://www.roote.ai/en/guides/scheduled-vs-real-time-transit-departures/)

## 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.

Learn more in the guide : [Bus schedules: what's the difference between theoretical and real-time?](https://www.roote.ai/en/guides/scheduled-vs-real-time-transit-departures/)

## 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.

Learn more in the guide : [Real-Time Bike Availability: How to Display It in an Application?](https://www.roote.ai/en/guides/real-time-bike-availability-display/)

## 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.

Learn more in the guide : [Real-Time Bike Availability: How to Display It in an Application?](https://www.roote.ai/en/guides/real-time-bike-availability-display/)

## 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.

Learn more in the guide : [Real-Time Bike Availability: How to Display It in an Application?](https://www.roote.ai/en/guides/real-time-bike-availability-display/)

## 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.

Learn more in the guide : [Real-Time Bike Availability: How to Display It in an Application?](https://www.roote.ai/en/guides/real-time-bike-availability-display/)

## 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.

Learn more in the guide : [Real-Time Bike Availability: How to Display It in an Application?](https://www.roote.ai/en/guides/real-time-bike-availability-display/)

## 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.

Learn more in the guide : [No result or API error: how to tell the difference?](https://www.roote.ai/en/guides/no-result-or-api-error-how-to-tell-the-difference/)

## 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.

Learn more in the guide : [How to Create an Assistant That Finds Mobility Options Around an Address?](https://www.roote.ai/en/guides/how-to-create-an-assistant-that-finds-mobility-near-an-address/)

## 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.

Learn more in the guide : [How to search for nearby transit stops with an API?](https://www.roote.ai/en/guides/find-nearby-transit-stops-with-an-api/)

## 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.

Learn more in the guide : [GTFS, GTFS-RT et GBFS : quelles différences ?](https://www.roote.ai/en/guides/gtfs-gtfs-realtime-and-gbfs-differences/)

## 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.

Learn more in the guide : [GTFS, GTFS-RT et GBFS : quelles différences ?](https://www.roote.ai/en/guides/gtfs-gtfs-realtime-and-gbfs-differences/)

## 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.

Learn more in the guide : [GTFS, GTFS-RT et GBFS : quelles différences ?](https://www.roote.ai/en/guides/gtfs-gtfs-realtime-and-gbfs-differences/)

## 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.

Learn more in the guide : [No result or API error: how to tell the difference?](https://www.roote.ai/en/guides/no-result-or-api-error-how-to-tell-the-difference/)

## 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.

Learn more in the guide : [API or MCP: Which to Choose for Integrating Mobility Data?](https://www.roote.ai/en/guides/api-or-mcp-which-to-choose-for-integrating-mobility-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.

Learn more in the guide : [How to search for nearby transit stops with an API?](https://www.roote.ai/en/guides/find-nearby-transit-stops-with-an-api/)

## 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.

Learn more in the guide : [How to search for nearby transit stops with an API?](https://www.roote.ai/en/guides/find-nearby-transit-stops-with-an-api/)

## 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.

Learn more in the guide : [How to integrate a mobility map into your website?](https://www.roote.ai/en/guides/how-to-integrate-a-mobility-map-into-your-website/)

## 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.

Learn more in the guide : [No result or API error: how to tell the difference?](https://www.roote.ai/en/guides/no-result-or-api-error-how-to-tell-the-difference/)

## 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.

Learn more in the guide : [No result or API error: how to tell the difference?](https://www.roote.ai/en/guides/no-result-or-api-error-how-to-tell-the-difference/)

## 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.

Learn more in the guide : [No result or API error: how to tell the difference?](https://www.roote.ai/en/guides/no-result-or-api-error-how-to-tell-the-difference/)

## 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.

Learn more in the guide : [No result or API error: how to tell the difference?](https://www.roote.ai/en/guides/no-result-or-api-error-how-to-tell-the-difference/)

## 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.

Learn more in the guide : [No result or API error: how to tell the difference?](https://www.roote.ai/en/guides/no-result-or-api-error-how-to-tell-the-difference/)

## 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.

Learn more in the guide : [How to Connect an AI Assistant to MCP ROOTE?](https://www.roote.ai/en/guides/connect-ai-assistant-to-mcp-roote/)

## 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.

Learn more in the guide : [How to search for nearby transit stops with an API?](https://www.roote.ai/en/guides/find-nearby-transit-stops-with-an-api/)

## 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.

Learn more in the guide : [How to search for nearby transit stops with an API?](https://www.roote.ai/en/guides/find-nearby-transit-stops-with-an-api/)

## 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.

Learn more in the guide : [How to integrate a mobility map into your website?](https://www.roote.ai/en/guides/how-to-integrate-a-mobility-map-into-your-website/)

## 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.

Learn more in the guide : [How to integrate a mobility map into your website?](https://www.roote.ai/en/guides/how-to-integrate-a-mobility-map-into-your-website/)

## 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.

Learn more in the guide : [What is an MCP server and what is it used for?](https://www.roote.ai/en/guides/what-is-an-mcp-server-and-what-is-it-used-for/)

## 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.

Learn more in the guide : [What is an MCP server and what is it used for?](https://www.roote.ai/en/guides/what-is-an-mcp-server-and-what-is-it-used-for/)

## MCP client

AI app component communicating with an MCP server. Manages protocol exchanges for this connection.

Example : Client sends search arguments to ROOTE.

Learn more in the guide : [What is an MCP server and what is it used for?](https://www.roote.ai/en/guides/what-is-an-mcp-server-and-what-is-it-used-for/)

## 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.

Learn more in the guide : [What is an MCP server and what is it used for?](https://www.roote.ai/en/guides/what-is-an-mcp-server-and-what-is-it-used-for/)

## 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.

Learn more in the guide : [How to Connect an AI Assistant to MCP ROOTE?](https://www.roote.ai/en/guides/connect-ai-assistant-to-mcp-roote/)

## 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.

Learn more in the guide : [How to Connect an AI Assistant to MCP ROOTE?](https://www.roote.ai/en/guides/connect-ai-assistant-to-mcp-roote/)

## 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.

Learn more in the guide : [How to Create an Assistant That Finds Mobility Options Around an Address?](https://www.roote.ai/en/guides/how-to-create-an-assistant-that-finds-mobility-near-an-address/)

## 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.

Learn more in the guide : [How to Create an Assistant That Finds Mobility Options Around an Address?](https://www.roote.ai/en/guides/how-to-create-an-assistant-that-finds-mobility-near-an-address/)

## 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.

Learn more in the guide : [How to Create an Assistant That Finds Mobility Options Around an Address?](https://www.roote.ai/en/guides/how-to-create-an-assistant-that-finds-mobility-near-an-address/)

## 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.

Learn more in the guide : [What is an MCP server and what is it used for?](https://www.roote.ai/en/guides/what-is-an-mcp-server-and-what-is-it-used-for/)