@Craig, thank you for this new information. I will give this a try
regarding keeping a changeset open while uploading different parts and will
also teach novice mappers about this option. Though, like John Whelan I am
still skeptical about the added advantage of bigger changesets.
@mmd regarding yo
@Craig, thank you for this new information. I will give this a try
regarding keeping a changeset open while uploading different parts and will
also teach novice mappers about this option. Though, like John Whelan I am
still skeptical about the added advantage of bigger changesets.
@mmd regarding yo
On 2018-01-20 14:36, Gaurav Thapa wrote:
Yes, I am aware of these buttons. Do you mean that we do Ctrl+S
frequently in order to do partial saves? I feel this might allow for
greater chance for conflicts to occur rather than uploading frequently.
In JOSM, click on the Upload button. Then in the
> Yes, I am aware of these buttons. Do you mean that we do Ctrl+S
frequently in order to do partial saves? I feel this might allow for
greater chance for conflicts to occur rather than uploading frequently.
and that would be my view as well. I'm not sure I see the advantage of
bigger changesets.
Yes, I am aware of these buttons. Do you mean that we do Ctrl+S frequently
in order to do partial saves? I feel this might allow for greater chance
for conflicts to occur rather than uploading frequently.
On Sat, Jan 20, 2018 at 2:59 AM, althio wrote:
> Hi Gaurav,
>
> In the row of buttons, the
Hi Gaurav,
In the row of buttons, the first two are "Open" and "Save": these actions
are for files locally on your computer.
Third and fourth buttons are "Download" and "Upload", commonly used to
interact with OSM servers.
-- althio
On Jan 19, 2018 10:29 AM, "Gaurav Thapa" wrote:
>
> Hi Michael
Hi Michael,
Could you tell me what buttons are used in JOSM for partial saves? Here in
Nepal we frequently upload changes as internet is intermittent this feature
would be greatly beneficial for us all.
Regards,
Gaurav
On Fri, Jan 19, 2018 at 1:13 PM, Michael Collinson wrote:
> Hi Micah,
>
> I
Hi Micah,
I think you came up with a good answer to your conundrum in an earlier
post in this thread: Don't explain what an optimal changeset IS, explain
what it is NOT:
Something like:
"It helps other contributors understand your edits if you group what you
are doing in a local area into o
I looked for similar issues and apparently it was already discussed,
considered back and forth and modified in iD.
https://github.com/openstreetmap/iD/issues/703
https://github.com/openstreetmap/iD/issues/1598
https://github.com/openstreetmap/iD/issues/2251#issuecomment-180469055
I don't know the
This a purely an iD problem. It should be down to their core programmers
to sort it out.
We should be encouraging users, especially newbies, to save frequently.
Potlatch does this without the problem of numerous changesets.
DaveF
On 17/01/2018 13:26, Michał Brzozowski wrote:
Many new users hav
This is how StreetComplete does it. Good thing is that the OSM server
automatically closes changesets where nothing was added after one hour,
so one does not need to worry that a changeset gets "stuck" if the user
exits the application without closing the changeset.
On 17/01/2018 18:47, Rory McCan
On 17.01.2018 18:47, Rory McCann wrote:
> Users want to save/upload frequently (because computers), so we'll never
> stop them pressing the button often.
But we could give them more than one button.
There's "save", and then there's "upload/commit/publish". The two
actions are distinct, and part o
On Wed, 17 Jan 2018 14:51:38 +0100
Tobias Zwick wrote:
> So, what is the optimal changeset size, and why?
>
For a novice? One building, or a short stretch of road, or a small
park. They'll almost always make mistakes, and small changesets let
you suggest better ways of doing things without ov
On 17/01/18 15:13, Michał Brzozowski wrote:
Certainly not:
- one changeset per building, repeated 20 times
Couldn't this be done with the "upload" vs "new changeset" feature of
the OSM API? A technical solution. Multiple uploads in a single changeset?
Users want to save/upload frequently (beca
A lot of new mappers come through HOT and one problem I see is the same
building mapped twice. The HOT tile system releases the lock after two
hours on the tile. If mappers uploaded every fifteen minutes there would
be fewer double mappings.
An optimal change set size is difficult to define in s
: Imre Samu ; talk@openstreetmap.org
Subject: Re: [OSM-talk] How to teach novices about optimal changeset size?
Certainly I am not intending to change the community and require every mapper
to comply. If you're an experienced mapper, you're fine.
I mean new users, who are not yet integrate
Certainly I am not intending to change the community and require every
mapper to comply. If you're an experienced mapper, you're fine.
I mean new users, who are not yet integrated with the community. Their work
should be checked thoroughly (in Achavi, osmcha...). All novices make
mistakes, after a
> one changeset per building, repeated 20 times
my typical use case: House numbering on the street: push the numbers &
forget & go to the next house( fast feedback loop vs. Delayed
gratification )
- sometimes the mobil app is crashing, and I don't want to go back 100m to
re-enter - the la
Certainly not:
- one changeset per building, repeated 20 times
- one changeset for 3 POIs that are 1000 km apart in different countries
These are real world examples. In the latter Achavi can often refuse to run.
That's also why I asked ;-) It's not that easy to formulate the answer what
is reaso
So, what is the optimal changeset size, and why?
Tobias
On 17/01/2018 14:26, Michał Brzozowski wrote:
> Many new users have a habit of e.g. sending one or few objects per
> changeset, resulting in a dozen or even more changesets per day.
> Obviously this makes them PITA to review quickly in Achav
Many new users have a habit of e.g. sending one or few objects per
changeset, resulting in a dozen or even more changesets per day. Obviously
this makes them PITA to review quickly in Achavi or whatever tool you use.
This habit is probably caused by non-knowledge of how auto-save works in iD
(whic
21 matches
Mail list logo