Re: [talk-au] Maxar bushfire imagery

2020-01-17 Thread Warin

On 17/1/20 10:08 pm, Mateusz Konieczny wrote:




17 Jan 2020, 11:42 by andrew.harv...@gmail.com:

I'm all for using the lifecycle prefix,
https://wiki.openstreetmap.org/wiki/Lifecycle_prefix. I agreed
that if there's still remains there use ruined or destroyed, not
sure what the difference is though.

ruined implies that ruins still remain, destroyed may mean that or 
that there is no trace at all


in practice difference is minor if any


Most of these will still have foundations in place, they may not be fit 
for reuse but they are there. Some fire places and chimneys too remain.


I'll use ruined. Unless there are other ideas?



Once it's been cleared you could use demolished, removed or raised

Probably razed, not raised. I see not real difference.

, again not sure what the difference is. While damaged is not
documented it seems the perfect fit since there is no other
suitable tag for this on the wiki.

damaged seems to me a poor fit as prefix, damaged building is still a 
building,

and I would expect building=something tag to be used.



By damaged I mean part of the building is intact but another part has 
been damaged .. e.g. a truck has run part way through the building.





___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au


Re: [talk-au] Maxar bushfire imagery

2020-01-17 Thread Warin

On 17/1/20 9:42 pm, Andrew Harvey wrote:
On Fri, 17 Jan 2020 at 19:53, Warin <61sundow...@gmail.com 
> wrote:


I have tagged some buildings that have been fire damaged to a
large degree.
I have used building=razed however I think this is wrong.

I think the lifecycle prefix should be used.

The choices are;

ruins:*

or

destroyed:*

Thoughts?

I note there is the possibility of partial damage. A new tag of
damaged:* might be of use?


I'm all for using the lifecycle prefix, 
https://wiki.openstreetmap.org/wiki/Lifecycle_prefix. I agreed that if 
there's still remains there use ruined or destroyed, not sure what the 
difference is though. Once it's been cleared you could use demolished, 
removed or raised, again not sure what the difference is. While 
damaged is not documented it seems the perfect fit since there is no 
other suitable tag for this on the wiki.


You'd probably need local knowledge to know all this, from the Maxar 
imagery you can see houses and trace them not sure how easy it will be 
to see destroyed houses though, will need to wait for the post event 
imagery to come out.



I have used imagery from press reports. As I am not copying the image I 
think that is ok.


For tracing in NSW I used the LPI Imagery.


___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au


Re: [talk-au] Maxar bushfire imagery

2020-01-17 Thread Graeme Fitzpatrick
Thanks for putting these up Andrew.

The silly question though is how do we use them? :-)

Thanks

Graeme
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au


Re: [talk-au] Maxar bushfire imagery

2020-01-17 Thread Mateusz Konieczny



17 Jan 2020, 11:42 by andrew.harv...@gmail.com:

> I'm all for using the lifecycle prefix, > 
> https://wiki.openstreetmap.org/wiki/Lifecycle_prefix> . I agreed that if 
> there's still remains there use ruined or destroyed, not sure what the 
> difference is though.
>
ruined implies that ruins still remain, destroyed may mean that or that there 
is no trace at all

in practice difference is minor if any

>  Once it's been cleared you could use demolished, removed or raised
>
Probably razed, not raised. I see not real difference.

> , again not sure what the difference is. While damaged is not documented it 
> seems the perfect fit since there is no other suitable tag for this on the 
> wiki.
>
damaged seems to me a poor fit as prefix, damaged building is still a building,
and I would expect building=something tag to be used.

___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au


Re: [talk-au] Maxar bushfire imagery

2020-01-17 Thread Andrew Harvey
On Fri, 17 Jan 2020 at 19:53, Warin <61sundow...@gmail.com> wrote:

> I have tagged some buildings that have been fire damaged to a large degree.
> I have used building=razed however I think this is wrong.
>
> I think the lifecycle prefix should be used.
>
> The choices are;
>
> ruins:*
>
> or
>
> destroyed:*
>
> Thoughts?
>
> I note there is the possibility of partial damage. A new tag of damaged:*
> might be of use?
>

I'm all for using the lifecycle prefix,
https://wiki.openstreetmap.org/wiki/Lifecycle_prefix. I agreed that if
there's still remains there use ruined or destroyed, not sure what the
difference is though. Once it's been cleared you could use demolished,
removed or raised, again not sure what the difference is. While damaged is
not documented it seems the perfect fit since there is no other suitable
tag for this on the wiki.

You'd probably need local knowledge to know all this, from the Maxar
imagery you can see houses and trace them not sure how easy it will be to
see destroyed houses though, will need to wait for the post event imagery
to come out.
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au


Re: [talk-au] Maxar bushfire imagery

2020-01-17 Thread Andrew Harvey
On Fri, 17 Jan 2020 at 20:45, Andy Mabbett 
wrote:

> On Fri, 17 Jan 2020 at 06:56, Andrew Harvey 
> wrote:
>
> > Maxar have generously donated some satellite imagery of bushfire affected
> > areas and they explicitly allow tracing for OSM,
> >
> >
> https://blog.maxar.com/open-data-program/2020/open-data-response-to-the-australian-wildfires
> .
>
> There's nothing explicitly about OSM on that page and the licence is
> stated (despite a claim of "open data") as "Creative Commons
> Attribution Non-Commercial 4.0 license (CC BY-NC 4.0). This licensing
> allows for non-commercial use of the information..."
>
> Have I missed something?
>

Yeah so if you click through to the landing page
https://www.digitalglobe.com/ecosystem/open-data/australia-wildfires and
then click the License button and then scroll down to see the OpenStreetMap
Exception.


> In the licensing terms, DigitalGlobe has a stated exception for
> OpenStreetMap. OSM is allowed to use imagery released under the Open Data
> Program. Even though OSM enables commercial usage, OSM is a critical
> platform for the disaster response community. Allowing usage of our imagery
> in OSM will enable faster data access by local communities as well as
> global relief efforts.
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au


Re: [talk-au] Maxar bushfire imagery

2020-01-17 Thread Andy Mabbett
On Fri, 17 Jan 2020 at 06:56, Andrew Harvey  wrote:

> Maxar have generously donated some satellite imagery of bushfire affected
> areas and they explicitly allow tracing for OSM,
>
> https://blog.maxar.com/open-data-program/2020/open-data-response-to-the-australian-wildfires.

There's nothing explicitly about OSM on that page and the licence is
stated (despite a claim of "open data") as "Creative Commons
Attribution Non-Commercial 4.0 license (CC BY-NC 4.0). This licensing
allows for non-commercial use of the information..."

Have I missed something?

___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au


Re: [talk-au] Maxar bushfire imagery

2020-01-17 Thread Warin

I have tagged some buildings that have been fire damaged to a large degree.
I have used building=razed however I think this is wrong.

I think the lifecycle prefix should be used.

The choices are;

ruins:*

or

destroyed:*

Thoughts?

I note there is the possibility of partial damage. A new tag of 
damaged:* might be of use?


On 17/1/20 5:56 pm, Andrew Harvey wrote:
Maxar have generously donated some satellite imagery of bushfire 
affected areas and they explicitly allow tracing for OSM, 
https://blog.maxar.com/open-data-program/2020/open-data-response-to-the-australian-wildfires. 



So far they haven't released any post event imagery but I'll try to 
keep an eye for updates (should out if you see any), I'm sure they'll 
start flowing in. In the meantime I've loaded pre event imagery going 
back to June 2019.


The URLs for JOSM / iD (exclude the "tms:", start with the "https") are

2019-06-15 
tms:https://{switch:a,b,c,d}.tiles.mapbox.com/v4/openstreetmapau.10300100921A2B00/{zoom}/{x}/{y}.jpg?access_token=pk.eyJ1Ijoib3BlbnN0cmVldG1hcGF1IiwiYSI6ImNqbWl3bXZ6aDA0MTkzd21xdnV1d2k0azEifQ.HYkMOqH_E2fYd1b0oXRe6w 

2019-06-15 
tms:https://{switch:a,b,c,d}.tiles.mapbox.com/v4/openstreetmapau.1030010093328400/{zoom}/{x}/{y}.jpg?access_token=pk.eyJ1Ijoib3BlbnN0cmVldG1hcGF1IiwiYSI6ImNqbWl3bXZ6aDA0MTkzd21xdnV1d2k0azEifQ.HYkMOqH_E2fYd1b0oXRe6w 

2019-07-01 
tms:https://{switch:a,b,c,d}.tiles.mapbox.com/v4/openstreetmapau.104001004E982900/{zoom}/{x}/{y}.jpg?access_token=pk.eyJ1Ijoib3BlbnN0cmVldG1hcGF1IiwiYSI6ImNqbWl3bXZ6aDA0MTkzd21xdnV1d2k0azEifQ.HYkMOqH_E2fYd1b0oXRe6w 

2019-07-13 
tms:https://{switch:a,b,c,d}.tiles.mapbox.com/v4/openstreetmapau.1050010017610F00/{zoom}/{x}/{y}.jpg?access_token=pk.eyJ1Ijoib3BlbnN0cmVldG1hcGF1IiwiYSI6ImNqbWl3bXZ6aDA0MTkzd21xdnV1d2k0azEifQ.HYkMOqH_E2fYd1b0oXRe6w 

2019-07-14 
tms:https://{switch:a,b,c,d}.tiles.mapbox.com/v4/openstreetmapau.105001001769C500/{zoom}/{x}/{y}.jpg?access_token=pk.eyJ1Ijoib3BlbnN0cmVldG1hcGF1IiwiYSI6ImNqbWl3bXZ6aDA0MTkzd21xdnV1d2k0azEifQ.HYkMOqH_E2fYd1b0oXRe6w 

2019-07-14 
tms:https://{switch:a,b,c,d}.tiles.mapbox.com/v4/openstreetmapau.105001001769C600/{zoom}/{x}/{y}.jpg?access_token=pk.eyJ1Ijoib3BlbnN0cmVldG1hcGF1IiwiYSI6ImNqbWl3bXZ6aDA0MTkzd21xdnV1d2k0azEifQ.HYkMOqH_E2fYd1b0oXRe6w 

2019-07-23 
tms:https://{switch:a,b,c,d}.tiles.mapbox.com/v4/openstreetmapau.103001009793C100/{zoom}/{x}/{y}.jpg?access_token=pk.eyJ1Ijoib3BlbnN0cmVldG1hcGF1IiwiYSI6ImNqbWl3bXZ6aDA0MTkzd21xdnV1d2k0azEifQ.HYkMOqH_E2fYd1b0oXRe6w 

2019-07-24 
tms:https://{switch:a,b,c,d}.tiles.mapbox.com/v4/openstreetmapau.1050010017841E00/{zoom}/{x}/{y}.jpg?access_token=pk.eyJ1Ijoib3BlbnN0cmVldG1hcGF1IiwiYSI6ImNqbWl3bXZ6aDA0MTkzd21xdnV1d2k0azEifQ.HYkMOqH_E2fYd1b0oXRe6w 

2019-08-02 
tms:https://{switch:a,b,c,d}.tiles.mapbox.com/v4/openstreetmapau.103001009840FE00/{zoom}/{x}/{y}.jpg?access_token=pk.eyJ1Ijoib3BlbnN0cmVldG1hcGF1IiwiYSI6ImNqbWl3bXZ6aDA0MTkzd21xdnV1d2k0azEifQ.HYkMOqH_E2fYd1b0oXRe6w 

2019-08-13 
tms:https://{switch:a,b,c,d}.tiles.mapbox.com/v4/openstreetmapau.103001009646FC00/{zoom}/{x}/{y}.jpg?access_token=pk.eyJ1Ijoib3BlbnN0cmVldG1hcGF1IiwiYSI6ImNqbWl3bXZ6aDA0MTkzd21xdnV1d2k0azEifQ.HYkMOqH_E2fYd1b0oXRe6w