Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[sumo-user] TripInfo Output: Missing Attributes

Hello,


I've been looking at the tripinfo-output results data when using the multi-stage person specification  and there is an inconsistency in the reporting of "walk" and "ride".


In the generated data the "ride" output has "depart", "arrival" and "arrivalPos" but the "walk" output only contains "arrival" and "arrivalPos", see picture provided.

This means that calculating the duration of the "walk" requires the previous line of data, which is an additional headache when parsing.

It would be useful if the "walk" could have the "depart" attribute included as well to simplify processing and for consistency.


An additional point is that the "stop" lines don't include the "actType", which have been specified in the person routing file. The stops specification wiki page (http://sumo.dlr.de/wiki/Specification#Stops) says that this attribute is "displayed for stopped person in GUI and output files (only applies to person simulation)".

It would again be really useful if this attribute was included in the output, so that there isn't a need to refer back to the original routing plan.


Apologies if I've missed that there are configuration parameters for this information to be output.


Thanks,


Greg



DISCLAIMER: This email is intended solely for the addressee. It may contain private and confidential information. If you are not the intended addressee, please take no action based on it nor show a copy to anyone. In this case, please reply to this email to highlight the error. Opinions and information in this email that do not relate to the official business of Nottingham Trent University shall be understood as neither given nor endorsed by the University. Nottingham Trent University has taken steps to ensure that this email and any attachments are virus-free, but we do advise that the recipient should check that the email and its attachments are actually virus free. This is in keeping with good computing practice.

Back to the top