Modify

Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#9283 closed defect (invalid)

minimise "change area" bounding box so that local changes can be spotted easier

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

Description

currently some 50-90% of OSM changesets indicate an area that is so large that watching local changes is completely useless.

As an example, this http://www.openstreetmap.org/browse/changeset/18754395 innocent change somehow spans half the earth even though the changes are local to a few hundreds meters.

It would be very helpful if JOSM could upload the changeset with a meaningful bounding box.

Attachments (0)

Change History (2)

comment:1 by Don-vip, 11 years ago

Resolution: invalid
Status: newclosed

The bounding box is computed by the API, not by JOSM, see http://wiki.openstreetmap.org/wiki/API_v0.6#Bounding_box_computation.

Moreover, it is not an innocent changeset at all. If you try to download it:

http://api.openstreetmap.org/api/0.6/changeset/18754395/download

You will see data in Germany and North Africa... The bounding box is perfectly correct, even if it's probably an error from the uploader.

comment:2 by RicoZ, 11 years ago

you are right, I was relying on the OSM history viewer which makes it really easy to miss the African part of the edit.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.