[OSM-talk] Is OSM Mapper ready for 0.6? (was Re: DisablePotlatch finally)
d at tucny.com
Thu Dec 18 09:33:26 GMT 2008
2008/12/18 Shaun McDonald <shaun at shaunmcdonald.me.uk>
> On 18 Dec 2008, at 08:56, maning sambale wrote:
> > In short:
> > Mappers need not worry about changing mapping habits. Editing is the
> > way it is (unlike the transition from API 0.4 to 0.5!), you're just
> > encourage to explain your edit session via changeset comments
> > This is what I usually do:
> > 1. Download a manageable chunk via OSMXAPI.
> Is the OSMXAPI ready to return version numbers? [For devs to answer]
> > 2. Edit via JOSM for a full 4-5 hours.
> > 3. Then upload via my dial-up (10 kbps) connection.
> > 4. Sleep.
> > What if someone edited a few ways? Does it invalidate my whole
> > changeset/edit session? Or just the modified node/way/relation?
> It will invalidate just the modified node/way/relation.
> With JOSM in 0.6 there will be diff uploads, which means that all the
> changes are sent at one time. This does mean that the whole change
> will be rejected, if one node has been modified before you have
> uploaded. As the upload is done as a single request, less bandwidth
> hence time will be required. I don't know what the speedup is. The
> speedup is likely to depend on the network connection.
If the API specifies which particular objects in the change were a problem,
it would be good if JOSM gave the option of downloading just those objects
and performing conflict resolution rather than just failing... Not got a
clue how hard that would be to implement though...
The speedup will be pretty sizable for high latency links such as many of
those in asia when transfering more than a few modification... I'd guess
Maning being on a dialup link in asia will probably see a pretty decent
speed up as compression should take care of most of the size of the change
and being sent in one go should remove most of the time taken in
establishing new connections...
With an rtt of 250ms, creating 100 nodes in 0.5 would take at least 750ms
per node or 75 seconds for the 100 nodes at one connection per node plus
transfer time... in 0.6 this should be reduced to 3 connections, so 2.25
seconds plus transfer time... I'd guess Maning's rtt is somewhat higher than
250ms though in which case he'd save even more, as I will with my best case
rtt of 320ms to the API...
Of course this assumes that JOSM isn't reusing connections, which I think is
true and it also assumes that I'm not making silly mistakes or missing
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the talk