Modify

Opened 8 years ago

Last modified 8 years ago

#4215 new enhancement

Changeset object counter

Reported by: Ldp Owned by: team
Priority: normal Milestone:
Component: Core Version:
Keywords: Cc:

Description

Assuming that changesets are usually opened, processed, and closed from within only 1 running JOSM version at the same time, it would make sense to add a counter to tell how many objects were already uploaded, and how many can still fit until hitting the limit.

Uploading more objects than the changeset can hold could result in a user warning before the upload starts, or when in chunked mode, could offer to open a new changeset with the same tags, once the changeset limit is approached or hit.

I understand that fetching the changeset object counter when scanning for open changesets may be harder, but if that is still doable without causing too much API load, that would also be excellent.

A user juggling the same changeset between multiple JOSM versions is already in Here Be Dragons-mode, so the counter being wrong there won't matter that much.

Attachments (0)

Change History (5)

comment:1 Changed 8 years ago by Gubaer

or when in chunked mode, could offer to open a new changeset with the same tags, once
the changeset limit is approached or hit.

That's what JOSM already does when an upload hits the size limit, see online help.

I understand that fetching the changeset object counter when scanning for open changesets
may be harder, but if that is still doable without causing too much API load, that would also
be excellent.

It is possible but for large changesets (changesets close to the size limit) it's not reasonable because we have to fetch the complete changeset content in order to count the objects on the client side. I'd rather like the OSM server to include a "size" property in the changeset properties. When we read a changeset the server replies a property "open" which indicates whether the changeset is still open. It would be nice if it also replied a property "size" with the current size of the changeset content.

comment:2 Changed 8 years ago by stoecker

The current "free size" should also be included as very likely this may change. This should be added as entry in OSM Trac.

comment:3 Changed 8 years ago by Ldp

Having a "free size" sounds like a good thing to have, as that would neatly account for uploads done in the changeset from outside JOSM.

comment:4 Changed 8 years ago by stoecker

See #o2582.

comment:5 Changed 8 years ago by Gubaer

We don't need a "free size". Its given by maxsize - actual size and maxsize is a API specific constant replied in the capabilities.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to Ldp
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.