added include and exclude.

[gknisely]

@meghanhade Can you add a sentence or two for Mobility Explorer for the following section on how to obtain Onestop IDs?
@irees Can you add a sentence or two for Transitland for the following section on how to obtain Onestop IDs?

Thanks.

[irees]

<li>Transitland - The Transitland Datastore API can be used to directly query for stops, routes, and operators using a number of options. For example, filtering for only [subway routes](http://transit.land/api/v1/routes?vehicle_type=metro) or [bus routes](http://transit.land/api/v1/routes?vehicle_type=bus). Please see the [Transitland Datastore API documentation](https://transit.land/documentation/datastore/api-endpoints.html) for more details.</li>

[meghanhade]

<li>[Mobility Explorer](https://mapzen.com/mobility/explorer/) - Onestop IDs can be obtained by selecting a single route, stop, or operator by clicking on it on the map. For routes and operators, you may also select by choosing from the drop-down menu in the sidebar. The Onestop ID will then be provided in the sidebar, along with other detailed information about the route, stop or operator you have chosen. More information can be found in the [Mobility Explorer documentation](https://mapzen.com/documentation/mobility/explorer/overview/).</li>

[gknisely]

added updates from @irees and @meghanhade Thank you!

@rmglennon @drewda @dnesbitt61 please review.

[gknisely]

Added HOV costing

[drewda]

@gknisely This looks good. My one recommendation would be to link the first reference of "Onestop ID" to https://transit.land/documentation/onestop-id-scheme/ for background information.

[dnesbitt61]

[gknisely]

@drewda thanks and updated.

[gknisely]

This will get merged when the blog goes out.

[drewda]

@gknisely 👍

[rmglennon]

I've pushed some changes into this branch for include/exclude.

Summary:

• fixed merge conflict with master
• removed API keys section and replaced it with a link (to match the trend these days and make the topic less service-oriented)
• replaced sample queries with working links that use keyless access (to match the styling used in the Search docs). This partially resolves Add hyperlinks for API query examples (but without API key) #138.
• moved the sample include/exclude query and Onestop ID info into a new section (the table was cut off or required scrolling otherwise)
• spelled out HOV on first use
• added a sentence on include/exclude to Mobility Explorer isochrone topic...although I'd like to get a demo so I can better understand the behavior.

[rmglennon]

Preview links: https://precog.mapzen.com/mapzen/mapzen-docs-generator/rhonda/in-ex-transit/documentation/mobility/turn-by-turn/api-reference/

https://precog.mapzen.com/mapzen/mapzen-docs-generator/rhonda/in-ex-transit/documentation/mobility/explorer/isochrones/

Also, I think the isochrone docs is OK as is because it says you can use the Turn-by-Turn costing for multimodal without repeating the options again in that topic. Let me know if we do need to add something here:

https://mapzen.com/documentation/mobility/isochrone/api-reference/#costing-parameters

[gknisely]

Updates look good, but do you think the transition from the Transit costing options table to the "For example, this is a route favoring buses, but also this person walks at a slower speed (4.1km/h):" and back to the new Filter transit data section bouncing around too much? Maybe move the example below the new Filter transit data section. Idk not sure. @rmglennon what do you think?

[gknisely]

looks good

[rmglennon]

Thanks @gknisely. The table loses scroll ability in the table, so my other thought was a separate section with all transit examples. The links look good in GitHub-flavored markdown, but not on the formatted docs site (yet).

[rmglennon]

All right, I ended up using HTML and escape characters for the include/exclude example. I also grouped all the transit examples together.

And put in mapzen/documentation#242 to look into the link markdown parsing.

[gknisely]