QueryRunnerExponential | plannerjs - v0.4.1

To improve the user perceived performance, the query gets split into subqueries with exponentially increasing time frames:

minimumDepartureTime + 15 minutes, 30 minutes, 60 minutes, 120 minutes...

In the current implementation, the maximumArrivalTime is ignored

Hierarchy

QueryRunnerExponential

Implements

IQueryRunner

Index

Constructors

constructor

Methods

run

Constructors

constructor

new QueryRunnerExponential(locationResolver: ILocationResolver, publicTransportPlannerFactory: interfaces.Factory<IPublicTransportPlanner>, roadPlanner: IRoadPlanner): QueryRunnerExponential

- Defined in src/query-runner/exponential/QueryRunnerExponential.ts:39
Parameters
- locationResolver: ILocationResolver
- publicTransportPlannerFactory: interfaces.Factory<IPublicTransportPlanner>
- roadPlanner: IRoadPlanner
Returns QueryRunnerExponential

Methods

run

run(query: IQuery): Promise<AsyncIterator<IPath>>

Implementation of IQueryRunner.run
- Defined in src/query-runner/exponential/QueryRunnerExponential.ts:55
Parameters
- query: IQuery
Returns Promise<AsyncIterator<IPath>>

Generated using TypeDoc