Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LocationInformationRequest for quay returns corresponding stopPlace, not quay #18

Open
GerdC opened this issue Dec 6, 2024 · 0 comments

Comments

@GerdC
Copy link

GerdC commented Dec 6, 2024

I'd like to get coordinates of quay de:08111:6160:1:2 to draw it on a map.

I sent the following request to the TRIAS server

<?xml version="1.0" encoding="UTF-8"?>
    <Trias version="1.2" xmlns="http://www.vdv.de/trias" xmlns:siri="http://www.siri.org.uk/siri">
        <ServiceRequest>
            <siri:RequestTimestamp>2024-11-27T12:00:00</siri:RequestTimestamp>
            <siri:RequestorRef>XXX</siri:RequestorRef>
            <RequestPayload>
                <LocationInformationRequest>
                  <LocationRef>
                     <StopPointRef>de:08111:6160:1:2</StopPointRef>
                  </LocationRef>
                </LocationInformationRequest>
            </RequestPayload>
        </ServiceRequest>
    </Trias>

The TRIAS server responds with

<?xml version="1.0" encoding="UTF-8"?>
<trias:Trias
	xmlns:siri="http://www.siri.org.uk/siri"
	xmlns:trias="http://www.vdv.de/trias"
	xmlns:acsb="http://www.ifopt.org.uk/acsb"
	xmlns:ifopt="http://www.ifopt.org.uk/ifopt"
	xmlns:datex2="http://datex2.eu/schema/1_0/1_0" version="1.2">
	<trias:ServiceDelivery>
		<siri:ResponseTimestamp>2024-12-06T20:30:15Z</siri:ResponseTimestamp>
		<siri:ProducerRef>de:nvbw</siri:ProducerRef>
		<siri:Status>true</siri:Status>
		<trias:Language>de</trias:Language>
		<trias:CalcTime>77</trias:CalcTime>
		<trias:DeliveryPayload>
			<trias:LocationInformationResponse>
				<trias:LocationResult>
					<trias:Location>
						<trias:StopPoint>
							<trias:StopPointRef>de:08111:6160</trias:StopPointRef>
							<trias:StopPointName>
								<trias:Text>Bopser</trias:Text>
								<trias:Language>de</trias:Language>
							</trias:StopPointName>
							<trias:LocalityRef>8111000:51</trias:LocalityRef>
						</trias:StopPoint>
						<trias:LocationName>
							<trias:Text>Stuttgart</trias:Text>
							<trias:Language>de</trias:Language>
						</trias:LocationName>
						<trias:GeoPosition>
							<trias:Longitude>9.18369</trias:Longitude>
							<trias:Latitude>48.76794</trias:Latitude>
						</trias:GeoPosition>
					</trias:Location>
					<trias:Complete>true</trias:Complete>
					<trias:Probability>1</trias:Probability>
				</trias:LocationResult>
			</trias:LocationInformationResponse>
		</trias:DeliveryPayload>
	</trias:ServiceDelivery>
</trias:Trias>

Which is the corresponding stopPlace de:08111:6160 with the stopPlace coordinate, not the quay.

Also layers are returned as stopPlaces.

For simple bus stops or tram stations, this is often on the wrong side of the street/track, for more complex stop places with trains and busses, the coordinate is completely off.

Is this my fault, can I send a better request, or is this a bug in the MENTZ implementation of TRIAS, or is this intended by the VDV standard?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant