Re: [HOT] step by step recipe for iD bug reporting
On Sat, May 23, 2015 at 1:40 PM, Charlotte Wolter techl...@techlady.com wrote: That sounds like we're getting closer to a solution, and putting it under Instructions makes sense. It would be even better if there were a button, labeled Report a Problem somewhere in the Tasking Manager. (something for the future) I would just write a draft Problem Report myself, but I don't know what those who would fix a problem would need to know, except the obvious stuff: User Name: Date: Time (with your time zone): Task Number: (Actually there are two, the big task and the little square they were working on. Too bad we can't capture this automatically) Operating system (?): Computer brand (?): Charlotte, Are we talking about two types of problems. One is an iD bug another is a problem with either the Tasking Manager or a task? For the TM related, we could ask for an enhancement to TM to allow people to submit TM bugs. For iD related issues, capturing the iD version and operating system should be do able. It is already captured on the changeset. For JOSM bugs, creating a new issue is more complex. If I remember correctly, the user has to capture some system/java info to attach to the report. Clifford -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
Re: [HOT] step by step recipe for iD bug reporting (was: Problems saving in ID)
On Sat, May 23, 2015 at 10:04 AM, Carl von Einem c...@einem.net wrote: 1. on the upper left is a search bar (Search GitHub): type 'iD' and click enter on your keyboard 2. in the list of search results click on openstreetmap/iD (should be the first item) 3. click on Issues (navigation bar on the right) At this point search to see if the bug has already been reported by adding key words in the filter text box and hit enter. If no open issues are found, then proceed to step 4. Otherwise enter any relevant information into the existing issue. 4. click on New issue (green button) 5. choose a good title and write your problem description 6. click on Submit... -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
[HOT] LearnOSM update - OsmAnd 2+ section
Hi, New section in LearnOSM for users of OsmAnd - http://learnosm.org/en/mobile-mapping/osmand2/ With grateful thanks to Win Olario (gitGOwin) for producing this guide. -- Nick Volunteer 'Tallguy' for https://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Team http://www.openstreetmap.org/user/Tallguy ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
Re: [HOT] step by step recipe for iD bug reporting
Cliff, Right. It should be clarified. Problem with iD or JSOM As for what else is needed, that is up to those who know how to fix either. Maybe the button above should lead to two choices: iD or JOSM, at which point the appropriate questionnaire appears. Does JOSM include a way to report issues? To my knowledge, iD does not. Clearly they need to be separate. --C At 02:51 PM 5/23/2015, you wrote: On Sat, May 23, 2015 at 1:40 PM, Charlotte Wolter mailto:techl...@techlady.comtechl...@techlady.com wrote:  That sounds like we're getting closer to a solution, and putting it under Instructions makes sense. It would be even better if there were a button, labeled Report a Problem somewhere in the Tasking Manager. (something for the future)     I would just write a draft Problem Report myself, but I don't know what those who would fix a problem would need to know, except the obvious stuff:     User Name:     Date:     Time (with your time zone):     Task Number:        (Actually there are two, the big task and the little square they were working on. Too bad we can't capture this automatically)     Operating system (?):     Computer brand (?): Charlotte, Are we talking about two types of problems. One is an iD bug another is a problem with either the Tasking Manager or a task? For the TM related, we could ask for an enhancement to TM to allow people to submit TM bugs. For iD related issues, capturing the iD version and operating system should be do able. It is already captured on the changeset. For JOSM bugs, creating a new issue is more complex. If I remember correctly, the user has to capture some system/java info to attach to the report. Clifford -- @osm_seattle http://osm_seattle.snowandsnow.usosm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch Charlotte Wolter 927 18th Street Suite A Santa Monica, California 90403 +1-310-597-4040 techl...@techlady.com Skype: thetechlady ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
[HOT] Fwd: Re: Fwd: step by step recipe for iD bug reporting (was: Problems saving in ID)
Suzan, It sound like you would be a great resource in making this happen. Now all we need to do is get a clear mandate from the board (important) and some programmers. When is the next board meeting? We should get this on the agenda. Charlotte Delivered-To: techl...@techlady.com From: Suzan Reed su...@suzanreed.com To: Charlotte Wolter techl...@techlady.com Date: Sat, 23 May 2015 16:24:50 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 AquaMail/1.5.7.3 (build: 21070068) Subject: Re: [HOT] Fwd: step by step recipe for iD bug reporting (was: Problems saving in ID) X-RR-Connecting-IP: 107.14.168.141:25 X-Authority-Analysis: v=2.1 cv=UbHfSciN c=1 sm=1 tr=0 a=CoGJZMXjC9ZqYjZMN9F/3A==:117 a=WSfeHOnGVVNQgzP7+CPq3g==:17 a=ayC55rCo:8 a=0oj8HZZGiqAA:10 a=j0qPZ1vW3qUA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=c40qY45Z:8 a=TZb1taSU:8 a=AUq6ltok:8 a=h1PgugrvaO0A:10 a=glSbvxPM:8 a=k5cIrk9c:8 a=595fbENk:8 a=NEAV23lm:8 a=-btfA0ZSW1iCa6GgQqQA:9 a=CjuIK1q_8ugA:10 a=d6Sr02UbQdMA:10 a=3hlsNCOeBJQA:10 X-Cloudmark-Score: 0 Exactly what Charlotte said. OSM and HOT are going through a monumental change. A huge influx of 3000, 4000 new to OSM people. We want them to continue to contribute and because we want them to stick around, we owe it to them to make everything about OSM and HOT as easy-to-use as possible. Convoluted workflows requiring new login and passwords, searches, and instructions that are scattered, all of that has to change as we grow into this new sized, new era of anyone can help. Anything we can do to make the experience intuitive and a no-brainer we need to do as good hosts. Either we welcome all these enthusiastic people, or we stay a small, insular, insider's club where diverse contributers find a difficult if not impossible terrain. For now your instructions would be great on an interim page people get when reporting an issue, inbetween the Task Manager and Github. Usability! We all need to think about how to make it easy! It's challenging and interesting to figure out the simpliest, easiest way to do something on the web! As this is one of the things I do professionally, I would love to make a proposal through a sample website working on a team with programmers. Thinking of Dan in Montana who left after one day because he was frustrated with OSM. Suzan On May 23, 2015 11:51:37 AM Charlotte Wolter techl...@techlady.com wrote: Carl, It's very nice that you spelled out the steps, but you're not getting it. We can't make ordinary mappers go through those steps just to submit a problem report. They need a link to a single page that has the words Problem Report at the top. They fill in the blanks and hit Submit. Otherwise, we'll lose them. They'll just give up, and we'll never know what issues are happening. Charlotte Delivered-To: techl...@techlady.com Date: Sat, 23 May 2015 19:04:59 +0200 From: Carl von Einem c...@einem.net Organization: www.einem.net User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 To: hot@openstreetmap.org X-Provags-ID: V03:K0:o1oj+HV0b/hlamTGseHI+e7OtO3edJdT5Uwby7dPU1D1fshTelQ JiXmffTqgMdQe+ga4lbjLMl3ipdPrJKrAsR/RBdKM8Dg8u2X38btUUu2NXmrQhQiQpxaNze 2TqsMdh/UiRmnWINT/VBAuQ1jDdvHq53U+hP9zXQUbG268FWiCNzE37iFIOKYt6kocEJSku I0TNWO8VXoXY3LcRecolg== X-UI-Out-Filterresults: notjunk:1; Subject: [HOT] step by step recipe for iD bug reporting (was: Problems saving in ID) X-BeenThere: hot@openstreetmap.org X-Mailman-Version: 2.1.16 Reply-To: c...@einem.net List-Id: Humanitarian OpenStreetMap Team hot.openstreetmap.org List-Unsubscribe: https://lists.openstreetmap.org/options/hot, mailto:hot-requ...@openstreetmap.org?subject=unsubscribe List-Archive: http://lists.openstreetmap.org/pipermail/hot/ List-Post: mailto:hot@openstreetmap.org List-Help: mailto:hot-requ...@openstreetmap.org?subject=help List-Subscribe: https://lists.openstreetmap.org/listinfo/hot, mailto:hot-requ...@openstreetmap.org?subject=subscribe X-RR-Connecting-IP: 107.14.168.105:25 X-Authority-Analysis: v=2.1 cv=Q5pc4uGa c=1 sm=1 tr=0 a=DB0hE7zaO8GYUp/YqmXQew==:117 a=CRRwbcOFI+X/mpt5jVcafw==:17 a=ayC55rCo:8 a=0oj8HZZGiqAA:10 a=vp1jIXIPkZwA:10 a=BLceEmwcHowA:10 a=wPDyFdB5xvgA:10 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=k5cIrk9c:8 a=TZb1taSU:8 a=595fbENk:8 a=lyYuGu4CHa5PaZGX25icmyaRxzw=:19 a=h1PgugrvaO0A:10 a=NEAV23lm:8 a=X0rGZIHscPEHP_VaLXUA:9 a=QEXdDO2ut3YA:10 X-Cloudmark-Score: 0 Charlotte Wolter wrote on 23.05.15 16:57: This is my point exactly. Github works only for people who already are insiders, people who know how to use it. It doesn't work if you're not used to it. We need a simple Problem Report form on the web site. If the coders want to use Github to solve the problem, fine. They're welcome to it. But for us ordinary people, we need something in simple direct English. By
Re: [HOT] step by step recipe for iD bug reporting
On Sat, May 23, 2015 at 5:00 PM, Charlotte Wolter techl...@techlady.com wrote: Right. It should be clarified. Problem with iD or JSOM As for what else is needed, that is up to those who know how to fix either. Maybe the button above should lead to two choices: iD or JOSM, at which point the appropriate questionnaire appears. Does JOSM include a way to report issues? To my knowledge, iD does not. Clearly they need to be separate. JOSM bugs are reported on the josm.openstreetmap.de website. One the main JOSM page are the instructions: Found a bug? | Have an idea? | Make a suggestion? http://josm.openstreetmap.de/#Bugs - Please report any bug found: Create a new ticket http://josm.openstreetmap.de/newticket using the Report Bug http://josm.openstreetmap.de/wiki/Help/Action/ReportBug entry in the main menu Help http://josm.openstreetmap.de/wiki/Help/Menu/Help. Alternatively, the same function is available under About http://josm.openstreetmap.de/wiki/Help/Action/About and Show status report http://josm.openstreetmap.de/wiki/Help/Action/ShowStatusReport. - Discuss ideas and suggestions also in the bug tracker http://josm.openstreetmap.de/newticket, on the josm-dev https://lists.openstreetmap.org/listinfo/josm-dev mailing list, or on the #josm IRC channel. JOSM is sold as an advanced editor which might give the impress that someone steps up from iD to JSOM. From what I've seen on HOT, for some tasks it is the preferred editor which means that new mappers are using JOSM. If they come from an open source, ie linux, background I don't see any real roadblocks to creating bug reports. But for the vast majority it is somewhat intimidating. One solution is to report the bug on the Tasking Manager for the task owner to verify. If it is a bug, the task owner reports the bug on the josm website. That allows the owner to triage the reports to make sure that they weed out user/training issues. I'm inclined to suggest modifying the TM interface to include these issues. What does everyone else think? Clifford -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
Re: [HOT] Database, OSM HOT (Was: Request for information about common set of tags for HOT)
At 22-05-2015 06:39 Friday, Andreas Goss wrote: I see that the open, flexible nature of the tag approach has its merits I suppose. The enduring mystery for me is how is this information used in a query? But maybe I am barking up the wrong tree here, perhaps this concept is only used for labeling features, and querying to select the data subset is not a common task. Hello Andreas, Yes, probably. But where did this key/value come from? In my look at the 366,017 records of a few days ago, I do not recall seeing any tags like this. Are they in fact emergency helipads by another name? Are they related to aeroway = helipad or leisure = common? What are the criteria for selecting them? There appear to be thousands. Oops, now I see that they are not even in Nepal. Does each project have its own set of terminology? Are we certain that some emergency landing sites were not given different tags by different mappers as this flexibility seems to be viewed as beneficial. To me this just demonstrates the chaotic nature of the tagging scheme, little consistency or documentation. However, if it appears to work then it works. Thanks Andreas, Cheers . . . . . . . . Spring You mean like this? http://overpass-turbo.eu/s/9wZ __ openstreetmap.org/user/AndiG88 wiki.openstreetmap.org/wiki/User:AndiG88â ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot /x-flowed ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
[HOT] Fwd: [CrisisMappers] Job Opportunity: Nepal Digital Humanitarian Coordinator
Hi folks, Just the messenger. If you someone, apply soon (The job is with the Digital Humanitarian Network, which HOT is a member). Heather -- Forwarded message -- From: Patrick Meier (iRevolution) patr...@irevolution.net Date: May 23, 2015 10:47 AM Subject: [CrisisMappers] Job Opportunity: Nepal Digital Humanitarian Coordinator To: crisismappers crisismapp...@googlegroups.com Cc: Dear CrisisMappers, We're recruiting a Nepal Digital Humanitarian Coordinator. Details here https://docs.google.com/document/d/1ZtOHtQERDJvXAfDGmyegGbmww1jZR7Xx9s_gYQjf_2E/edit; note the tight deadline. Feel free to share further with your networks. Thank you, Patrick Andrej @: PatrickMeier https://twitter.com/PatrickMeier, PhD Blog: iRevolutions.org http://www.irevolutions.org/ (1.5M hits) Book: Digital-Humanitarians.com http://www.digital-humanitarians.com/ Newsletter: Digital Humanitarians http://eepurl.com/9O7Y9 -- CrisisMappers | The Humanitarian Technology Network http://www.CrisisMappers.net To subscribe, follow this link: https://groups.google.com/group/crisismappers To unsubscribe, please send email to crisismappers+unsubscr...@googlegroups.com Visit CrisisMappers at: http://groups.google.com/group/crisismappers?hl=en --- You received this message because you are subscribed to the Google Groups CrisisMappers group. To unsubscribe from this group and stop receiving emails from it, send an email to crisismappers+unsubscr...@googlegroups.com. To post to this group, send email to crisismapp...@googlegroups.com. Visit this group at http://groups.google.com/group/crisismappers. For more options, visit https://groups.google.com/d/optout. ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
Re: [HOT] newbie needs advice
At 22-05-2015 01:06 Friday, cascafico wrote: Springfield Harrison wrote As a 30+ year helicopter pilot, I did have some concern with the very skimpy helipad instructions. In high-altitude, rugged terrain there is much more to locating helipads than finding a 30 m flat square of ground. Is there any technical oversight by experienced pilots on this task? I assume that there are no current maps for this area, just the OSM edits? I did find some ASM 1950s mapping. Is there nothing newer than that? Hello cascafico, That does sound like an interesting approach. Not sure how well the NIR data would identify suitable landing surfaces but it might be a good start. Some sense of the topography is important, the OSM imagery is not really very good for that. Thanks, Cheers . . . . . . . . Spring Harrison One of the first exercises during remote sensing lessons is closely related to your concerns: identify potential landing spots using digital terrain model and near infra-red imagery. It's pretty simple. I wonder why some GIS people didn't automate that, say conditional 10° slope, slope direction, elevation11.000 ft and scrub free land ...maybe no NIR data available? JOSM crowd should be aware of the 30 m DEM TMS available since 20150506 [1] before mapping potential landings... it's very useful, even without vegetation data. [1] http://gis.19327.n5.nabble.com/30-m-DEM-TMS-rendering-for-Nepal-td5843573.html - -- cascafico.altervista.org twitter.com/cascafico -- View this message in context: http://gis.19327.n5.nabble.com/newbie-needs-advice-tp5843387p5845528.html Sent from the Humanitarian OpenStreetMap (HOT) mailing list archive at Nabble.com. ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
Re: [HOT] Database, OSM HOT (Was: Request for information about common set of tags for HOT)
Hello Blake, Thanks for those references. I understand the first one although it does certainly appear daunting. The problem I see is that the long list of attributes/keys/values that are specified for inclusion in the shapefile can go out of date very often as crowd-mappers or new projects invent new key/value tags. Having to manually inspect the other_tags field looks like a bottleneck that could lead to unintended query results, most likely overlooking items that have new keys. This is a long list to keep up to date and there are quite a few of them in your example: attributes=name,type,aeroway,amenity,admin_level,barrier,boundary,building,craft,geological,historic,land_area,landuse,leisure,man_made,military,natural,office,place,shop,sport,tourism Anyway, I understand what you're driving at but the process seems to be overly complex and not given to reliable automation. Has anyone created a GUI for this? Your example for hand wiring all these INI files looks tedious and easy to screw up. I can see that a query builder tool that presented all the keys and their values in pick lists along with the relevant operators would boost the reliability and ease the workload in creating these queries. Thanks for bearing with me again, Cheers . . . . . . . . Spring Harrison At 22-05-2015 06:55 Friday, Blake Girardot wrote: Hi Springfield, Here is how I get useful thematic layers out OSM: http://wiki.openstreetmap.org/wiki/User:Bgirardot/How_To_Convert_osm_.pbf_files_to_Esri_Shapefiles And here is an example files generated through what I would guess is a similar process every 30 mins: http://nepal.piensa.co/ Actually, I see they use a slightly different process with the same basic method, and the same software for the conversion/extraction: https://github.com/GFDRR/osm-extract (feedback on my thematic layers is always welcome, we want to create the most useful layers we can. Examples can be found in the wiki entry for Vanuatu typhoon response) cheers, Blake On 5/22/2015 8:26 AM, Springfield Harrison wrote: Hello John, Thanks for your patient explanation, I'm beginning to see that OSM is a very different flavour of GIS. At the outset, my assumption was that it was entirely emergency oriented. I was puzzled by the references to hairdressers and gymnasiums but I guess they result from a different process. I do think that some emergency related features such as potential helipads, powerline crossings, towers, cable cars, landslides, glacial lakes, emergency shelters and such like might be better left to those with experience with those types of features. They wouldn't necessarily need to be experienced with OSM, just familiar with identifying those features. I'm surprised that there is no process for identifying and directing the more highly qualified mappers. I had intended to help with the helipad project but quickly became discouraged with the less than adequate imagery and the weirdness of leisure = common. Merely verifying the leisure = common sites would probably overlook lots of other qualified sites. And how many sites with this tag are actually sports fields as per the original intention? Then, mapping existing helipads marked with H in a circle, might be redundant as such official sites would probably be already mapped by a national agency. I would recommend that potential helipads be tagged as aeroway = helipads_potential, verified = no. Proper assessment of helipads requires an oblique, 3-D view. I attempted to introduce Google Earth into the process but licensing fears put the kibosh on that. I found this surprising because Google Earth does have several other products and does make a lot of noise about community and not for profit mapping without any references to licensing. They appear to actively promote user generated files being placed into the public domain. I have spent some time attempting to talk to them about this but the best I could do was an e-mail. Will advise. Thanks again for your time on this, I'm sure you have larger fish to fry, Cheers . . . . . . . . Spring Harrison ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
Re: [HOT] Database, OSM HOT (Was: Request for information about common set of tags for HOT)
Oops, now I see that they are not even in Nepal. Does each project have its own set of terminology? Are we certain that some emergency landing sites were not given different tags by different mappers as this flexibility seems to be viewed as beneficial. The idea is certainly not for very project to have its own tags and we try to avoid it whenever possible, even try to merge tags when we see there are similar meanings (which isn't easy, because mass edits aren't allowed unless you basically get 100% support) What usually happens is that there is local demand to tag something and then people come up with a tag. Unfortunately people often forget to document it as you already figured out, if there had been a wiki page for landing_site and it had been linked on aeroway=helipad someone from HOT might have found that tag. To me this just demonstrates the chaotic nature of the tagging scheme, little consistency or documentation. However, if it appears to work then it works. It's certainly a issue and HOT is certainly not the project doing the best job when it comes to documentation (Well, it's often documented somewhere, but not easy to find). Most mappers usually care about their area, which means HOT can often get away with strange tags or tags that have not been discussed, because they don't pop up in the neighbourhood of mappers in Europe. I mean of you started tagging amenity=kitchen in Germany you would have a 10 page discussion of what kind of kitchen that is, who has access etc. Cheers, Andi __ openstreetmap.org/user/AndiG88 wiki.openstreetmap.org/wiki/User:AndiG88 ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
Re: [HOT] Database, OSM HOT (Was: Request for information about common set of tags for HOT)
There is a fairly standardized set of tags that are used frequently. There's no requirement that they be used, but they are common conventions that make the data more usable. So, the *database* doesn't make sure things are right--the *community* does. If you haven't seen it yet, many of these common tags--possibly too many ;)--are collected on the Map Features page ( http://wiki.openstreetmap.org/wiki/Map_Features) and used in other ways such as editor presets. Another, often fascinating, way to look at tag usage is at Taginfo (http://taginfo.openstreetmap.org/). 125 million building=yes features! http://taginfo.openstreetmap.org/tags/building=yes OSM to shapefile (or database) stuff is always a pain, because of the tabular structure that shapefile/databases expect versus the freeform key=value structure of OSM data. So you're bound to get a certain subset of tags, unless you do some customization. There are lots of ways to create shapefiles--see http://wiki.openstreetmap.org/wiki/Shapefiles#Create_your_own_shapefiles (or for PostGIS, see http://wiki.openstreetmap.org/wiki/Osm2pgsql) Tagging is sometimes chaotic, inconsistent and poorly documented, but for the most part it keeps improving--what more can you ask for? :) Cheers, Brad On Sat, May 23, 2015 at 1:52 AM, Springfield Harrison stellar...@gmail.com wrote: Hello Blake, Thanks for those references. I understand the first one although it does certainly appear daunting. The problem I see is that the long list of attributes/keys/values that are specified for inclusion in the shapefile can go out of date very often as crowd-mappers or new projects invent new key/value tags. Having to manually inspect the other_tags field looks like a bottleneck that could lead to unintended query results, most likely overlooking items that have new keys. This is a long list to keep up to date and there are quite a few of them in your example: attributes=name,type,aeroway,amenity,admin_level,barrier,boundary,building,craft,geological,historic,land_area,landuse,leisure,man_made,military,natural,office,place,shop,sport,tourism Anyway, I understand what you're driving at but the process seems to be overly complex and not given to reliable automation. Has anyone created a GUI for this? Your example for hand wiring all these INI files looks tedious and easy to screw up. I can see that a query builder tool that presented all the keys and their values in pick lists along with the relevant operators would boost the reliability and ease the workload in creating these queries. Thanks for bearing with me again, Cheers . . . . . . . . Spring Harrison At 22-05-2015 06:55 Friday, Blake Girardot wrote: Hi Springfield, Here is how I get useful thematic layers out OSM: http://wiki.openstreetmap.org/wiki/User:Bgirardot/How_To_Convert_osm_.pbf_files_to_Esri_Shapefiles And here is an example files generated through what I would guess is a similar process every 30 mins: http://nepal.piensa.co/ Actually, I see they use a slightly different process with the same basic method, and the same software for the conversion/extraction: https://github.com/GFDRR/osm-extract (feedback on my thematic layers is always welcome, we want to create the most useful layers we can. Examples can be found in the wiki entry for Vanuatu typhoon response) cheers, Blake On 5/22/2015 8:26 AM, Springfield Harrison wrote: Hello John, Thanks for your patient explanation, I'm beginning to see that OSM is a very different flavour of GIS. At the outset, my assumption was that it was entirely emergency oriented. I was puzzled by the references to hairdressers and gymnasiums but I guess they result from a different process. I do think that some emergency related features such as potential helipads, powerline crossings, towers, cable cars, landslides, glacial lakes, emergency shelters and such like might be better left to those with experience with those types of features. They wouldn't necessarily need to be experienced with OSM, just familiar with identifying those features. I'm surprised that there is no process for identifying and directing the more highly qualified mappers. I had intended to help with the helipad project but quickly became discouraged with the less than adequate imagery and the weirdness of leisure = common. Merely verifying the leisure = common sites would probably overlook lots of other qualified sites. And how many sites with this tag are actually sports fields as per the original intention? Then, mapping existing helipads marked with H in a circle, might be redundant as such official sites would probably be already mapped by a national agency. I would recommend that potential helipads be tagged as aeroway = helipads_potential, verified = no. Proper assessment of helipads requires an oblique, 3-D view. I attempted to introduce Google Earth into the process but licensing fears put the kibosh on
Re: [HOT] tasks.hotosm.org bug report
Unfortunately there's not a way to delete the comment or load it otherwise. We will hopefully have a patch soon so that it is viewable again. Best,Ethan aka FTA From: openstreetmap@scare.ca Date: Sat, 23 May 2015 01:39:44 -0500 Subject: Re: [HOT] tasks.hotosm.org bug report To: eman...@hotmail.com CC: hot@openstreetmap.org It might work then if the @ was URL-encoded into %40 . Is there a way to edit or delete my most recent comment, without being able to load the task page it was left on? http://tasks.hotosm.org/user/Scare%21 This is indeed a bug that has been reported in the past for links containing the @ symbol (see https://github.com/hotosm/osm-tasking-manager2/issues/493). I will add your experience to the issue thread, though ideally we shouldn't link to copyrighted maps. Thanks for your notification! Best,Ethan aka FTA ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
[HOT] Fwd: Re: Fwd: Re: Problems saving in ID
All, This is my point exactly. Github works only for people who already are insiders, people who know how to use it. It doesn't work if you're not used to it. We need a simple Problem Report form on the web site. If the coders want to use Github to solve the problem, fine. They're welcome to it. But for us ordinary people, we need something in simple direct English. By the way, there still are a couple of ongoing issues with iD that no one seems to be tackling, despite reports on Github. Charlotte Delivered-To: techl...@techlady.com Subject: Re: [HOT] Fwd: Re: Problems saving in ID From: Suzan Reed su...@suzanreed.com Date: Fri, 22 May 2015 16:37:23 -0700 Cc: Charlotte Wolter techl...@techlady.com, althio althio althio.fo...@gmail.com To: Robert Banick rban...@gmail.com, HOT hot@openstreetmap.org X-Mailer: Apple Mail (2.1085) X-RR-Connecting-IP: 107.14.168.7:25 X-Authority-Analysis: v=2.1 cv=XIu+SGRE c=1 sm=1 tr=0 a=s24Y6Gjpp1c7EhQxjb5ZoQ==:117 a=WSfeHOnGVVNQgzP7+CPq3g==:17 a=ayC55rCo:8 a=0oj8HZZGiqAA:10 a=BLceEmwcHowA:10 a=N659UExz7-8A:10 a=c40qY45Z:8 a=TZb1taSU:8 a=AUq6ltok:8 a=h1PgugrvaO0A:10 a=NEAV23lm:8 a=glSbvxPM:8 a=pGLkceIS:8 a=595fbENk:8 a=pWACv58TRM1kQv9pLpYA:9 a=pILNOxqGKmIA:10 a=d6Sr02UbQdMA:10 X-Cloudmark-Score: 0 Hi everyone! So I started working on the tutorial for Github, feeling enthusiastic, and quickly realized the workflow in Github delivers disasterous results. Once you login or sign up, which has to be done before you can report and issue, you are directed to a landing page that has nothing to do with OpenStreetMaps, and instead asks you to choose a plan and pay money. Yikes! What!?? How did I get here? How do I find a way to report my problem? (https://github.com/) It took many clicks and searches that didn't produce anything at all relevant to end up no where. (I took screen shots.) Finally! I clicked on the original link provided by Nick and althio, and I was at the right page and already signed in. Success! But not intuitive. (Also, signing in is not easy once you have an account as it asked me five different times to give a new username. What!?? I already have a username for Github! And now my past usernames are taken? Really?) So this is my conclusion (I used to teach and lecture on Usability so I hope this is of some help): 1. Either find another tool that's much easier to use or 2. See if Github can be customized and dumbed down so it delivers the correct landing page for OpenStreetMaps, and further customize it by deleting a lot of the other buttons (fork etc.) that appear now. or the KISS, easy, user-friendly solution 3. Simply provide a web based email form, with instructions to the user to add their OS, browser, etc., that goes to the programming group and have them copy and paste into Github. (Happy to help format and write so it's easy to understand for the user.) Bottom line: As it is, I don't think many non-IT/programming/scientific people are going to figure out how to report an issue. Therefore, programming isn't going to know there's an issue, and the non-tech user public will continue to have a really bad experience, say with iD not saving and oddball dialog boxes, and doubling or even tripling the number of buildings and roads on a tile through multiple saves that make the validator do a lot of extra work. Not good. ~ Software that doesn't work makes OSM and HOT look bad. ~ Easy solutions make OSM and HOT look good and the public user feel happy. I really did want to write the tutorial, but goodness, Github is a hot mess! I bow to the programmers who like it. Suzan On May 22, 2015, at 10:25 AM, Robert Banick wrote: Hi Charlotte, The intention of putting issue reporting there is to create information thats *actionable* for the (primarily Mapbox) folks who maintain and develop iD. That way problems are automatically linked to solutions. As you can tell, I gently disagree with your assessment of githubs utility. Im not a developer but I find it really useful for communicating to developers, who, after all, are the ones to fix things. That being said, could you maybe explain how Github is poor for reporting issues with iD? If you can maybe explain your frustrations further we can understand how to either better explain Github to new users *or* create new processes that better match your needs as a user. Im not opposed to the latter but I would hope to give Github a shot instead of inventing yet another process. Cheers, Robert Sent from Mailbox On Fri, May 22, 2015 at 1:07 PM, Charlotte Wolter techl...@techlady.com wrote: Suzan, You're not alone. Github was designed for people writing software. It is an absolutely terrible way to report issues with iD or anything else. Why isn't there a page on the OSM web site with a simple form for reporting these issues? Charlotte Delivered-To: techl...@techlady.com
[HOT] step by step recipe for iD bug reporting (was: Problems saving in ID)
Charlotte Wolter wrote on 23.05.15 16:57: This is my point exactly. Github works only for people who already are insiders, people who know how to use it. It doesn't work if you're not used to it. We need a simple Problem Report form on the web site. If the coders want to use Github to solve the problem, fine. They're welcome to it. But for us ordinary people, we need something in simple direct English. By the way, there still are a couple of ongoing issues with iD that no one seems to be tackling, despite reports on Github. I'm no coder and here is my step by step recipe for iD bug reporting: Visit https://github.com/ and Sign up (the platform is independent from OSM and HOT so you'll need to create a new account first). When successfully logged in just follow this procedure: 1. on the upper left is a search bar (Search GitHub): type 'iD' and click enter on your keyboard 2. in the list of search results click on openstreetmap/iD (should be the first item) 3. click on Issues (navigation bar on the right) 4. click on New issue (green button) 5. choose a good title and write your problem description 6. click on Submit... Done! ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
Re: [HOT] Fwd: step by step recipe for iD bug reporting (was: Problems saving in ID)
That's a valid point. Carl Charlotte Wolter wrote on 23.05.15 20:49: Carl, It's very nice that you spelled out the steps, but you're not getting it. We can't make ordinary mappers go through those steps just to submit a problem report. They need a link to a single page that has the words Problem Report at the top. They fill in the blanks and hit Submit. Otherwise, we'll lose them. They'll just give up, and we'll never know what issues are happening. Charlotte ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
Re: [HOT] tasks.hotosm.org bug report
It might work then if the @ was URL-encoded into %40 . Is there a way to edit or delete my most recent comment, without being able to load the task page it was left on? http://tasks.hotosm.org/user/Scare%21 This is indeed a bug that has been reported in the past for links containing the @ symbol (see https://github.com/hotosm/osm-tasking-manager2/issues/493). I will add your experience to the issue thread, though ideally we shouldn't link to copyrighted maps. Thanks for your notification! Best, Ethan aka FTA ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
[HOT] Fwd: step by step recipe for iD bug reporting (was: Problems saving in ID)
Carl, It's very nice that you spelled out the steps, but you're not getting it. We can't make ordinary mappers go through those steps just to submit a problem report. They need a link to a single page that has the words Problem Report at the top. They fill in the blanks and hit Submit. Otherwise, we'll lose them. They'll just give up, and we'll never know what issues are happening. Charlotte Delivered-To: techl...@techlady.com Date: Sat, 23 May 2015 19:04:59 +0200 From: Carl von Einem c...@einem.net Organization: www.einem.net User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 To: hot@openstreetmap.org X-Provags-ID: V03:K0:o1oj+HV0b/hlamTGseHI+e7OtO3edJdT5Uwby7dPU1D1fshTelQ JiXmffTqgMdQe+ga4lbjLMl3ipdPrJKrAsR/RBdKM8Dg8u2X38btUUu2NXmrQhQiQpxaNze 2TqsMdh/UiRmnWINT/VBAuQ1jDdvHq53U+hP9zXQUbG268FWiCNzE37iFIOKYt6kocEJSku I0TNWO8VXoXY3LcRecolg== X-UI-Out-Filterresults: notjunk:1; Subject: [HOT] step by step recipe for iD bug reporting (was: Problems saving in ID) X-BeenThere: hot@openstreetmap.org X-Mailman-Version: 2.1.16 Reply-To: c...@einem.net List-Id: Humanitarian OpenStreetMap Team hot.openstreetmap.org List-Unsubscribe: https://lists.openstreetmap.org/options/hot, mailto:hot-requ...@openstreetmap.org?subject=unsubscribe List-Archive: http://lists.openstreetmap.org/pipermail/hot/ List-Post: mailto:hot@openstreetmap.org List-Help: mailto:hot-requ...@openstreetmap.org?subject=help List-Subscribe: https://lists.openstreetmap.org/listinfo/hot, mailto:hot-requ...@openstreetmap.org?subject=subscribe X-RR-Connecting-IP: 107.14.168.105:25 X-Authority-Analysis: v=2.1 cv=Q5pc4uGa c=1 sm=1 tr=0 a=DB0hE7zaO8GYUp/YqmXQew==:117 a=CRRwbcOFI+X/mpt5jVcafw==:17 a=ayC55rCo:8 a=0oj8HZZGiqAA:10 a=vp1jIXIPkZwA:10 a=BLceEmwcHowA:10 a=wPDyFdB5xvgA:10 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=k5cIrk9c:8 a=TZb1taSU:8 a=595fbENk:8 a=lyYuGu4CHa5PaZGX25icmyaRxzw=:19 a=h1PgugrvaO0A:10 a=NEAV23lm:8 a=X0rGZIHscPEHP_VaLXUA:9 a=QEXdDO2ut3YA:10 X-Cloudmark-Score: 0 Charlotte Wolter wrote on 23.05.15 16:57: This is my point exactly. Github works only for people who already are insiders, people who know how to use it. It doesn't work if you're not used to it. We need a simple Problem Report form on the web site. If the coders want to use Github to solve the problem, fine. They're welcome to it. But for us ordinary people, we need something in simple direct English. By the way, there still are a couple of ongoing issues with iD that no one seems to be tackling, despite reports on Github. I'm no coder and here is my step by step recipe for iD bug reporting: Visit https://github.com/ and Sign up (the platform is independent from OSM and HOT so you'll need to create a new account first). When successfully logged in just follow this procedure: 1. on the upper left is a search bar (Search GitHub): type 'iD' and click enter on your keyboard 2. in the list of search results click on openstreetmap/iD (should be the first item) 3. click on Issues (navigation bar on the right) 4. click on New issue (green button) 5. choose a good title and write your problem description 6. click on Submit... Done! ___ HOT mailing list mailto:HOT@openstreetmap.orgHOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot Charlotte Wolter 927 18th Street Suite A Santa Monica, California 90403 +1-310-597-4040 techl...@techlady.com Skype: thetechlady ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
Re: [HOT] step by step recipe for iD bug reporting
Thanks, Clifford, that's an important step. As Charlotte correctly points out we'll probably lose a huge number of users here anyhow. But maybe this can be a basis for a How can I report a technical problem? guide in the Questions About Tasks, Mapping or HOT? section of the OSM Tasking Manager. Actually this should also be available in the Instructions tab and in http://tasks.hotosm.org/about. Carl Clifford Snow wrote on 23.05.15 20:44: On Sat, May 23, 2015 at 10:04 AM, Carl von Einem c...@einem.net mailto:c...@einem.net wrote: 1. on the upper left is a search bar (Search GitHub): type 'iD' and click enter on your keyboard 2. in the list of search results click on openstreetmap/iD (should be the first item) 3. click on Issues (navigation bar on the right) At this point search to see if the bug has already been reported by adding key words in the filter text box and hit enter. If no open issues are found, then proceed to step 4. Otherwise enter any relevant information into the existing issue. 4. click on New issue (green button) 5. choose a good title and write your problem description 6. click on Submit... ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
Re: [HOT] step by step recipe for iD bug reporting
I believe Clifford's suggested approach would address some of the issues brought up by Charlotte and Suzan. I'd recommend going further and for the next activation approaching this scale, have a small group of experienced HOT volunteers whose primary task is to set up and actively participate in a well publicized beginner's chat -- answering questions, clarifying instructions, and steering folks to resources. Cheers, John On Sat, May 23, 2015 at 7:15 PM, Clifford Snow cliff...@snowandsnow.us wrote: On Sat, May 23, 2015 at 5:00 PM, Charlotte Wolter techl...@techlady.com wrote: Right. It should be clarified. Problem with iD or JSOM As for what else is needed, that is up to those who know how to fix either. Maybe the button above should lead to two choices: iD or JOSM, at which point the appropriate questionnaire appears. Does JOSM include a way to report issues? To my knowledge, iD does not. Clearly they need to be separate. JOSM bugs are reported on the josm.openstreetmap.de website. One the main JOSM page are the instructions: Found a bug? | Have an idea? | Make a suggestion? http://josm.openstreetmap.de/#Bugs - Please report any bug found: Create a new ticket http://josm.openstreetmap.de/newticket using the Report Bug http://josm.openstreetmap.de/wiki/Help/Action/ReportBug entry in the main menu Help http://josm.openstreetmap.de/wiki/Help/Menu/Help. Alternatively, the same function is available under About http://josm.openstreetmap.de/wiki/Help/Action/About and Show status report http://josm.openstreetmap.de/wiki/Help/Action/ShowStatusReport. - Discuss ideas and suggestions also in the bug tracker http://josm.openstreetmap.de/newticket, on the josm-dev https://lists.openstreetmap.org/listinfo/josm-dev mailing list, or on the #josm IRC channel. JOSM is sold as an advanced editor which might give the impress that someone steps up from iD to JSOM. From what I've seen on HOT, for some tasks it is the preferred editor which means that new mappers are using JOSM. If they come from an open source, ie linux, background I don't see any real roadblocks to creating bug reports. But for the vast majority it is somewhat intimidating. One solution is to report the bug on the Tasking Manager for the task owner to verify. If it is a bug, the task owner reports the bug on the josm website. That allows the owner to triage the reports to make sure that they weed out user/training issues. I'm inclined to suggest modifying the TM interface to include these issues. What does everyone else think? Clifford -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
Re: [HOT] step by step recipe for iD bug reporting
Never mind, think I answered my own question; so my opinion – if the idea is that anyone can ‘report a bug’ they find on any OSM tool/platform to the HOT volunteers coordinating the response who then triage and report to the proper place – that is not going to happen, sorry. =Russ From: Russell Deffner [mailto:russell.deff...@hotosm.org] Sent: Saturday, May 23, 2015 10:12 PM To: 'Clifford Snow'; 'Charlotte Wolter' Cc: 'HOT' Subject: RE: [HOT] step by step recipe for iD bug reporting How would the report then get to the proper place? =Russ From: Clifford Snow [mailto:cliff...@snowandsnow.us] Sent: Saturday, May 23, 2015 8:16 PM To: Charlotte Wolter Cc: HOT Subject: Re: [HOT] step by step recipe for iD bug reporting On Sat, May 23, 2015 at 5:00 PM, Charlotte Wolter techl...@techlady.com wrote: Right. It should be clarified. Problem with iD or JSOM As for what else is needed, that is up to those who know how to fix either. Maybe the button above should lead to two choices: iD or JOSM, at which point the appropriate questionnaire appears. Does JOSM include a way to report issues? To my knowledge, iD does not. Clearly they need to be separate. JOSM bugs are reported on the josm.openstreetmap.de website. One the main JOSM page are the instructions: Found a bug? | Have an idea? | Make a suggestion? * Please report any bug found: Create a http://josm.openstreetmap.de/newticket new ticket using the http://josm.openstreetmap.de/wiki/Help/Action/ReportBug Report Bug entry in the main menu http://josm.openstreetmap.de/wiki/Help/Menu/Help Help. Alternatively, the same function is available under http://josm.openstreetmap.de/wiki/Help/Action/About About and http://josm.openstreetmap.de/wiki/Help/Action/ShowStatusReport Show status report. * Discuss ideas and suggestions also in the http://josm.openstreetmap.de/newticket bug tracker, on the https://lists.openstreetmap.org/listinfo/josm-dev josm-dev mailing list, or on the #josm IRC channel. JOSM is sold as an advanced editor which might give the impress that someone steps up from iD to JSOM. From what I've seen on HOT, for some tasks it is the preferred editor which means that new mappers are using JOSM. If they come from an open source, ie linux, background I don't see any real roadblocks to creating bug reports. But for the vast majority it is somewhat intimidating. One solution is to report the bug on the Tasking Manager for the task owner to verify. If it is a bug, the task owner reports the bug on the josm website. That allows the owner to triage the reports to make sure that they weed out user/training issues. I'm inclined to suggest modifying the TM interface to include these issues. What does everyone else think? Clifford -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
Re: [HOT] Fwd: Re: Fwd: step by step recipe for iD bug reporting (was: Problems saving in ID)
Oh, not met by myself! I would work with a small team to iron this out, but we would get a better product with a small team participating. Who wants to help? ___ Here's a rough idea of how this could work. (I may be leaving out some of the programming needed. Please comment.) Workflow: 1. One link in the Task Manager Report a Problem. Maybe in the red header? This would hardwire it into Task Manager. 2. Click goes to a new page. (The form automatically picks up the OS, the browser, the date and time, and so on. Whatever the team needs.) (There would need to be buy in from the teams who fix problems as they would have to put these into Github. Could programming populate Github but that circumvents the search to see if the problem has been previously reported. In other situations, this is called an Open Ticket and these go into the reporting workflow whether they come from phone calls, emails, forms.) Copy: Thank you for reporting an issue. Please fill in the form below. It will automatically be sent to the responsible team. Radio buttons where only one selection is possible: iD, JOSM, Other. Could be added to. (These buttons automatically direct where the email is routed.} Form: First name: (It's nice to know who you are talking to, address them my name.) Last name: (Because there may be more than one Chris or Cliff. Username: (This is the username you use to log into OSM.) Email address: (Privacy statement can be noted at the bottom of the page.) Please describe exactly what happened in detail: (Or other prompt.) Box for the description Place to upload screenshots with copy describing how to do this. Use Browse and Drag and Drop? Send Links to common issues and how to fix them. Links to Learning the OSM Track Manager. Other links. On May 23, 2015, at 5:03 PM, Charlotte Wolter wrote: Suzan, It sound like you would be a great resource in making this happen. Now all we need to do is get a clear mandate from the board (important) and some programmers. When is the next board meeting? We should get this on the agenda. Charlotte Delivered-To: techl...@techlady.com From: Suzan Reed su...@suzanreed.com To: Charlotte Wolter techl...@techlady.com Date: Sat, 23 May 2015 16:24:50 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 AquaMail/1.5.7.3 (build: 21070068) Subject: Re: [HOT] Fwd: step by step recipe for iD bug reporting (was: Problems saving in ID) X-RR-Connecting-IP: 107.14.168.141:25 X-Authority-Analysis: v=2.1 cv=UbHfSciN c=1 sm=1 tr=0 a=CoGJZMXjC9ZqYjZMN9F/3A==:117 a=WSfeHOnGVVNQgzP7+CPq3g==:17 a=ayC55rCo:8 a=0oj8HZZGiqAA:10 a=j0qPZ1vW3qUA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=c40qY45Z:8 a=TZb1taSU:8 a=AUq6ltok:8 a=h1PgugrvaO0A:10 a=glSbvxPM:8 a=k5cIrk9c:8 a=595fbENk:8 a=NEAV23lm:8 a=-btfA0ZSW1iCa6GgQqQA:9 a=CjuIK1q_8ugA:10 a=d6Sr02UbQdMA:10 a=3hlsNCOeBJQA:10 X-Cloudmark-Score: 0 Exactly what Charlotte said. OSM and HOT are going through a monumental change. A huge influx of 3000, 4000 new to OSM people. We want them to continue to contribute and because we want them to stick around, we owe it to them to make everything about OSM and HOT as easy-to-use as possible. Convoluted workflows requiring new login and passwords, searches, and instructions that are scattered, all of that has to change as we grow into this new sized, new era of anyone can help. Anything we can do to make the experience intuitive and a no-brainer we need to do as good hosts. Either we welcome all these enthusiastic people, or we stay a small, insular, insider's club where diverse contributers find a difficult if not impossible terrain. For now your instructions would be great on an interim page people get when reporting an issue, inbetween the Task Manager and Github. Usability! We all need to think about how to make it easy! It's challenging and interesting to figure out the simpliest, easiest way to do something on the web! As this is one of the things I do professionally, I would love to make a proposal through a sample website working on a team with programmers. Thinking of Dan in Montana who left after one day because he was frustrated with OSM. Suzan On May 23, 2015 11:51:37 AM Charlotte Wolter techl...@techlady.com wrote: Carl, It's very nice that you spelled out the steps, but you're not getting it. We can't make ordinary mappers go through those steps just to submit a problem report. They need a link to a single page that has the words Problem Report at the top. They fill in the blanks and hit Submit. Otherwise, we'll lose them. They'll just give up, and we'll never know what issues are happening. Charlotte Delivered-To: techl...@techlady.com Date: Sat, 23 May 2015 19:04:59 +0200 From: Carl von Einem c...@einem.net Organization: www.einem.net User-Agent: Mozilla/5.0
Re: [HOT] step by step recipe for iD bug reporting
Sorry, it is late for me - I always try to offer a solution rather than just shoot something down; I just hadn't got there yet. A little more of my thinking: if we put any sort of 'report bug' link onto the Tasking Manager and it's for reporting more than issues with the TM itself, then we're going to need a lot more discussion (at least with our Activation and Tech Working Groups), so it's great to see some mock-ups, but without more time to really look at the logistics - if it basically sends an email - then that isn't going to fix problems that we will surely get like 'the website is down', how to I get the building plug-in for JOSM, etc. My 'solution', and just to make sure everyone is aware of the 'official' OSM Help site: https://help.openstreetmap.org/ - we could definitely add a link to there on the TM. Cheers, =Russ -Original Message- From: Suzan Reed [mailto:su...@suzanreed.com] Sent: Saturday, May 23, 2015 11:29 PM To: Russell Deffner Subject: Re: [HOT] step by step recipe for iD bug reporting Hey Russ and all, The form can be programmed to go to the right team automatically depending on which radio button is selected (iD, JOSM, or Other. See the rough I sent. It's a straight forward programming line - radio1=JOSMteam (email address or web address etc.). Something like that! Suzan On May 23, 2015, at 9:51 PM, Russell Deffner wrote: Never mind, think I answered my own question; so my opinion – if the idea is that anyone can ‘report a bug’ they find on any OSM tool/platform to the HOT volunteers coordinating the response who then triage and report to the proper place – that is not going to happen, sorry. =Russ From: Russell Deffner [mailto:russell.deff...@hotosm.org] Sent: Saturday, May 23, 2015 10:12 PM To: 'Clifford Snow'; 'Charlotte Wolter' Cc: 'HOT' Subject: RE: [HOT] step by step recipe for iD bug reporting How would the report then get to the proper place? =Russ From: Clifford Snow [mailto:cliff...@snowandsnow.us] Sent: Saturday, May 23, 2015 8:16 PM To: Charlotte Wolter Cc: HOT Subject: Re: [HOT] step by step recipe for iD bug reporting On Sat, May 23, 2015 at 5:00 PM, Charlotte Wolter techl...@techlady.com wrote: Right. It should be clarified. Problem with iD or JSOM As for what else is needed, that is up to those who know how to fix either. Maybe the button above should lead to two choices: iD or JOSM, at which point the appropriate questionnaire appears. Does JOSM include a way to report issues? To my knowledge, iD does not. Clearly they need to be separate. JOSM bugs are reported on the josm.openstreetmap.de website. One the main JOSM page are the instructions: Found a bug? | Have an idea? | Make a suggestion? • Please report any bug found: Create a new ticket using the Report Bug entry in the main menu Help. Alternatively, the same function is available under About and Show status report. • Discuss ideas and suggestions also in the bug tracker, on the josm-dev mailing list, or on the #josm IRC channel. JOSM is sold as an advanced editor which might give the impress that someone steps up from iD to JSOM. From what I've seen on HOT, for some tasks it is the preferred editor which means that new mappers are using JOSM. If they come from an open source, ie linux, background I don't see any real roadblocks to creating bug reports. But for the vast majority it is somewhat intimidating. One solution is to report the bug on the Tasking Manager for the task owner to verify. If it is a bug, the task owner reports the bug on the josm website. That allows the owner to triage the reports to make sure that they weed out user/training issues. I'm inclined to suggest modifying the TM interface to include these issues. What does everyone else think? Clifford -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot ___ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
