[OSM-talk] Something Might be Broken

Andrew Ayre andy at britishideas.com
Sat Aug 1 01:08:22 BST 2009


Tom Hughes wrote:
> On 31/07/09 23:55, Andrew Ayre wrote:
> 
>> I think if the OSM API was improved so it could accept large changesets
>> faster then that would greatly help out the people who are trying to add
>> large amounts of data. So far I haven't see a fast and reliable method.
> 
> Excuse me a minute while I find my magic wand...
> 
> [ time passes ]
> 
> ...found it! <fx: waves wand> There you go, changeset processing is now 
> 100 times faster.
> 
>> Perhaps people can apply for access to a second API for large changesets
>> only?
> 
> How exactly is that supposed to help? Will this API have access to some 
> magic accelerator technology that the current API doesn't use?

It would help because people could upload large data sets as fast as 
they can prepare them, then tweak any problems quickly and efficiently.

I was perhaps thinking of a dedicated machine/bandwidth for large 
uploads. But then I don't know what the bottleneck is in the current 
system. Is it users, bandwidth, processing power, something else or a 
combination?

A couple of weeks ago JOSM told me it would take 15 hours to upload a 
5Mb OSM file. It seems a bit better recently though.

Anyway, just throwing out ideas borne of frustration.

Andy

-- 
Andy
PGP Key ID: 0xDC1B5864




More information about the talk mailing list