Workaround: TripResponse stops without coordinates

[GerdC]

At least in the MENTZ implementation of TRIAS, stops and stopPoints in a TripResponse do not contain coordinates, so it is not possible to draw stopPoints on a map with the data in a TRIAS TripResponse.

Workaround:
TripResponse stopPoints contain an element StopPointRef

You can use the value of StopPointRef to create a LocationInformationRequest:

<?xml version="1.0" encoding="UTF-8"?>
<Trias version="1.1" xmlns="http://www.vdv.de/trias" xmlns:siri="http://www.siri.org.uk/siri">
    <ServiceRequest>
        <siri:RequestTimestamp>\(now)</siri:RequestTimestamp>
        <siri:RequestorRef>XXXXXXXXXXX</siri:RequestorRef>
        <RequestPayload>
            <LocationInformationRequest>
              <LocationRef>
                 <StopPointRef>\(stopPointRef)</StopPointRef>
              </LocationRef>
            </LocationInformationRequest>
        </RequestPayload>
    </ServiceRequest>
</Trias>

And ask the TRIAS server for the locationInformation of that stopPoint, which among other information, contains the coordinates.

This workaround is expensive and slow for client and server, but it works.

Is there another way to get the coordinates?
Probably yes:

TripResponse contains an AbstractResponseContextStructure (chapter 7.6.17. ) which can contain locations with the same information as returned by the LocationInformationRequest described above.

It is my understanding, that AbstractResponseContextStructure should contain Location information for each StopPointRef in a TripResponse. If my understanding is correct, it is a bug in the MENTZ EFA implementation of TRIAS not to fill the context element of a TripResponse.

Does the HAFAS implementation of TRIAS have the same problem?

[derhuerst]

Can we get someone from Mentz to fix this? Sounds like, technically, it should be a rather simple fix, right?