You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: stoecker [Submitted to the original trac issue database at 10.55am, Monday, 28th December 2009]
The changeset information request should add information about contained elements as well as free space additional to the "open" argument. See also [http://josm.openstreetmap.de/ticket/4215].
P.S. Please also remember we still need a way to retrieve "deleted objects in a given bounding box".
The text was updated successfully, but these errors were encountered:
Author: guggis [Added to the original trac issue at 5.36pm, Monday, 28th December 2009]
Priorities are as follows:
Prio 1 - include an attribute size="" in the <changeset ...> element. The value is the number of objects currently assigned to the changeset.
Prio 2 (less important) - include an attribute free="" in the <changeset ...> element. The value is the number of objects which can still be uploaded to the changeset provided the changeset is still open. The following invariants hold:
open="false" => free="0"
open="true" => free="xyz" where xyz > 0
free is less important because it is given by the size limit for changesets in the API capabilities and the attribute size
Reporter: stoecker
[Submitted to the original trac issue database at 10.55am, Monday, 28th December 2009]
The changeset information request should add information about contained elements as well as free space additional to the "open" argument. See also [http://josm.openstreetmap.de/ticket/4215].
P.S. Please also remember we still need a way to retrieve "deleted objects in a given bounding box".
The text was updated successfully, but these errors were encountered: