Re: [HOT] Bounding box not in iD Editor anymore

[Rebecca Firth]

Hi All,

Re-kindling this thread as another mapper and myself appear to be
experiencing the bounding box issue again (in Safari and Chrome) across a
few different tasks.

Re-pasting the workaround instructions from before for anyone mapping
presently:


   1. Load task in iD
   2. Return to Task on TM, go back to 'edit with' and select JOSM
   3. You will get an error message about JOSM remote control, but it will
   give you access to a section of the JOSM menu
   4. From the section that reads "*Tip: Download the following .gpx file
    and load it in JOSM in
   order to see the current task boundary" *right click on *".gpx file" *and
   select *"Save link as" -* I put mine in my downloads folder.
   5. Back to the iD *tab in your browser, and have file manager open as
   well - drag & drop the downloaded .gpx file onto the window of ID -- then
   wait...*
   6. If all goes well you now have the square on your iD screen.* It took
   a while to load on my setup & a message about waiting or closing appeared -
   but it has loaded each time I've tried. *

Thanks,

Rebecca

On Mon, Feb 6, 2017 at 9:06 AM, Blake Girardot HOT/OSM <
blake.girar...@hotosm.org> wrote:

> Hi Nick!
>
> Your work around is great and working for people! Thank you very much!
>
> Pierre Giraud, just put a hotfix on the Tasking Manager to make your
> solution easier. This is live now.
>
> The link to the .gpx file now shows up on the iD Editor menu
> selection, you do not need to try josm and have it fail. Just go back
> to the page and dowload the .gpx file from the iD Editor selected
> dialog.
>
> A screenshot is attached to make it more clear.
>
> Thank you again Nick and Pierre!
>
> Respectfully,
> Blake
>
>
> On Mon, Feb 6, 2017 at 7:02 AM, Nick Allen 
> wrote:
> > Hi,
> >
> >
> > A quick but dirty workaround
> >
> >
> > 1. Load task in iD
> >
> > 2. return to Task on TM, go back to 'edit with' and select JOSM
> >
> > 3. You will get an error message about JOSM remote control, but it will
> give
> > you access to a section of the JOSM menu
> >
> > 4. From the section that reads "Tip: Download the following .gpx file and
> > load it in JOSM in order to see the current task boundary" right click on
> > ".gpx file" and select "Save link as" - I put mine in my downloads
> folder.
> >
> > 4. Back to the iD tab in your browser, and have file manager open as
> well -
> > drag & drop the downloaded .gpx file onto the window of ID -- then
> wait...
> >
> > 5. If all goes well you now have the square on your iD screen. It took a
> > while to load on my setup & a message about waiting or closing appeared -
> > but it has loaded each time I've tried.
> >
> >
> > I'll try to put together a quick howto with images on LearnOSM and make
> it
> > downloadable. Feedback as to whether this works for everyone would be
> > appreciated in case I have to make amendments.
> >
> > Regards
> >
> >
> > Nick
> > (Tallguy)
> >
> > On 06/02/17 11:36, Donal Hunt wrote:
> >
> > Can confirm. Have noticed that the bounding box doesn't always display.
> > Usually closing the tab and relaunching 1-2 times results in it
> appearing.
> > If logs / javascript console output is useful for tracking down the
> issue,
> > let me know and I'll share. :)
> >
> > d.
> >
> > On 6 February 2017 at 08:09, Rebecca Firth 
> wrote:
> >>
> >> Hi,
> >>
> >> Just to add in on this one, there are quite a lot of mapathons going on
> >> over the next few days, including a group of students in Botswana
> mapping
> >> from today for the next two weeks.
> >>
> >> @Bryan - I had noticed over the past few months that sometimes the pink
> >> box didn't load immediately when you loaded a square, and you needed to
> wait
> >> quite a while or reload the square to see it. Not sure if others had
> seen
> >> the same.
> >>
> >> Thanks,
> >>
> >> Rebecca
> >>
> >> On Sun, Feb 5, 2017 at 10:43 PM, Bryan Housel 
> >> wrote:
> >>>
> >>> That does look like a bug!   I will try to get a fix merged in by your
> >>> event Wednesday…
> >>>
> >>>
> >>> On Feb 5, 2017, at 2:41 PM, Orla McManus 
> >>> wrote:
> >>>
> >>> Hi everyone,
> >>>
> >>> I am unable to see the square bounding box in iD Editor when I lock and
> >>> open a task/grid square e.g.http://tasks.hotosm.org/
> project/2477#task/58. My
> >>> understanding is that this bounding box enables the digitiser to
> ensure that
> >>> they are working only in their grid square so that they can mark it as
> done
> >>> in the Tasking Manager.
> >>>
> >>> Has this been removed with a recent update of iD Editor? Will this
> >>> functionality be added again?
> >>>
> >>> We have a mapathon organised for Wednesday with all beginners and it
> will
> >>> be much more difficult to coordinate our progress without this
> bounding box
> >>> in iD Editor.
> >>>
> >>> Thanks very much,
> >>> Orla
> >>>
> >>>
> >>>
> >>> 

[HOT] Fundraising WG Mtg. Weds. 3/1 @ 12PM EST

[Rachel VanNice]

For anyone interested, the Fundraising Working Group will be meeting
this *Weds.
March 1st, at 12PM EST* on Skype (ping tyler.radford or rachel.vannice if
you'd like to join). We're going to be discussing upcoming and recent grant
applications, website donation functionality and building recurring
donations to sustain's HOT's work.
Thanks!
-- 
Rachel VanNice
Operations Coordinator
E-Mail: rachel.vann...@hotosm.org
Skype: rachel.vannice

Humanitarian OpenStreetMap Team
Using OpenStreetMap for Humanitarian Response & Economic Development
web  | twitter  | facebook
 | donate

___
HOT mailing list
HOT@openstreetmap.org
https://lists.openstreetmap.org/listinfo/hot

Re: [HOT] Could we get more out of our mappers by asking for less?

[Blake Girardot HOT/OSM]

On Mon, Feb 27, 2017 at 11:36 AM, Jo  wrote:
> If you use 'w' in JOSM there is hardly ever a need to delete user's
> contributions. It's really easy to drag the corners where they need to be,
> then finish of with 'q' to square the building.
>
> Polyglot

This is a good tip, I forgot about this one for fixing up mapping.

If I do feel the need to re-map from scratch, I do it on a blank
layer, then merge the layer with the existing mapping layer, then use
Replace Geometry for each building pair (old and new). I estimate it
takes only about 10% longer than just totally re-mapping from scratch,
but that is worth it to me to keep the history and original mapper's
contribution.

Video demonstration of that process: https://youtu.be/Kv5AOmX8M9g

Thanks again Polyglot for reminding us about Improve Way for improving
building mapping.

Cheers
Blake







> 2017-02-26 20:00 GMT+01:00 Russell Deffner :
>>
>> On this topic, there has been concern over validators doing so much
>> deletion of recently mapped objects.  This triggers a few monitoring sites
>> that watch for 'suspicious changesets'; it doesn't mean much in the
>> immediate, but thinking longer term for the OSM project, those algorithms
>> could be used for automatic warnings or blocks.  I think no matter what,
>> we're always going to be dealing with poor mapping, so we should also look
>> at some best practices/rules of thumb for when to delete versus improve a
>> previously mapped feature.  Although I do find myself deleting and
>> re-drawing sometimes, I try to minimize that as there is something to
>> preserving the original mappers contribution.  This can also be an issue for
>> trying to calculate mappers contributions for a mapathon or project if a
>> validator unnecessarily deletes the objects.
>>
>> To quickly touch on project creation; I think roads and
>> settlements/residential areas go well together - they both should be done
>> with larger task squares than for building projects, but not sure it matters
>> too much which one comes first, but for disaster response as an example, I
>> would think roads and settlements are first priority followed by buildings.
>>
>> Happy Mapping,
>> =Russ
>>
>> -Original Message-
>> From: Andrew Buck [mailto:andrew.r.b...@gmail.com]
>> Sent: Sunday, February 26, 2017 10:20 AM
>> To: hot@openstreetmap.org
>> Subject: Re: [HOT] Could we get more out of our mappers by asking for
>> less?
>>
>> > I think this is a different conversation, I would prefer mappers take a
>> > little more time and care, some buildings I've seen mapped have little
>> > relationship to the size or shape of the building.
>> >
>> > Cheerio John
>>
>> I agree on this.  Especially with respect to buildings.  Roads are
>> fairly easy to add refinements to by doing them one at a time and using
>> the replace geometry tool in JOSM, however poorly mapped buildings take
>> longer to clean up than simply deleting them and mapping them fresh.
>>
>> I would rather see a user add 10 buildings that are high quality then
>> 100 or even 1000 that have to be remapped by someone else.  Having to
>> map something that has already been mapped poorly by someone else is
>> really disheartening.  On the one hand you spend your whole time mapping
>> thinking about how your work is duplicating that of someone else, and on
>> the other hand you feel bad about removing their contribution from the
>> database.  So you get hit with it on both fronts.
>>
>> -AndrewBuck
>>
>>
>>
>>
>> ___
>> HOT mailing list
>> HOT@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/hot
>
>
>
> ___
> HOT mailing list
> HOT@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/hot
>



-- 

Blake Girardot
Humanitarian OpenStreetMap Team, TM3 Project Manager
skype: jblakegirardot
HOT Core Team Contact: i...@hotosm.org
Live OSM Mapper-Support channel - https://hotosm-slack.herokuapp.com/
BE A PART OF HOT'S MICRO GRANTS: https://donate.hotosm.org/

___
HOT mailing list
HOT@openstreetmap.org
https://lists.openstreetmap.org/listinfo/hot

Re: [HOT] Could we get more out of our mappers by asking for less?

[Jo]

If you use 'w' in JOSM there is hardly ever a need to delete user's
contributions. It's really easy to drag the corners where they need to be,
then finish of with 'q' to square the building.

Same goes for highways (Ctrl-left mouse button to add nodes where needed).
Truly nifty that improve way accuracy tool.

Polyglot

2017-02-26 20:00 GMT+01:00 Russell Deffner :

> On this topic, there has been concern over validators doing so much
> deletion of recently mapped objects.  This triggers a few monitoring sites
> that watch for 'suspicious changesets'; it doesn't mean much in the
> immediate, but thinking longer term for the OSM project, those algorithms
> could be used for automatic warnings or blocks.  I think no matter what,
> we're always going to be dealing with poor mapping, so we should also look
> at some best practices/rules of thumb for when to delete versus improve a
> previously mapped feature.  Although I do find myself deleting and
> re-drawing sometimes, I try to minimize that as there is something to
> preserving the original mappers contribution.  This can also be an issue
> for trying to calculate mappers contributions for a mapathon or project if
> a validator unnecessarily deletes the objects.
>
> To quickly touch on project creation; I think roads and
> settlements/residential areas go well together - they both should be done
> with larger task squares than for building projects, but not sure it
> matters too much which one comes first, but for disaster response as an
> example, I would think roads and settlements are first priority followed by
> buildings.
>
> Happy Mapping,
> =Russ
>
> -Original Message-
> From: Andrew Buck [mailto:andrew.r.b...@gmail.com]
> Sent: Sunday, February 26, 2017 10:20 AM
> To: hot@openstreetmap.org
> Subject: Re: [HOT] Could we get more out of our mappers by asking for less?
>
> > I think this is a different conversation, I would prefer mappers take a
> > little more time and care, some buildings I've seen mapped have little
> > relationship to the size or shape of the building.
> >
> > Cheerio John
>
> I agree on this.  Especially with respect to buildings.  Roads are
> fairly easy to add refinements to by doing them one at a time and using
> the replace geometry tool in JOSM, however poorly mapped buildings take
> longer to clean up than simply deleting them and mapping them fresh.
>
> I would rather see a user add 10 buildings that are high quality then
> 100 or even 1000 that have to be remapped by someone else.  Having to
> map something that has already been mapped poorly by someone else is
> really disheartening.  On the one hand you spend your whole time mapping
> thinking about how your work is duplicating that of someone else, and on
> the other hand you feel bad about removing their contribution from the
> database.  So you get hit with it on both fronts.
>
> -AndrewBuck
>
>
>
>
> ___
> HOT mailing list
> HOT@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/hot
>
___
HOT mailing list
HOT@openstreetmap.org
https://lists.openstreetmap.org/listinfo/hot