-
Notifications
You must be signed in to change notification settings - Fork 15
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
propertys not implemented #7
Comments
Also noticed that there is no corresponding property for the "timepoint" field of stop_times. |
Adding this here because it's a similar issue, gtfs:arrivalTime and gtfs:departureTime should specify range as XSD:time |
@diarmuidr3d the range is xsd:duration... Not sure why we didn't add this in the spec yet indeed. Willing to do a pull request? |
Sure thing, I'll do that shortly. |
And also because it's defined as time from midnight, which returns counter-intuitive results for days where the was an hour more or less due to daylight saving time, so xsd:time would not work |
Add range for arrivalTime and departureTime for #7
While going through the spec there for a seperate project I noticed that it lists gtfs:routeUrl as the predicate for specifying the route_url property from routes.csv.
However this predicate doesn't appear to be specified in the ontology at http://vocab.gtfs.org/terms#
The text was updated successfully, but these errors were encountered: