Guidance on Mapping Complex Mobility Service Data to Beckn Protocol

[amixpal]

I am currently working on developing an interoperable journey planner and booking platform that aims to offer comprehensive itineraries across multiple transport modes, including bus, train, walking, ride-hailing, and more. Our goal is to provide users with detailed, multi-leg itineraries (BPPs) that can seamlessly integrate various transport services into a single, coherent journey plan.

Our platform utilizes a specific API structure for search requests and responses to convey complex journey planning data, including multiple legs, transport modes, and relevant metadata for each leg of the journey. Below is an example of our current search API request structure:

{
    "from": {
        "name": "Amsterdam Airport Schiphol (AMS)",
        "coordinates": {
            "lng": 5.0974594,
            "lat": 52.0252597,
            "alt": 0
        }
    },
    "to": {
        "name": "Amsterdam Airport Schiphol (AMS)",
        "coordinates": {
           "lng": 4.4312561,
            "lat": 51.9514653,
            "alt": 0
        }
    },
    "nrOfTravelers": 1,
    "modeOfTransport": [],
    "departureTime": "2024-03-16T14:24:00.000Z",
    "showIntermediateStops": true 
}

Our Response structure (Currently Aligned with Tomp Standard and Open trip planner), which includes detailed options for multi-leg journeys, each leg potentially utilizing different transport modes, along with pricing, conditions, geometry, and other relevant data:

{
    "data": {
        "validUntil": "2024-03-13T00:15:37.339520008Z",
        "options": [
            {
                "id": "unique_option_id",
                "validUntil" : "2024-03-16T14:44:10Z",
                "from": {
                    "name": "Starting Point",
                    "coordinates": { "lng": 5.0974594, "lat": 52.0252597 }
                },
                "to": {
                    "name": "Destination Point",
                    "coordinates": { "lng": 4.4312561, "lat": 51.9514653 }
                },
                "legs": [
                  {
                        "id": "b43eafe6-a346-4a55-976d-effcf713f862",
                        "from": {
                            "name": "Amsterdam Airport Schiphol (AMS)",
                            "coordinates": {
                                "lng": 5.0974594,
                                "lat": 52.0252597
                            }
                        },
                        "to": {
                            "name": "Nieuwegein, Marconi (laag)",
                            "coordinates": {
                                "lng": 5.100284,
                                "lat": 52.027975
                            }
                        },
                        "departureTime": "2024-03-16T14:44:10Z",
                        "arrivalTime": "2024-03-16T14:55:00Z",
                        "assetType": {
                            "assetClass": "FOOT"
                        },
                        "conditions": [
                            {
                                "requiredFields": null
                            }
                        ],
                        "state": "NOT_BOOKABLE",
                        "distance": 707,
                        "legGeometry": {
                            "points": "{dp|Hqsb^A??uA?k@?c@Am@c@F[D[Hc@T_@R?@GD[VOPMJy@dAEB[b@e@z@Q`@Ur@HLFHFAFFDABEEKqAsDaBqEGHCAo@OKCGUz@{BXe@M[Bc@Bq@??",
                            "length": 42
                        },
                        "legGeometryColor": "2d83e5",
                        "co2": 0,
                        "calories": 45
                    }
                    /* Additional legs */
                ],
                /* Additional option-specific data */
            }
            /* Additional options */
        ]
    }
}

I am looking for recommendations on how to effectively map our search requests and responses to the Beckn protocol? Specifically, we're looking for advice on handling complex itineraries that include multiple legs and modes of transport, and how to structure this data within Beckn's framework.

[emmayank]

Hi @amixpal ,

Can we connect sometime on Monday (18th March'24), to discuss this further? I believe what you are trying to achieve can be done using the same mobility specification.

Thanks
@emmayank

[amixpal]

Sure! sent you a message