Profile
A profile is the most important concept to configure routing. There are two important concepts related to this:
- Vehicle: A definition of a vehicle that travels the network. This can be a car but also a pedestrian for example.
- Profile: A profile describes the behaviour of a vehicle.
Default profiles
A few default vehicle profiles are available, but only for OpenStreetMap (OSM).
OpenStreetMap (OSM)
If you are only planning on using OpenStreetMap (OSM) and you just need a default profile these are available:
- Car (
Itinero.Osm.Vehicles.Vehicle.Car
): A default car profile, all restrictions enabled.- Fastest: Calculates fastest functional routes.
- Shortest: The shortest route.
- Classifications: Follows a bit more aggressively the road classifications.
- Bicycle (
Itinero.Osm.Vehicles.Vehicle.Bicycle
): A default bicycle profile.- Fastest: Calculates fastest functional routes.
- Shortest: The shortest route.
- Balanced: Chooses dedicated cycling infrastructure.
- Networks: Chooses dedicated cycling networks.
- Pedestrian (
Itinero.Osm.Vehicles.Vehicle.Pedestrian
): A default pedestrian profile.- Shortest: The shortest route.
You can use the profiles as follows:
// using Itinero;
// using Itinero.IO.Osm;
// using Itinero.Osm.Vehicles;
// get a profile.
var profile = Vehicle.Car.Fastest(); // the default OSM car profile.
Custom profiles
One of the most important features in Itinero is the option to define your own profiles and completely customize them using either:
- Lua Profiles: A scripting language, this allows embedding the profiles in the RouterDb. This is the default and preferred option.
- C# Profile: Define your profiles in C#, or any other .NET language for that matter.
What to read next?
Learn more about the RouterPoint concept.