<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Well options 2 and 4 are absolutely not feasible, assuming you are<br>
talking about using the <a href="http://osm.org" target="_blank">osm.org</a> map query API. The OSM API is for<br>
editing the map only, not for clients to query for use in some 3rd<br>
party service. Of course some small non-editing related calls get<br>
through but if you start querying a lot of data you will get blocked<br>
pretty quickly. For non edit related querying there are other services<br>
like jxapi or overpass. But even then, this does not sound like the<br>
best idea.<br></blockquote><div><br>Yeah, I was considering using an
XAPI interface, but honestly I didn't realize that was the only way
allowable... I was just leaning that way because of the larger area
coverage allowed on a request. But yeah I agree neither of these ideas
are ideal.<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The specific example you linked to does seem very odd. It does look<br>
like the MapQuest Open routing service behaves correctly thought:<br>
<a href="http://mapq.st/1067Po9" target="_blank">http://mapq.st/1067Po9</a><br></blockquote><div><br>Good
find. I had skipped over mapquest open earlier for some reason, and
you're right it does work on that one. However I found some other route
attempts that would not work on mapquest but WOULD work on YOURS. How
confusing. See image here if you're curious.<br><a href="http://i.imgur.com/Rv0UNpa.jpg">http://i.imgur.com/Rv0UNpa.jpg</a><br>Both attempts in that image work on BRouter, but it doesn't have a public API, and it is really weird about starting the route far ahead of (or behind) the actual point you give it (though at least still on the same path).<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Looking on a couple of other routing services, the OSRM demo is set<br>
for cars only so it won't even try to go on the highway=path. No clue<br>
where the cloudmade router's head is. It will obviously use<br>
highway=path but for some reason it is refusing to transition to it<br>
right there. I can't figure out why either.<br></blockquote><div><br>Thanks
for your input anyway. I have the mapquest one working in my app
already... was very easy to set up. Just doesn't work for half the
routes I want it to. Considering having my application make both a
mapquest open AND a YOURS request, and then internally judge which one
is better and present that to the user.<br></div></div>