We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The following components are currently hardcoded to imperial units through call to humanizeDistanceString() and should support output to metric units:
humanizeDistanceString()
AccessLegSummary
itinerary-body
AccessLeg
printable-itinerary
TransitStopOption
location-field
EDIT: Other components may still have to be modified to support metric application-wide, and they will have to be covered under separate issues.
The text was updated successfully, but these errors were encountered:
fix: opentripplanner#116 Add outputMetricUnits to config types and us…
7d2d02d
…e in itinerary-body
*WIP* fix: opentripplanner#116 Add new story and flag outputMetricUni…
c389bed
…ts to location-field
No branches or pull requests
The following components are currently hardcoded to imperial units through call to
humanizeDistanceString()
and should support output to metric units:AccessLegSummary
(packageitinerary-body
)AccessLeg
(packageprintable-itinerary
)TransitStopOption
(packagelocation-field
)EDIT: Other components may still have to be modified to support metric application-wide, and they will have to be covered under separate issues.
The text was updated successfully, but these errors were encountered: