[Strategic] Featured routing services

[Frederik Ramm]

Eugene,

On 03/04/11 09:43, Eugene Usvitsky wrote:
> I believe we should discuss 2 different questions:
> - which service should be used for website
> - which service should be used for internal data quality checks?

Maybe the first question to discuss is whether routing is desired at all.

> My documents give answer only to the first question. In my opinion,
> MapQuest routing engine is the most feature-rich among all commercial
> and non-commercial. We can't (or better shouldn't) use several routing
> engines for website because it will confuse its users, so our choice
> is MapQuest API.

Personally I would not use an external routing service on our web site. 
If someone wants to use MapQuest's routing engine, then why not go to 
open.mapquest.com where it is readily available?

> Currently I am interested in something
> different - do we really need routing for data quality? As far as I
> understand, routing can check 2 things:

OSM thrives on the "unexpected" uses people find for our data. It will 
be the same with a routing engine that can be used for quality checking 
- people would not be limited to the two things that you can currently 
think of; people would find their own uses.

Bye
Frederik