[OSM-dev] Server Timeouts - JOSM and the forthcoming biguploads via the API

[Tom Hughes]

In message <!&!AAAAAAAAAAAuAAAAAAAAAOKaD4mR3JBOrEpRon92nMgBANp/H2q5kHFIvKMsnZiQaZAAAAABxJAAABAAAABXIPf9Z5/qQr8V0/2tgnw3AQAAAAA=@blueyonder.co.uk>
        Andy Robinson <Andy_J_Robinson at blueyonder.co.uk> wrote:

> Tom Hughes wrote:
>
> > I was talking to one of the Dutch guys about the AND data at the AGM and
> > they would like to load the data directly on the server rather than doing
> > it with API calls.
> >
> > That seemed sensible to me - my only preference was that it be done
> > through the rails object model rather than via direct SQL queries.
> >
> > Maybe what we need is a ruby program to load an OSM file and insert
> > it into the database via the rails object model?
>
> Sounds logical although if we want to allow general OSM users to upload
> TIGER data themselves it would need a simple interface, so presumably it
> would be logical to run it via a website form with the TIGER .osm files
> already sitting on the server ready for use?

Well I hadn't given any thought to that level of automation - for
the AND data I was assuming it would just be done by hand.

Perhaps an upload system like for GPX files, where a daemon then
processes the queued files would be a good idea?

Tom

-- 
Tom Hughes (tom at compton.nu)
http://www.compton.nu/