Some text updates to intro section #26
Conversation
|
|
|
|
||
| We hope to relax the limits on route distance as we improve performance on longer routes. The limit of number of locations will be increased shortly, stay tuned. | ||
| Send a message if you need higher limits in the meantime. |
There was a problem hiding this comment.
might want to reiterate where you want the message to be sent
There was a problem hiding this comment.
Thinking this should be an email, rather than a GitHub issue...will add the address here.
|
looks good |
|
Thanks @kevinkreiser (and @dnesbitt61 for the merge/shipit squirrel). Will look at these notes and the restrictions section (hadn't gotten through that part yet!). I took out some of the intro stuff and will put it elsewhere, too. Just wanted to get the limits updated. |
|
It would probably be nice to show an example of a simple request. I have this one saved for a route that avoids Canada by using the country_crossing_penalty: http://valhalla.api.dev.mapzen.com/route?json={"locations":[{"lat":42.358528,"lon":-83.271400,"street":"Appleton"},{"lat":42.996613,"lon":-78.749855,"street":"Ranch Trail"}],"costing": "auto","costing_options":{"auto":{"country_crossing_penalty":2000.0}},"directions_options":{"units":"miles"}}&api_key= |
|
Thanks, @kdiluca! There is a section on sample requests. I added this one (will need to be updated without the dev URL). Update: added this explanation for this particular route (commit 3): This request provides automobile routing between the Detroit, Michigan area and Buffalo, New York, with an optional street name parameter to improve navigation at the start and end points. It attempts to avoid routing north through Canada by adding a penalty for crossing international borders. The resulting route is displayed in miles. |
Moved unordered lists into tables, cleaned up text, added links to OSM tags, ordered costing options, added bicycle options. To do: get started, fix heading hierarchy, output section
Removed section on rate limitations per second/day (following discussion check in meeting), formatting of JSON output section
Added route return examples, removed compatibility mode, updated URLs, improved table cell alignment, added code formatting
|
OK, think this addresses all the "to do" items, as well as updated formatting and some rewrites. Take a look and see if these changes can be merged. Thanks! |
|
we dont currently support pbf output but it is planned. might want to also name this out_format to match the other parameter names. i would also favor the values without the '.' for this. anyway, this is sweet. SHIP SHIP SHIP |
indicating that pdf and sos are not yet supported.
|
|
Some text updates to intro section
Filled in the to do items on API key, bugs/issues, service limits from @kdiluca. (This is still in progress, just doing an initial check in.)