[Routing] Crowdsourced costing - offer of writing a client+metric for it

[Marcus Wolschon]

On Wed, 3 Dec 2008 12:42:31 +0100, Sascha Silbe
<sascha-ml-gis-osm-routing at silbe.org> wrote:
> On Wed, Dec 03, 2008 at 12:11:46PM +0100, Marcus Wolschon wrote:
> 
>> I tried to not make it to make my firt draft not too
>> fine-grained due to privacy and not-enough-data -concerns.
> 
>> We can have a * day =
>>
(weekday,weekend,holiday,beforeHoliday,afterHoliday,schoolVacation,beforeSchoolVacation,afterSchoolVacation)
>> ** weekday (mo,...sa,so)
> That's better, though you still miss some cases (e.g. the christmas 
> shopping period). In addition, the user is required to enter more data, 
> making it more likely (s)he just doesn't bother enough to submit the 
> data.
> How about just making the (full) date field optional? Send it by 
> default, but give the user the choice of anonymizing the data.

I don`t think the xmas-perio matters that much apart
from the days right before and after the holidays.
(xmas, night before xmas and new-year)
I see privacy as a main-issue here, thus I don`t want
the user to have to trust the server at all. If it does
not need the exact timestamp, it will not get it in the
first place. 

>> The server need never hand out data of a single upload.
>> To be meaningfull it even needs to be averaged for many
>> users.
> To be useful to a single end-user, it needs to be aggregated some way, 
> yes. But there are many ways to aggregate the data, so tool developers 
> would want excerpts of the raw data as well.

To provide the aggregated data is exactly the service provided.
I`m not sure about this requirement to come up at all but we may
add additional query-types for them later as they come up.
No need to over-engeneer things.


>> I suggested soap because it is supported by many
>> systems, it is type-safe and trivial to check and
>> there is good tooling.
> Type-safety is certainly good to have. Though I'd rather like a format 
> that can be used for offline storage and exchange as well...

I`d more like to leave local storage of the answers up to the application.

Marcus