-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
typhoon_2013:damage=xxx could improve the situation, but you would still have tag garbage if you don't update/delete those tags after the buildings are repaired. In any case, typhoon_2013:damage could be deleted after a certain time with a bot. I would suggest typhoon_Haiyan:damage instead, as there can be more than one typhoon in 2013, though. Cheers, Rafael. On 19/11/13 10:06, Stéphane Henriod wrote: > Hi > > the only concern I have with > > typhoon:damage=limited typhoon:damage=moderate > typhoon:damage=extensive > > is the tracking over time: how will we deal with this tag when the > next typhoon hits? We cannot assume that every single building will > be updated once rebuilt (typhoon:damage=none, e.g.). So we might > end up with an inconsistent database over time... > > what about something in the line of typhoon_2013:damage=xxx ? > > Cheers > > Stéphane > > -- "Le mot progrès n'aura aucun sens tant qu'il y aura des enfants > malheureux" -- Albert Einstein > > "A journey does not need reasons. Before long, it proves to be > reason enough in itself. One thinks that one is going to make a > journey, yet soon it is the journey that makes or unmakes you." -- > Nicolas Bouvier > > Photos de voyages, photos de montagne: http://www.henriod.info > <http://www.henriod.info/> > > > On Tue, Nov 19, 2013 at 9:50 AM, Rafael Avila Coya > <[email protected] <mailto:[email protected]>> wrote: > > Hi, > > I was merging some of the impassable roads into OSM yesterday. > > The first atribute is not useless; it's just an abbreviation of > the second. > > I was tagging "source=US NGA", but your suggestion it's ok too. I > could just change it, no problem. > > For the damage intensity, why not to use the typhoon:damage one, > that we already have? Like this: > > typhoon:damage=limited typhoon:damage=moderate > typhoon:damage=extensive > > Cheers, > > Rafael. > > On 19/11/13 04:13, Bruno Remy wrote: >> Hi, > >> NGA Files contains some attributs that we do not use in OSM >> Database. Exemple: "Damage_"="LD" "Damage_Ext"="LIMITED" or >> "MODERATE" "Production"="11/17/2013" > >> The first one is useless, so we can ignore it for importation. >> The third one can be changed to " source"="NGA Damage assessment >> report-11/17/2013" > >> But the 'Damage_Ext' provides some accurate information about >> the intensity of damage (limited/moderate/extensive) and should >> be strategic to give some priority for humanitarian help >> (healthcare) or reconstruction help (ingenneers, construction, >> etc...) > >> So : should we keep or not these tags, and if so, witch tags >> should be appropriate? > >> Suggestion : "NGA:damage_intensity"="limited" > >> Regards, > >> Bruno > > > > >> Le lundi 18 novembre 2013 12h08, Vivien Deparday >> <[email protected] <mailto:[email protected]>> a > écrit : Hi all, a bit of feedback on >> this instruction for road damage assessment that are on the >> tasks, I think they could be clarified a bit: > >> - while reviewing a post disaster task (350), I have found a >> road duplicate that had been created just to mark the damage on >> it instead of marking the existing pre-disaster road. This is >> currently not very clear in the workflow description, it says >> 'Please make a segment covering the damages and mark it' . The >> 'make' could mean create a new road or it could mean split the >> existing one to mark only the affected part of the roads. I >> suppose it is the latter but it could be made a bit clearer like >> it is written in capital for the buildings. > >> - Also, it is not very clear how the road obstacle and the >> impassable section should be marked and related to each other. >> Do you mark the whole road as impassable from one road block to >> the other but then you do really need to mark the road blocks >> themselves? I suppose it would still be useful to mark them if >> they are road blocks that are in the middle of an impassable >> section because then one can know how many debris have to be >> removed. If there is a section of road between two road blocks >> that had no debris, should it be marked passable or impassable >> (since you cannot get to it), etc...? It seems like all the road >> blocks should be added to the existing roads as new nodes >> belonging to the road and marked as barrier, and also each >> segment between the road blocks should be marked as impassable? >> It seems like that shouldn't mess the database? Anyone with more >> experience on that? > >> Once there is agreement, it should be described clearly on the >> workflow tab, maybe with a link to a wikipage with more details. > >> I just had a look at the shapefile from NGA and they are only >> road segment marked as impassable. > >> Cheers, > >> Vivien GFDRR Labs > > >> On Mon, Nov 18, 2013 at 10:33 AM, Pierre Béland >> <[email protected] > <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>>> wrote: > >> Hi all, > >> The tags to be used for tagging roads are described in the >> Workflow panel of Task Manager job >> http://tasks.hotosm.org/job/350 > >> If any questions, dont hesitate to contact us or come discuss on >> the #HOT Irc. > >> Thanks to all, > >> Pierre > > > > _______________________________________________ HOT mailing list > [email protected] <mailto:[email protected]> > https://lists.openstreetmap.org/listinfo/hot > > - -- Twitter: http://twitter.com/ravilacoya - -------------------------------- Por favor, non me envíe documentos con extensións .doc, .docx, .xls, .xlsx, .ppt, .pptx, aínda podendoo facer, non os abro. Atendendo á lexislación vixente, empregue formatos estándares e abertos. http://es.wikipedia.org/wiki/OpenDocument#Tipos_de_ficheros -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBAgAGBQJSizafAAoJEB3niTly2pPQvH4P/AzQ1jPPAcJp4JQs6f/+c6fB VubBCWaTgfd7QDNWDWpsG+budeBr9LJxA9BtCpKEwJ5Jp7TXRVBSmSMQ4ynhJzwe ikUBVAy3HBkbwFkD3NvPMZ+3ww5Wr93NVtnGkwwcwTtIztPIRkZKWX7Kaue/vX8v Qs+tLK6v/gu21FcuybzSEXRlSTeav2gDwv4v9IlIYtlu5QfU7gcQayTqh4duyBZe DX3ZI/80ealfp8fUewJiEMHpXGAeCBnZHFhiHP3NnOSHZsKq/LfDU0Lq8QMNhwwi 2mLJ29oT9uSEt3IXUoamDiXSwnzGCXMzZPlgDGDfTXapAXCLiWVISzXU4QuEU7qY sZytEy01taNg01/Rq8pcR0nzVPbrF8Atag8Ya2ZDCM2jjIPjq5Okb0V6Y8dE1hsO 95PZeRWSeCbMN76kuxu3+dkSDXvHYynyzoH/+AKxkPwEHioo2mxP9xloXz3FdCcr hYgK4jyMdkf/BZ2dcoli2T+XMnzDDo+dKuyqm8MSmIwdpAWAXRB3PCoI6Yn27ZgT ih0y6dTr0DOicyfzdrpwziiBR4yCiuwdx/HVjMzlv74QwjVu3mU63mcCVxvz0Szh EkMH6rV3AM+1HS3DgciXpB3BFjF7RoeNAVjgobO/ACVd/xdr4V3MiwEkeMbvNU8U eyqiMYGw+YjVDrHIED4w =EQoG -----END PGP SIGNATURE----- _______________________________________________ HOT mailing list [email protected] https://lists.openstreetmap.org/listinfo/hot
