Hi Bryce:
Have you ever done any single task of any Tasking Manager project?
From your comments, it seems you are completely wrong on what the Tasking
Manager is about.
Cheers,
Rafael.
El 24 de mayo de 2015 02:55:17 CDT, Bryce Nesbitt bry...@obviously.com
escribió:
On Sun, May 24, 2015 at
On Sun, May 24, 2015 at 2:34 AM, Rafael Avila Coya ravilac...@gmail.com
wrote:
Hi Bryce:
Have you ever done any single task of any Tasking Manager project?
From your comments, it seems you are completely wrong on what the Tasking
Manager is about.
Cheers,
Rafael.
Why, yes I have used the
There is an organization already tracking crowd-sourced reports of needed
repairs, SeeClickFix. I have used this to report issues such as blocked
street drains. The local Public Works department monitors these reports and
marks them closed once the needed repairs have been done.
On May 24,
On Fri, May 22, 2015 at 3:54 AM, Richard Z. ricoz@gmail.com wrote:
On Thu, May 21, 2015 at 09:52:06PM -0700, Bryce Nesbitt wrote:
Note that just because you can collect some data, does not make it a good
idea to put in OSM. Maintenance is harder than collection: and who's
going
to go
On Fri, May 22, 2015 at 5:02 AM, Blake Girardot bgirar...@gmail.com wrote:
The intention of the damage:event=* or maybe disaster:event=* tag doesn't
have much to do with assigning causation, and has more to do with tag
maintenance. We want to be able to run projects that get objects that were
On 24/05/2015 5:09 PM, Bryce Nesbitt wrote:
On Fri, May 22, 2015 at 3:54 AM, Richard Z. ricoz@gmail.com
mailto:ricoz@gmail.com wrote:
On Thu, May 21, 2015 at 09:52:06PM -0700, Bryce Nesbitt wrote:
Note that just because you can collect some data, does not make
it a good
On 24/05/2015 5:10 PM, Bryce Nesbitt wrote:
On Fri, May 22, 2015 at 5:02 AM, Blake Girardot bgirar...@gmail.com
mailto:bgirar...@gmail.com wrote:
The intention of the damage:event=* or maybe disaster:event=* tag
doesn't have much to do with assigning causation, and has more to
do
On Sun, May 24, 2015 at 12:22 AM, Warin 61sundow...@gmail.com wrote:
Because it become available to others .. like the government/local
authorities who may be in charge of repairs?
Crowd source databases are not appropriate sources for government/local
action at that level. Were there
Hi,
On 05/22/2015 06:12 AM, Blake Girardot wrote:
OSM is about mapping what is important to people
AND on the ground. Important alone doesn't suffice.
and believe me, if the
only bridge for 50km is out that is important to me and others.
Yes, of course. If there is no bridge left at all
Am 22.05.2015 um 09:04 schrieb Frederik Ramm frede...@remote.org:
Yes, of course. If there is no bridge left at all then we'd simply
delete - or refrain from mapping - the bridge (rather than create an
object saying there was a bridge but it's gone now).
Incidentally this means that
On 22/05/2015 8:54 PM, Richard Z. wrote:
On Thu, May 21, 2015 at 09:52:06PM -0700, Bryce Nesbitt wrote:
Note that just because you can collect some data, does not make it a good
idea to put in OSM. Maintenance is harder than collection: and who's going
to go back three years after the HOT
On Thu, May 21, 2015 at 09:52:06PM -0700, Bryce Nesbitt wrote:
Note that just because you can collect some data, does not make it a good
idea to put in OSM. Maintenance is harder than collection: and who's going
to go back three years after the HOT event and clean up?
same is even worse with
On 22/05/2015 5:32 PM, Martin Koppenhoefer wrote:
Am 22.05.2015 um 09:04 schrieb Frederik Ramm frede...@remote.org:
Yes, of course. If there is no bridge left at all then we'd simply
delete - or refrain from mapping - the bridge (rather than create an
object saying there was a bridge but
On Thu, May 21, 2015 at 09:36:10PM +0200, Andreas Goss wrote:
As you linked to this on the HOT list a few things noticed...
What about the typhoon:, earthquake: or tsunami: tags? Replaced with
damage:event?
What about e.g. damage:building? This could still be used even if you have
These replies are all very helpful, thank you very much.
On 5/22/2015 9:04 AM, Frederik Ramm wrote:
Whether the bridge was broken by a hurricane or an earthquake or in a
war, will often not be easy to discern on the ground. Therefore I view a
tag that details the event which broke the bridge,
2015-05-22 12:14 GMT+02:00 Warin 61sundow...@gmail.com:
Much quicker and cheaper to repair/replace sections that are damaged than
place a new road + bridges elsewhere.
yes, also because typically there has been a reason why a certain spot has
been chosen for the bridge (topography, river
I don't know Andreas, do we need to say what kind of event it is?
I would lean toward damage:type=hurricane|earthquake|etc
or event:type=hurricane|earthquake|etc
But this actually brings up an issue that we ran into in Nepal.
How do identify the event (and maybe event type) independent of
I feel this is a good example of a database that should use
OSM as a base layer.
A rendering engine can match a given primary key for, say, a building
outline
to the given damage assessment tag.
---
Damage assessment data is very transitory, compared to the lifetime of
objects in OSM.
Damage info has been tagged in OSM for a long time.
OSM already tags a lot of temporary and transient stuff.
We are aware of the nature of the tags and want to be able to review,
maintain the remove the tags, it is one of the main goals of any tagging
system we settle on like that.
On
On Thu, May 21, 2015 at 1:46 PM, Blake Girardot bgirar...@gmail.com wrote:
Damage info has been tagged in OSM for a long time.
OSM already tags a lot of temporary and transient stuff.
We are aware of the nature of the tags and want to be able to review,
maintain the remove the tags, it is
Hi, Bryce:
Everything is temporary: the highway surfaces, oneway, classification...
Railways go disused and new ones are constructed every day.
Thousands of shops close everyday, to reopen with a new name and type (and
contact:*...)
Farmlands go greenfields, then construction, then
On Thu, May 21, 2015 at 3:52 PM, Rafael Avila Coya ravilac...@gmail.com
wrote:
Hi, Bryce:
Yes. Everything is temporary. So whatever we do in OSM for temporary
objects has to be applied to ALL objects.
We don't store the number of chickens found in each compound.
We do store railways, the
On 5/22/2015 1:43 AM, Bryce Nesbitt wrote:
On Thu, May 21, 2015 at 3:52 PM, Rafael Avila Coya ravilac...@gmail.com
mailto:ravilac...@gmail.com wrote:
Hi, Bryce:
Yes. Everything is temporary. So whatever we do in OSM for temporary
objects has to be applied to ALL objects.
We don't
Note that just because you can collect some data, does not make it a good
idea to put in OSM. Maintenance is harder than collection: and who's going
to go back three years after the HOT event and clean up?
-
Keep in mind this tagging mailing list is a tiny and non-representative
As you linked to this on the HOT list a few things noticed...
What about the typhoon:, earthquake: or tsunami: tags? Replaced with
damage:event?
What about e.g. damage:building? This could still be used even if you
have building= and damage=
What about the status= and impassable= keys and
Greetings everyone,
I am looking to help further develop a set of tags to reflect disaster
event damage to mapped objects in OSM. OSM has already used damage
tags in the past several times for example after Typhoon Haiyan:
http://wiki.openstreetmap.org/wiki/Damaged_buildings_crisis_mapping
And
26 matches
Mail list logo
