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

propertys not implemented #7

Open
diarmuidr3d opened this issue Dec 2, 2015 · 5 comments
Open

propertys not implemented #7

diarmuidr3d opened this issue Dec 2, 2015 · 5 comments

Comments

@diarmuidr3d
Copy link
Contributor

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#

@diarmuidr3d diarmuidr3d changed the title gtfs:routeUrl not implemented propertys not implemented Dec 3, 2015
@diarmuidr3d
Copy link
Contributor Author

Also noticed that there is no corresponding property for the "timepoint" field of stop_times.

@diarmuidr3d
Copy link
Contributor Author

Adding this here because it's a similar issue, gtfs:arrivalTime and gtfs:departureTime should specify range as XSD:time

@pietercolpaert
Copy link
Member

@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?

@diarmuidr3d
Copy link
Contributor Author

Sure thing, I'll do that shortly.
Why do you use xsd:duration, is it because the GTFS time may go over 24 h? Would xsd:time not work anyway?

diarmuidr3d added a commit to diarmuidr3d/linked-gtfs that referenced this issue Jan 19, 2016
@pietercolpaert
Copy link
Member

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

pietercolpaert pushed a commit that referenced this issue Jan 19, 2016
Add range for arrivalTime and departureTime for #7
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

2 participants