For those interested in knowing what a "typical" bounding box size is,
check out my diary entry where I sample changesets over the last 8 years
and generate a heatmap of bounding box sizes over time.
https://www.openstreetmap.org/user/b-jazz/diary/393858
On Sun, Jun 14, 2020 at 3:21 AM wrote:
On Sat, 13 Jun 2020 21:36:37 +0100, Alan Mackie wrote:
>I have no problem with big bounding boxes that result from editing large
>objects. I get annoyed by the ones where somebody added twontiny houses on
>opposite sides of the world.
And those with a normal work method of editing random
> On Jun 13, 2020, at 3:42 AM, Simon Poole wrote:
>
> And all this because of a API defect (because there is just one bounding
> box per changeset instead of a list)?
This hints at a reasonable and not terribly difficult solution, which is for
the editor to (optionally and automatically)
I have no problem with big bounding boxes that result from editing large
objects. I get annoyed by the ones where somebody added twontiny houses on
opposite sides of the world.
On Sat, 13 Jun 2020, 20:40 Mark Wagner, wrote:
> On Sat, 13 Jun 2020 08:03:11 +0200
> Florian Lohoff wrote:
>
> > On
On Sat, 13 Jun 2020 08:03:11 +0200
Florian Lohoff wrote:
> On Fri, Jun 12, 2020 at 11:19:46AM -0400, James wrote:
> > No they shouldn't, mapping roads in northern Canada, your bbox can
> > become quite large quickly as mapping logging roads/dirt roads is
> > quick and easy, but span over
is it just rivers or would that included polygons, river banks, area ?
Saturday, June 13, 2020 11:44 AM -05:00 from Joseph Eisenberg
:
I mostly have mapped in parts of Indonesia where there was no data, and the new
road or river was mapped for the first time.
Usually I try to split roads
>i did that it was 10 feet than someone says it can not be 10 feet a mile or so
>down the road and he is right
>
>so i changed it but it was 10 feet where i was.
>
>>Saturday, June 13, 2020 11:44 AM -05:00 from Joseph Eisenberg <
>>joseph.eisenb...@gmail.com >:
>>
>>I mostly have mapped in
I mostly have mapped in parts of Indonesia where there was no data, and the
new road or river was mapped for the first time.
Usually I try to split roads and rivers every ~10 kilometers.
- Joseph Eisenberg
On Sat, Jun 13, 2020 at 8:46 AM Mateusz Konieczny via talk <
talk@openstreetmap.org>
Jun 13, 2020, 08:03 by f...@zz.de:
> On Fri, Jun 12, 2020 at 11:19:46AM -0400, James wrote:
>
>> No they shouldn't, mapping roads in northern Canada, your bbox can become
>> quite large quickly as mapping logging roads/dirt roads is quick and easy,
>> but span over multiple kms
>>
>
> The
Splitting changesets does sound like a lot of work if you don't already
have for example the multi layer tools that JOSM has.
Would a warning that "you already have pending edits ___ km away, please
consider saving or discarding those before editing here" be useful in the
interim? I think this
I've advocated for this in the past, but getting this right from a
business logic pov is fairly tricky and is yet another thing that an
editor needs to keep track of when creating and modify geometries, and
changing tags. From the top my head at least: new object creation,
dragging nodes and
: Re: [OSM-talk] Could/should editors detect/disallow huge changeset
bboxes?
On Fri, 12 Jun 2020 at 16:45, Paul Johnson mailto:ba...@ursamundi.org> > wrote:
This isn't unique to JOSM, though. This is easily doable with iD as well (as
evidenced by watching OSMCha with a bbox
On Fri, Jun 12, 2020 at 11:19:46AM -0400, James wrote:
> No they shouldn't, mapping roads in northern Canada, your bbox can become
> quite large quickly as mapping logging roads/dirt roads is quick and easy,
> but span over multiple kms
The point is that the line/way of that road should also not
>I understand fred, how do you know the date of the satelite view, in pre-fab a
>building can go up
>
>in a day.
>>Friday, June 12, 2020 7:24 PM -05:00 from Dave F via talk <
>>talk@openstreetmap.org >:
>>
>>On 12/06/2020 15:32, 80hnhtv4agou--- via talk wrote:
>>> I am confused,
>>> are you
On 12/06/2020 15:32, 80hnhtv4agou--- via talk wrote:
I am confused,
are you telling me being in chicago, where i can go to the place i am
editing, not relying on satellite view
which is behind by at least 7 month or more here, i should be messing
around in London.
If you have information
On 12/06/2020 23:00, 80hnhtv4agou--- via talk wrote:
Friday, June 12, 2020 10:20 AM -05:00 from James
:
No they shouldn't, mapping roads in northern Canada, your bbox can
become quite large quickly as mapping logging roads/dirt roads is
quick and easy, but span over
On 12/6/20 9:19 pm, Colin Smale wrote:
On 2020-06-12 13:00, Frederik Ramm wrote:
Hi,
I wonder if it would be feasible or desirable for editors to warn users
if they are at risk of creating country/world-spanning changesets.
Something like "you have unsaved edits more than 500km away from
>Friday, June 12, 2020 10:20 AM -05:00 from James :
>
>No they shouldn't, mapping roads in northern Canada, your bbox can become
>quite large quickly as mapping logging roads/dirt roads is quick and easy, but
>span over multiple kms
If the satellite view ( imagery) in my local area is 7
On Fri, 12 Jun 2020 at 18:27, Mateusz Konieczny via talk <
talk@openstreetmap.org> wrote:
>
>
>
> Jun 12, 2020, 18:26 by aamac...@gmail.com:
>
> There have been requests for iD to warn users if they have unsaved edits
> far away before they start editing a new area, but so far these issues have
>
Jun 12, 2020, 18:26 by aamac...@gmail.com:
> There have been requests for iD to warn users if they have unsaved edits far
> away before they start editing a new area, but so far these issues have been
> closed once it is mentioned that other software also does this on occasion.
> See for
On Fri, 12 Jun 2020 at 16:45, Paul Johnson wrote:
>
>
> This isn't unique to JOSM, though. This is *easily* doable with iD as
> well (as evidenced by watching OSMCha with a bbox edged on Oklahoma's
> maximum extents, Amazon Logistics does this a good 3-4 times a day every
> day with changesets
On Fri, Jun 12, 2020 at 10:31 AM Florian Lohoff wrote:
> On Fri, Jun 12, 2020 at 03:45:17PM +0200, Frederik Ramm wrote:
> > Hi,
> >
> > On 12.06.20 15:22, Dave F via talk wrote:
> > > There is a lot of negativity about large changsets, but assessment of
> > > them should be based on quality, not
On Fri, Jun 12, 2020 at 03:45:17PM +0200, Frederik Ramm wrote:
> Hi,
>
> On 12.06.20 15:22, Dave F via talk wrote:
> > There is a lot of negativity about large changsets, but assessment of
> > them should be based on quality, not quantity.
>
> Yes, we're not discussing a popup that says "You
On Fri, Jun 12, 2020 at 02:14:15PM +0200, Mateusz Konieczny via talk wrote:
>
>
>
> Jun 12, 2020, 13:59 by f...@zz.de:
>
> > Changeset envelopes which span more than 100s of km² are broken.
> >
> Except cases where you edit/delete already created huge objects or you create
> huge object that
No they shouldn't, mapping roads in northern Canada, your bbox can become
quite large quickly as mapping logging roads/dirt roads is quick and easy,
but span over multiple kms
On Fri., Jun. 12, 2020, 11:10 a.m. ndrw, wrote:
> On 12/06/2020 15:32, 80hnhtv4agou--- via talk wrote:
> > I am
On 12/06/2020 13:35, Tobias Knerr wrote:
On 12.06.20 13:00, Frederik Ramm wrote:
I wonder if it would be feasible or desirable for editors to warn users
if they are at risk of creating country/world-spanning changesets.
It would certainly be a improvement for day-to-day work.
The root of the
On 12/06/2020 15:32, 80hnhtv4agou--- via talk wrote:
I am confused,
are you telling me being in chicago, where i can go to the place i am
editing, not relying on satellite view
which is behind by at least 7 month or more here, i should be messing
around in London.
Yes, you can map anywhere
I am confused,
are you telling me being in chicago, where i can go to the place i am editing,
not relying on satellite view
which is behind by at least 7 month or more here, i should be messing around in
London.
>Friday, June 12, 2020 9:26 AM -05:00 from Dave F via talk
>:
>
>On
On 12/06/2020 14:44, Frederik Ramm wrote:
Hi,
On 12.06.20 15:22, Dave F via talk wrote:
There is a lot of negativity about large changsets, but assessment of
them should be based on quality, not quantity.
Yes, we're not discussing a popup that says "You dumbass, why did you
create a
On Fri, Jun 12, 2020 at 6:07 AM Frederik Ramm wrote:
> I wonder if it would be feasible or desirable for editors to warn users
> if they are at risk of creating country/world-spanning changesets.
> Something like "you have unsaved edits more than 500km away from where
> you are editing at the
Yes please - I am using Osmcha to look at changesets around me and i
have a high number of changesets which span half Europe and thus
intersect with the area i am looking at.
Changeset envelopes which span more than 100s of km² are broken.
In which case, isn't it really OSMCha which is
Hi,
On 12.06.20 15:22, Dave F via talk wrote:
> There is a lot of negativity about large changsets, but assessment of
> them should be based on quality, not quantity.
Yes, we're not discussing a popup that says "You dumbass, why did you
create a world-spanning changeset?" ;)
The way in which
> Yes please - I am using Osmcha to look at changesets around me and i
have a high number of changesets which span half Europe and thus
intersect with the area i am looking at.
Side note to this discussion — in OSMCha you can filter out these wide spanning
changesets with “Bbox size bound”
On 12/06/2020 12:00, Frederik Ramm wrote:
and very rarely intentional.
Point 1:
This is what's always confused me. I occasionally look into world wide
changeset & it's often one spurious object in another continent, which
the contributor can't explain.
I'm unsure if it's one specific
Le 12 juin 2020 14:14:15 GMT+02:00, Mateusz Konieczny via talk
a écrit :
>
>
>
>Jun 12, 2020, 13:59 by f...@zz.de:
>
>> Changeset envelopes which span more than 100s of km² are broken.
>>
>Except cases where you edit/delete already created huge objects or you
>create
>huge object that actually
On 12.06.20 13:00, Frederik Ramm wrote:
> I wonder if it would be feasible or desirable for editors to warn users
> if they are at risk of creating country/world-spanning changesets.
It would certainly be a improvement for day-to-day work.
The root of the issue, though, is that bounding boxes
Le 12.06.20 à 13:00, Frederik Ramm a écrit :
> desirable
imho yes, including offline editor like maps.me,
when a contributor edit one object at the airport
of departure and another at the airport of arrival,
both in the same changeset.
___
talk mailing
Jun 12, 2020, 13:59 by f...@zz.de:
> Changeset envelopes which span more than 100s of km² are broken.
>
Except cases where you edit/delete already created huge objects or you create
huge object that actually should be created.
___
talk mailing list
Hi,
showing a warning for huge bboxes is a great idea. I can also imagine to
extends this idea to the number of changes. So also showing a warning
when there are more than a specific amount of added/changed/deleted
nodes or something.
I had the situation that I accidentally uploaded a huge bunch
On Fri, Jun 12, 2020 at 01:00:56PM +0200, Frederik Ramm wrote:
> Hi,
>
> I wonder if it would be feasible or desirable for editors to warn users
> if they are at risk of creating country/world-spanning changesets.
> Something like "you have unsaved edits more than 500km away from where
> you are
Jun 12, 2020, 13:00 by frede...@remote.org:
> Hi,
>
> I wonder if it would be feasible or desirable for editors to warn users
> if they are at risk of creating country/world-spanning changesets.
> Something like "you have unsaved edits more than 500km away from where
> you are editing at the
On 2020-06-12 13:00, Frederik Ramm wrote:
> Hi,
>
> I wonder if it would be feasible or desirable for editors to warn users
> if they are at risk of creating country/world-spanning changesets.
> Something like "you have unsaved edits more than 500km away from where
> you are editing at the
Hi,
I wonder if it would be feasible or desirable for editors to warn users
if they are at risk of creating country/world-spanning changesets.
Something like "you have unsaved edits more than 500km away from where
you are editing at the moment, please upload those before you continue"
or so.
43 matches
Mail list logo
