Issues

  • Customer Service Locations Data Incorrect

    Hello there, I notice that the https://api.at.govt.nz/v2/locations/customerservicecentres api always returns identical latitude and longitude, which is not correct. I believe the longitude data is wrong.

    Status: Proposed | Reported by Hidden Thu, 24 Nov 2016 08:42:48 GMT
  • No Documentation About Real-Time Agency Coverate

    Which agencies in the GTFS file are included in the tripupdates and vehiclelocations?

    Status: Proposed | Reported by Hidden Fri, 07 Oct 2016 13:21:47 GMT
  • GTFS Schedules Do Not Match Printed Publications

    Routes are not listed as they appear in other publications. Separate routes appear in the GTFS data to denote route directions.

    Status: Proposed | Reported by Hidden Fri, 07 Oct 2016 13:19:42 GMT
  • Static Data Doesn't Support Tracking Route Schedules

    The static GTFS file doesn't support tracking route schedules because the route_id changes.

    Status: Proposed | Reported by Hidden Fri, 07 Oct 2016 13:17:56 GMT
  • 500 Internal server error when using protobuf with realtime api

    When adding the header "Accept: application/x-protobuf" to the https://api.at.govt.nz/v2/public/servicealerts api, the server returns a 500 internal server error. Without the header a non-protobuf response is returned okay.

    Status: Proposed | Reported by Hidden Fri, 07 Oct 2016 13:15:51 GMT
  • Call to "Points Of Interest" (https://api.at.govt.nz/v2/public/display/poi) gives error

    Calling the service gives the following error { "status": "Error", "response": null, "error": { "name": "Error", "message": "wrong status code returned from ESRI: 500" } }

    Status: Proposed | Reported by Hidden Thu, 29 Sep 2016 22:23:26 GMT
  • Minor issue with scheduled works

    The Scheduled Works service call https://api.at.govt.nz/v2/public/display/scheduledworks returns - array of array of numeric for polygon - array of numeric for point but it returns - array of array of string for line It should be array of array of numeric for consistency

    Status: Open | Reported by Hidden Thu, 29 Sep 2016 20:31:32 GMT
  • Trip Updates Protobuf format invalid

    When parsing the protobuf data for Trip Updates, any negative arrival or departure delays are showing up as invalid timestamps (e.g., 4294967225). I've tested the same code on other GTFS TripUpdate feeds (protobuf) and they work fine.

    Status: Proposed | Reported by Hidden Mon, 19 Sep 2016 02:39:59 GMT
  • Get Trip List API is blocked

    We can not get trip list data now, it always return null, could you guys please check it?

    Status: Proposed | Reported by Hidden Wed, 07 Sep 2016 21:14:56 GMT
  • Geocode forward is restricted

    It is listed in the API documentation, but is unable to be used with a normal developers key. Error message: Access denied due to invalid subscription key. Make sure to provide a valid key for an active subscription.

    Status: Proposed | Reported by Hidden Sat, 03 Sep 2016 11:12:47 GMT

You're not signed in. Please sign-in to report an issue or post a comment.