Implement OpenJourneyPlanner(OJP) query and serialisation format

[t2gran]

Expected behavior

Able to interface with OpenJourneyPlanner clients.

Observed behavior

OpenTripPlanner OTP1 do not have support for OJP.

[t2gran]

This is on the Entur road map (Q4, 2019) - because it is required by the European Union to support this.

I think this is a perfect candidate for the sandbox model #2745.

[skinkie]

Would that imply to start a second webserver? Or is routing requests possible within the sandbox model?

[t2gran]

No need to start a second web server, just a (one or more) separate endpoint and the ability to turn it on/off.

@skinkie do you plan to work on this in the near feature? I think I can do the #2745 quite fast - need some help from @abyrd to merge in a couple of other PRs first.

[skinkie]

@t2gran I already created most of the Java parts a few months ago. So if you are ready in about 3-4 weeks I am happy to continue.

[t2gran]

@skinkie That sounds good, we can probably use the OJP as an example for the Sandbox - also this means that we do not need an approval from the PLC before we start. Formally the OJP is not approved by the PLC jet, but this let us test it out and if there are wide spread use we can move it into the core later.

[tuukka]

I would just remind to make it clear that the API is not officially supported by OTP at this point - but that would go for all sandbox features.

[drewda]

Is a concise overview of OpenJourneyPlanner inputs and outputs available online?

[abyrd]

Unfortunately in typical Netex style, I believe most of the documents are massive, exhaustive descriptions of an XML data model. @skinkie might have some short summary documents or examples of requests/responses to post.

[skinkie]

@drewda https://github.com/VDVde/OJP latest standard erata available by e-mail.

[abyrd]

@skinkie that looks like an exhaustive schema, which is good to have, but I suspect @drewda was just trying to get a high-level view of what the request/response looks like, and generally which features will be available via this API. Could you possibly just hit an existing OJP API and capture the request and response body to serve as an example?

[skinkie]

@abyrd I'll see what I can do from my initial prototype. The current live system that I run has implemented OJP in gRPC, hence no XML.

[abyrd]

Oh, that's interesting. Looks like gRPC would allow any payload format, including XML but also protobuf. So you're generating protobuf defintions from XSD?

[skinkie]

Generated it by hand. Still there are something in the standard that should receive a pragmatic review, independently on how things are arranged in for example SIRI.