Wikidata:Property proposal/Humanitarian OpenStreetMap Tasking Manager project ID
Jump to navigation
Jump to search
Humanitarian OpenStreetMap Tasking Manager project ID
[edit]Originally proposed at Wikidata:Property proposal/Generic
Description | identifier for a project in the Humanitarian OpenStreetMap Tasking Manager |
---|---|
Represents | HOT Tasking Manager (Q100511474) |
Data type | External identifier |
Domain | geographic region (Q82794), disaster (Q3839081), warfare and armed conflicts (Q71266556) |
Allowed values | [1-9]\d* |
Example 1 | 2013 Lushan earthquake (Q11547847) → 236 |
Example 2 | Cyclone Amphan (Q94694597) → 8723 |
Example 3 | 2013 Aceh earthquake (Q13593376) → 272 |
Example 4 | Niokolo-Koba National Park (Q679891) → 721 |
Example 5 | Kunduz (Q108155) → 199 |
Number of IDs in source | ca. 9000 at the moment, growing by dozens a month |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://tasks.hotosm.org/projects/$1 |
Motivation
[edit]Many events within the scope of Wikidata:WikiProject Humanitarian Wikidata trigger crisis mapping (Q13476292) efforts, including through Humanitarian OpenStreetMap Team (Q27237385), who operate the HOT Tasking Manager (Q100511474) that catalogues cases of coordinated mapping activity. I think linking relevant Wikidata items to those Humanitarian OpenStreetMap Tasking Manager projects through a dedicated Wikidata property for their IDs would be useful. Some issues to consider:
- the mapping is often not 1:1, as there may be several mapping projects for the same or overlapping events or areas (example: buildings and roads in San Andres (Q174667))
- some of the mapping efforts are targeted at unmapped areas (example), which correlate strongly with areas that are not well-represented in Wikidata
Daniel Mietchen (talk) 01:20, 18 October 2020 (UTC)
Discussion
[edit]- Comment datatype for this would be external-id, even if it's a number/series of digits. I'm updating the proposal accordingly. --- Jura 11:15, 19 October 2020 (UTC)
- @Jura1: Thanks! --Daniel Mietchen (talk) 02:08, 20 October 2020 (UTC)
- Comment The label should reflect that it is supposed to be used on the related catastrophes item. I am not sure, how to efficiently achieve this, i.e. without making it too long. --CamelCaseNick (talk) 20:42, 26 October 2020 (UTC)
- @CamelCaseNick: I would not try to limit it that way — things like example 4 are not catastrophes. --Daniel Mietchen (talk) 00:48, 1 November 2020 (UTC)
- @Daniel Mietchen: Ah, sorry, the emphasis of comment was meant on the related and not the catastrophes, i.e. the mapping initiatives themselves don't get an item. And to avoid any confusion how the relation between the HOT project id and the item is meant to be, I just would have suggested to have label reflect this fact. --CamelCaseNick (talk) 00:58, 1 November 2020 (UTC)
- BTW .. it's missing a description. --- Jura 09:41, 1 November 2020 (UTC)
- @Daniel Mietchen: Ah, sorry, the emphasis of comment was meant on the related and not the catastrophes, i.e. the mapping initiatives themselves don't get an item. And to avoid any confusion how the relation between the HOT project id and the item is meant to be, I just would have suggested to have label reflect this fact. --CamelCaseNick (talk) 00:58, 1 November 2020 (UTC)
- @CamelCaseNick: I would not try to limit it that way — things like example 4 are not catastrophes. --Daniel Mietchen (talk) 00:48, 1 November 2020 (UTC)
- @Jura1: Description added. --Daniel Mietchen (talk) 23:21, 6 December 2020 (UTC)
- Support Seems useful. I would like to see the domain well-defined before the property is created though. Simon Cobb (User:Sic19 ; talk page) 19:27, 19 December 2020 (UTC)
- Support I've added some domains per request from @Sic19: --Dhx1 (talk) 16:36, 21 December 2020 (UTC)