Hey,
You can actually find that info in two ways:
-
If you’re running GraphHopper locally, open http://localhost:8989/info.
It shows a JSON with all available encoded values and their possible categories.
Here’s an example of the output after enabling both car and foot profiles:
{
"bbox": [
-53.270096,
-25.980898,
-29.306872,
-14.171793
],
"profiles": [
{
"name": "car"
},
{
"name": "foot"
}
],
"version": "11.0",
"elevation": false,
"encoded_values": {
"car_access": [
"true",
"false"
],
"car_average_speed": [
">number",
"<number"
],
"road_access": [
"YES",
"DESTINATION",
"CUSTOMERS",
"DELIVERY",
"PRIVATE",
"AGRICULTURAL",
"FORESTRY",
"NO"
],
"foot_access": [
"true",
"false"
],
"hike_rating": [
">number",
"<number"
],
"mtb_rating": [
">number",
"<number"
],
"foot_priority": [
">number",
"<number"
],
"country": [
"MISSING",
"AFG",
"AGO",
"AIA",
"ALB",
"AND",
"ARE",
"ARG",
"ARM",
"ATG",
"AUS",
"AUT",
"AZE",
"BDI",
"BEL",
"BEN",
"BFA",
"BGD",
"BGR",
"BHR",
"BHS",
"BIH",
"BLR",
"BLZ",
"BMU",
"BOL",
"BRA",
"BRB",
"BRN",
"BTN",
"BWA",
"CAF",
"CAN",
"CHE",
"CHL",
"CHN",
"CIV",
"CMR",
"COD",
"COG",
"COK",
"COL",
"COM",
"CPV",
"CRI",
"CUB",
"CYM",
"CYP",
"CZE",
"DEU",
"DJI",
"DMA",
"DNK",
"DOM",
"DZA",
"ECU",
"EGY",
"ERI",
"ESP",
"EST",
"ETH",
"FIN",
"FJI",
"FLK",
"FRA",
"FRO",
"FSM",
"GAB",
"GBR",
"GEO",
"GGY",
"GHA",
"GIB",
"GIN",
"GMB",
"GNB",
"GNQ",
"GRC",
"GRD",
"GRL",
"GTM",
"GUY",
"HND",
"HRV",
"HTI",
"HUN",
"IDN",
"IMN",
"IND",
"IOT",
"IRL",
"IRN",
"IRQ",
"ISL",
"ISR",
"ITA",
"JAM",
"JEY",
"JOR",
"JPN",
"KAZ",
"KEN",
"KGZ",
"KHM",
"KIR",
"KNA",
"KOR",
"KWT",
"LAO",
"LBN",
"LBR",
"LBY",
"LCA",
"LIE",
"LKA",
"LSO",
"LTU",
"LUX",
"LVA",
"MAR",
"MCO",
"MDA",
"MDG",
"MDV",
"MEX",
"MHL",
"MKD",
"MLI",
"MLT",
"MMR",
"MNE",
"MNG",
"MOZ",
"MRT",
"MSR",
"MUS",
"MWI",
"MYS",
"NAM",
"NER",
"NGA",
"NIC",
"NIU",
"NLD",
"NOR",
"NPL",
"NRU",
"NZL",
"OMN",
"PAK",
"PAN",
"PCN",
"PER",
"PHL",
"PLW",
"PNG",
"POL",
"PRK",
"PRT",
"PRY",
"PSE",
"QAT",
"ROU",
"RUS",
"RWA",
"SAU",
"SDN",
"SEN",
"SGP",
"SGS",
"SHN",
"SLB",
"SLE",
"SLV",
"SMR",
"SOM",
"SRB",
"SSD",
"STP",
"SUR",
"SVK",
"SVN",
"SWE",
"SWZ",
"SYC",
"SYR",
"TCA",
"TCD",
"TGO",
"THA",
"TJK",
"TKL",
"TKM",
"TLS",
"TON",
"TTO",
"TUN",
"TUR",
"TUV",
"TWN",
"TZA",
"UGA",
"UKR",
"URY",
"USA",
"UZB",
"VAT",
"VCT",
"VEN",
"VGB",
"VNM",
"VUT",
"WSM",
"XKX",
"YEM",
"ZAF",
"ZMB",
"ZWE"
],
"road_class": [
"OTHER",
"MOTORWAY",
"TRUNK",
"PRIMARY",
"SECONDARY",
"TERTIARY",
"RESIDENTIAL",
"UNCLASSIFIED",
"SERVICE",
"ROAD",
"TRACK",
"BRIDLEWAY",
"STEPS",
"CYCLEWAY",
"PATH",
"LIVING_STREET",
"FOOTWAY",
"PEDESTRIAN",
"PLATFORM",
"CORRIDOR",
"CONSTRUCTION",
"BUSWAY"
],
"foot_road_access": [
"MISSING",
"YES",
"DESIGNATED",
"DESTINATION",
"PRIVATE",
"USE_SIDEPATH",
"NO"
],
"foot_average_speed": [
">number",
"<number"
],
"average_slope": [
">number",
"<number"
],
"road_environment": [
"OTHER",
"ROAD",
"FERRY",
"TUNNEL",
"BRIDGE",
"FORD"
],
"roundabout": [
"true",
"false"
],
"road_class_link": [
"true",
"false"
],
"max_speed": [
">number",
"<number"
],
"ferry_speed": [
">number",
"<number"
],
"foot_network": [
"MISSING",
"INTERNATIONAL",
"NATIONAL",
"REGIONAL",
"LOCAL",
"OTHER"
],
"car_subnetwork": [
"true",
"false"
],
"foot_subnetwork": [
"true",
"false"
]
},
"import_date": "2025-10-07T21:31:09Z",
"data_date": "2025-10-02T20:21:17Z"
}
- If you prefer to look directly in the code, you can check the parsers here:
parses. That’s where you’ll find things like road_class, surface, foot_network, and other road attributes used by each profile.
Feel free to add or correct anything if I missed some details.