Documentation error: "GET GET GetRouteShape," no guidance on how to use it.

There are several function listings with a double "GET" at the front and zero information on arguments. I do not know how to use the "GetRouteShape" call, for example. I assume "GetRouteShape" is the call which returns the complete geometry of a route, which is what I'm looking for. But again, there is no documentation for this function, and no descriptions for any of the parameters in any function.

Comments

  •  
    Sorry for confusion. This method is going to be deprecated soon, I suggest to use FullRouteInfo instead
    Posted by Hidden Wed, 03 Oct 2018 18:30:34 GMT
  •  
    Thank you! FullRouteInfo is exactly what I was looking for.
    Posted by Hidden Thu, 04 Oct 2018 07:17:15 GMT
  •  
    Actually, I still wonder if there is documentation for the returned information. Is RouteColor a hex RGB string? (Which makes 002 a blue route!?) Do DirectionVariants number more than one, and if so, when? What is ServiceDate, exactly, and is there any way to find the last time the route was changed? The API's schema is here but not the docs. I've gleaned that it's based on CommuterAPI or TransitIQ or something, but they don't seem to offer any docs of any kind.
    Posted by Hidden Fri, 05 Oct 2018 14:17:02 GMT
  •  
    While full documentation is not here for this service, I can answer some questions "Is RouteColor a hex RGB string?" - Yes "Do DirectionVariants number more than one" - not sure what is asked. It is not uncommon for the route to have 1,2, even 4 directions "What is ServiceDate, exactly" - shedule information may be different for different dates, for example holidays vs weekend vs weekdays. Thats why everything is date-specific. If you need realtime info, supply todays date "is there any way to find the last time the route was changed?" - if "changed" means when Houston Metro changed schedule for this route, no.
    Posted by Hidden Thu, 11 Oct 2018 20:09:45 GMT
  •  
    Okay, that clears some things up. I see that DirectionVariants is more varied than I thought, and I haven't visualized them yet, so I'm uncertain whether they represent connecting legs of a route or different legs under different circumstances, but that's a minor problem. What seems to be a stumbling block in rendering these routes is that RouteColor does not correspond to frequency like color normally does on a system map -- all local buses and park & rides have RouteCOlor "004080" for me, and there is nothing I see to indicate frequency anywhere else. I have to scrape the schdeules themselves to determine frequency? On the CoH GIS site (which has data claiming to be no newer than from 2015), it included a standard route color name matching how the Metro maps render them.
    Posted by Hidden Fri, 26 Oct 2018 10:02:59 GMT
  •  
    While I do not represent county or Houston Metro, this is the color information we're getting from them. Alternatively, you can grab their GTFS file and see if you can extract better information from there. It is not a difficult format, just a bunch of comma-delimited files
    Posted by Hidden Fri, 26 Oct 2018 15:36:10 GMT


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