1-01-01 Addition of variable definitions (part 2: lightning) #391

fstuerzl · 2022-04-29T09:34:58Z

Proposal Summary

Please consult the Guidance and use the following structure for new issues. Note, the content in this initial comment box is subject to modification to document the final decisions or to provide more details as needed.

Summary and Purpose

Add definitions to lightning variables.

Proposal

(definitions updated)

notation	path	name	description
new	\Atmosphere\Lightning\Total lightning (flash) density	Total lightning (flash) density	Total number of detected flashes in the corresponding time interval and space unit. Note: The space unit (grid box) should be equal to the horizontal resolution and the accumulation time to the observing cycle
new	\Atmosphere\Lightning\Lightning (flash) density cloud-to-ground	Lightning (flash) density cloud-to-ground	Number of detected cloud-to-ground flashes in the corresponding time interval and space unit. Note:
258	\Atmosphere\Lightning\Lightning discharge polarity	Lightning discharge polarity	Polarity of the charge effectively lowered to ground during a lightning discharge.
259	\Atmosphere\Lightning\Lightning discharge rates	Lightning discharge rates	Number of lightning discharges per unit time in a given region (e.g. world-wide) or for a given storm system (e.g. a thunderstorm cell).
260	\Atmosphere\Lightning\Lightning discharge type (cloud to cloud, cloud to surface)	Lightning discharge type (cloud to cloud, cloud to surface)	Lightning discharge type, defined by the path of the lightning discharge: between two clouds or the same cloud (intra-cloud) or between cloud and ground (cloud-to-ground).
432	\Atmosphere\Lightning\Position\Lightning direction from station	Lightning direction from station	Azimuth of the lightning event with respect to the corresponding station.
433	\Atmosphere\Lightning\Position\Lightning distance from station	Lightning distance from station	Distance of the lightning event from the corresponding station.

new

(supersedes current 257)

notation	path	name	description
tbd	\Atmosphere\Lightning\Lightning discharge current	Lightning discharge current	Current incurred by the lightning discharge.

deprecate

notation	path	name	description
257	\Atmosphere\Lightning\Lightning discharge energy	Lightning discharge energy

Reason

Every entry in the WMDR code lists should have a useful definition.

Stakeholder(s)

[include names and emails or handles of individuals or groups that introduced the proposal]

Consultations

@sibalm (Simone Balmelli, MeteoSwiss)

@hpohjolawmo (Heikki, WMO)

@gaochen-larc (Will Mc Carty)

@tjlang (Timothy Lang)

@deeplycloudy (Eric Bruning)

@... (Steve Goodman)

@... (Pekka Rossi)

Context

[include references to manuals or guides that are reviewed to ensure alignment, if proposal differs then document how and why]

Expected Impact of Change

LOW

fstuerzl · 2022-04-29T09:54:05Z

Variables 12001 and 12002 are included in OSCAR/Requirements, so I suggest to use the definitions provided there:

Name	Definition
Total lightning density	Total number of detected flashes in the corresponding time interval and the space unit. The space unit (grid box) should be equal to the horizontal resolution and the accumulation time to the observing cycle
Cloud to Ground lightning density	Number of detected cloud-to-ground flashes in the corresponding time interval and the space unit. The space unit (grid box) should be equal to the horizontal resolution and the accumulation time to the observing cycle

joergklausen · 2022-05-20T10:20:18Z

I have reached out to a colleague on this one.

https://library.wmo.int/?lvl=notice_display&id=220 may also contain some useful descriptions.

JohnEyre · 2022-05-24T13:02:10Z

OSCAR/Requirements currently contains two lightning variables:

total lightning density,
cloud to ground lightning density.
So there is a clear match here, and the only issue is the ordering of the words in the variable name.

sibalm · 2022-05-30T07:21:57Z

This is a proposal for the descriptions

notation	path	name	description
12001	\Atmosphere\Lightning\Total lightning density	Total lightning density	Total number of detected flashes in the corresponding time interval and space unit.
12002	\Atmosphere\Lightning\Lightning density cloud-to-ground	Lightning density cloud-to-ground	Number of detected cloud-to-ground flashes in the corresponding time interval and space unit.
257	\Atmosphere\Lightning\Lightning discharge energy	Lightning discharge energy	Energy released by the lightning discharge.
258	\Atmosphere\Lightning\Lightning discharge polarity	Lightning discharge polarity	Polarity of the charge effectively lowered to ground during a lightning discharge.
259	\Atmosphere\Lightning\Lightning discharge rate	Lightning discharge rate	Number of lightning discharges per unit time in a given region (e.g. world-wide) or for a given storm system (e.g. a thunderstorm cell)
260	\Atmosphere\Lightning\Lightning discharge type (intra-cloud, cloud-to-ground)	Lightning discharge type (intra-cloud, cloud-to-ground)	Lightning discharge type, defined by the path of the lightning discharge: between two clouds or the same cloud (intra-cloud) or between cloud and ground (cloud-to-ground).
432	\Atmosphere\Lightning\Position\Lightning direction from station	Lightning direction from station	Azimuth of the lightning event with respect to the corresponding station
433	\Atmosphere\Lightning\Position\Lightning distance from station	Lightning distance from station	Distance of the lightning event from the corresponding station

sibalm · 2022-05-30T07:23:46Z

And here are some further comments:

12001-12002) Optionally, we may replace the name "Total lightning density" by "Total lightning flash density", and "Lightning density cloud-to-ground" by "Cloud-to-ground lightning flash density", to make it clear we are speaking of flashes.
The sentence: "The space unit (grid box) should be equal to the horizontal resolution and the accumulation time to the observing cycle"
may not be appropriate for lightning data. Indeed, lightning data do not have a uniquely defined horizontal resolution (the localization accuracy varies for each event)
nor observing cycle (lightning events are detected in real time).
So, there is no unique space and time unit for defining the lighting density.
A typical definition of lightning density is #events/km^2/min
A last comment: we may also consider adding "lighing discharge" densities; in this case, we don't speak of flashes anymore, but of their subcomponents (strokes and pulses). These correspond e.g. to the lightning events that are plotted in NinJo.

257-) Lightning energy is difficult to measure, and is not, for instance, part of the data we receive from Météorage. Instead, we receive the measurement of the lightning current intensity (measured in kA).
It may be meaningful to add the current intensity as a new voice of the lightning vocabulary, or even to replace the lightning energy by it.

259-) As you see by the description, the concept of "lighting discharge rate" is not unique, as it can be applied to different contexts (regions, thunderstorm cells,...).
Does it makes sense to keep this voice? Or shall we specify it better?

432-433) We may replace "lightning" by "lightning discharge", so that it is clear we are not speaking of lightning flashes.
Notice: we receive lightning data on the whole COSMO-Alps domain. The stations mentioned here (I presume, in our case, Swissmetnet stations), are not responsible for the lightning detection
(instead, a network of Météorage antennas makes the detection).
For historical and climatological reasons, we however classify lightning data depending on the distance from each SwissMetNet station.
I cannot judge whether it makes sense to keep these voices here, but it must be clear that these parameters are somehow "artificial".

Best regards,

Simone Balmelli

JohnEyre · 2022-05-30T09:35:16Z

@sibalm @joergklausen @amilan17 . Thanks for these explanations. I suggest that we also check with experts on lightning imagery from satellites, as I know that the processing of these data (and hence potentially the data dissemination) uses many of these concepts. WMO Space Programme will have the appropriate contacts.

amilan17 · 2022-09-22T13:58:39Z

https://github.com/wmo-im/tt-wigosmd/wiki/Meeting-2022.09.22 notes:

@joergklausen will work on this
@amilan17 ask Heikki to help find someone from the space-based lightning community to review
@gaochen-larc can reach out to Will McCarty

amilan17 · 2022-10-06T12:41:44Z

https://github.com/wmo-im/tt-wigosmd/wiki/2022.10.06-TT-WIGOSMD meeting notes:

no progress yet

amilan17 · 2022-10-06T14:12:05Z

Steve Goodman from NOAA can provide some feedback after October

joergklausen · 2022-10-19T09:39:32Z

Definitions provided by @sibalm make sense. Still need to agree on remaining comments, paraphrased here:

12001: Optionally, replace the name "Total lightning density" by "Total lightning flash density"
12002: Optionally, replace "Lightning density cloud-to-ground" by "Cloud-to-ground lightning flash density", to make it clear we are speaking of flashes.
(new) Also consider adding "lightning discharge" densities; in this case, we don't speak of flashes anymore, but of their subcomponents (strokes and pulses).
257: Supersede "Lightning energy" by (new) "Lightning current intensity" (measured in kA).
259: The concept of "lighting discharge rate" is not unambiguous, as it can be applied to different contexts (regions, thunderstorm cells,...). Does it makes sense to keep it? Or is there a need for better specification?
432: Suggestion to replace "lightning" by "lightning discharge", so that it is clear we are not speaking of lightning flashes.
433: Suggestion to replace "lightning" by "lightning discharge", so that it is clear we are not speaking of lightning flashes.

Need comments from @hpohjolawmo and @gaochen-larc (Will Mc Carty) and @joergklausen (Urs Germann)

joergklausen · 2022-11-03T14:20:57Z

I reached out to Urs Germann, but he doesn't feel compenent enough to provide additional insight.

amilan17 · 2022-11-03T14:21:10Z

https://github.com/wmo-im/tt-wigosmd/wiki/2022.11.03-TT-WISOSMD notes:
@amilan17: Heikki will provide some feedback soon

amilan17 · 2022-11-17T16:48:38Z

@sibalm thank you for your contributions to the definitions of these proposals. Can you please update your profile with your full name and affiliation? I like to document who has contributed to proposals for amendments when submitting for approval. Thanks. Anna (WMO Secretariat)

joergklausen · 2022-11-22T09:52:53Z

Proposal updated. Need review by @hpohjolawmo (Heikki) and @gaochen-larc (Will McCarthy)

amilan17 · 2022-11-22T09:59:31Z

@joergklausen I don't see any changes in the proposal summary. Am I missing something?

joergklausen · 2022-11-22T11:18:03Z

@joergklausen I don't see any changes in the proposal summary. Am I missing something?

I had to redo this, left the page before updating, apparently ...

amilan17 · 2022-11-22T14:08:25Z

Review from Heikki, Steve Goodman and Pekka Rossi

**

According to GitHub thread is not clear what was the reason for the proposed change of 12001 and 12002 from “total lightning density” to “total lightning flash density”. This is causing an issue for the existing measurement when total lightning density is not always based only on flash measurements. Thus, we think it is better to keep it as it is, or then create additional codes for all total densities based on all variables.
Also, existing codes are based on the ground based lightning detection systems and they are not supporting space-based measurements. Additional codes should be created to support space-based lightning detection. It should take into account pulses, events, groups and flashes. It should also cover the optical energy measured by space based lightning detection system. However, The fundamental idea that WMDR codes are technology independent should be kept in mind.
We propose additional review to be done for entire code library related to lighting detection before any changes, and then to create the next version of the codes supporting all existing lighting detection technologies.

**

and

**

If your objective is to system agnostic then perhaps fewer codes is better, for example,

Ground based RF space-based optical
Stroke…..…………………… group
Pulse ………………………… event
Flash …………………………. Flash
Peak current (kA)………………. Radiance (fJ)
Polarity………………………… N/A

**

amilan17 · 2022-11-22T14:16:20Z

https://github.com/wmo-im/tt-wigosmd/wiki/2022.11.22-TT-WIGOSMD notes:

@joergklausen will reach out to collaborators to see if they are willing to form a temporary editing team to finalize this proposal such that it represents sattelite and ground observations.

sibalm · 2022-11-22T14:28:46Z

@sibalm thank you for your contributions to the definitions of these proposals. Can you please update your profile with your full name and affiliation? I like to document who has contributed to proposals for amendments when submitting for approval. Thanks. Anna (WMO Secretariat)

@amilan17 I have updated my profile. Please tell me if you need more information. Thank you!

amilan17 · 2023-03-17T14:17:58Z

https://github.com/wmo-im/tt-wigosmd/wiki/2023-03-17-TT-WIGOSMD notes:
@amilan17 set up meeting with stakeholders

joergklausen · 2023-04-21T11:51:22Z

IMHO, the only way forward here is to organize this meeting suggested earlier.

amilan17 · 2023-06-01T12:43:00Z

https://github.com/wmo-im/tt-wigosmd/wiki/2023.06.01-TT-WIGOSMD notes:

no progress
@amilan17 will try to set up a meeting soon

joergklausen · 2023-09-19T13:01:32Z

@amilan17 Setup a MS Teams meeting with Tim Lang, John Eyre, Simone Balmelli, Heikki

meulenvd · 2024-02-02T13:03:08Z

@joergklausen has asked me to give this action new momentum because it seems almost solved but not really finalized. Taking notice of all the comments, I have concluded that in fact the discussion is much broader and I can split this issue into the following activities:

modification of the existing notations 12001, 12002, 258, 259, 260, 432 and 433 and replacement of 257 by a new notation
introduction of new, alternative notations
introduction of new notations in line with satellite based products because the present notations are largely associated with surface based observations
additional review to be done for the entire code library related to lighting detection to generate a more complete or better structured set; may be a complete reorganization of all lightning associated notifications.

So, in order to speed up, it may be better to finalized first activity no. 1 and than follow up with the others.

w/r 1:
For the current proposal (see on top), I think acceptance is straightforward at present. One suggestion is still open (see comment by @joergklausen: 432 (direction) and 433 (distance): Suggestion to replace "lightning" by "lightning discharge", so that it is clear we are not speaking of lightning flashes.

w/r 2:
mentioned in the comment by @deeplycloudy and @tjlang a new notation is suggested: lightning flash extent density (FED). However the notations with lightning (flash) density are comparable and distinction between a new notation and the existing ones must be clear to avoid confusion.

w/r 3:
This would be a separate activity, dedicated to experts working on lightning observations by satellites. I recommend to take note of the new (2021) Volume IV of the GIMO (WMO-No. 8) on Space-based Observations and with paragraphs describing the technology to determine and observe lightning from space. For an excerpt from this Volume on lightning, see: 8_IV_2021_en(Excerpt on Lightning).pdf

w/r 4:
A overall review of the entire code library is proposed. It will help to improve consistency, although such a review may result in a major revision of the present naming convention (flash, discharge, etc.). Although the WMDR codes should be technology free, most notations are linked to available observation techniques. So, this review will be quite a challenge and time consuming. For this activity I recommend to take note of the new version of the chapter on Lightning Detection in GIMO, Volume III (WMO-No. 8). The latest version is approved by EC-76 mid 2023, see: 8_III_6_en_LCP.pdf

So, I kindly request all contributors to give there comments on this proposal, in particular @sibalm (Simone Balmelli, MeteoSwiss), @hpohjolawmo (Heikki, WMO), @gaochen-larc (Will Mc Carty), @tjlang (Timothy Lang), and @deeplycloudy (Eric Bruning).

amilan17 · 2024-02-15T12:54:09Z

https://github.com/wmo-im/tt-wigosmd/wiki/2024.02.15-TT-WIGOSMD notes:
Jitze added a proposal in GH (see above) with no comment yet; will follow through with an email;

JREyre · 2024-02-16T10:31:54Z

@meulenvd @joergklausen @amilan17
This Issue is still in need of expert review, and I hope that contacts established by Jitze will achieve this. At the end of the day, we need a set of names and definitions that are acceptable to both space-based and surface-based observing communities, because they are both trying to provide observational information on the same geophysical phenomena. However, it would be acceptable for some variables to relate only to space-based or only to surface-based observations (and, in these cases, the definitions should make this clear).

meulenvd · 2024-02-19T22:51:12Z

@joergklausen @amilan17 @JREyre
Separate E-mail send to @sibalm @hpohjolawmo @gaochen-larc @tjlang @deeplycloudy, requesting comments, see
e-mail (2024-02-19) issue 391.pdf

amilan17 · 2024-04-09T12:22:04Z

https://github.com/wmo-im/tt-wigosmd/wiki/2024.04.09%E2%80%90TT%E2%80%90WIGOSMD notes:
@amilan17 to organize a meeting with relevant parties; John recommends just having a meeting with key experts;

amilan17 · 2024-05-06T13:43:45Z

@meulenvd and I agree to move forward with step 1 (see attached). If/when we need other codes, new amendments can be proposed at that time. The original purpose here was to add missing definitions.

lightning-issue391.docx

meulenvd · 2024-05-10T21:45:59Z

see list of steps
w/r step 2 and 3 (introduction of new or alternative notations in line with satellite based products) the following information on

Flash extent density (FED)
Average flash area (AFA) and
total optical energy (TOE)

might be of interest:

amilan17 · 2024-05-16T11:45:50Z

https://github.com/wmo-im/tt-wigosmd/wiki/2024.05.16%E2%80%90TT%E2%80%90WIGOSMD notes:
team agrees to move forward with proposal as is.

amilan17 · 2024-06-13T12:36:47Z

@joergklausen branch is updated

* update branch for issue #391 * Github Action Commit --------- Co-authored-by: Anna Milan <metadata.adds.meaning@gmail.com> Co-authored-by: joergklausen <joergklausen@users.noreply.github.com>

#391

* update branch for issue #391 (#538) * update branch for issue #391 * Github Action Commit --------- Co-authored-by: Anna Milan <metadata.adds.meaning@gmail.com> Co-authored-by: joergklausen <joergklausen@users.noreply.github.com> * 443 1 01 01 addition of definitions for cloud variables (#537) * Update 1-01-01.csv * Update 1-01-01.csv * Github Action Commit --------- Co-authored-by: Franziska Stürzl <72029328+fstuerzl@users.noreply.github.com> Co-authored-by: joergklausen <joergklausen@users.noreply.github.com> * add core and recommended (#544) * add flash definitions (#545) #391 * Github Action Commit * issue Bug: Superseded unit in WMDR code table #520 (#540) #520 * Update 1-01-01.csv editorial revision to definition of 507 * Github Action Commit * Update 1-01-01.csv editorial * Github Action Commit * Update 9-02.csv editorial * Revise datapolicy (#546) * Update 9-02.csv #475 * Update 9-02.csv * Update 9-02.csv re-order * Update 9-02.csv (#547) remove comparisons to previous data policies * Apply suggestions from code review replace issue numbers with sequential notation numbers --------- Co-authored-by: Jörg Klausen <34302947+joergklausen@users.noreply.github.com> Co-authored-by: joergklausen <joergklausen@users.noreply.github.com> Co-authored-by: Franziska Stürzl <72029328+fstuerzl@users.noreply.github.com> Co-authored-by: amilan17 <amilan17@users.noreply.github.com>

fstuerzl mentioned this issue Apr 29, 2022

1-01-x Re-concile variable lists of OSCAR/Requirements with the official WMD codelists #190

Closed

fstuerzl added the Discussion required This issues should be checked and discussed by TT-WMD. label Apr 29, 2022

This comment was marked as outdated.

Sign in to view

amilan17 added the atmosphere label May 13, 2022

amilan17 added this to the FT2023-1 milestone May 31, 2022

joergklausen self-assigned this Sep 22, 2022

amilan17 modified the milestones: FT2023-1, noTargetMilestone Nov 22, 2022

amilan17 removed this from the noTargetMilestone milestone Feb 3, 2023

amilan17 modified the milestones: FT2023-2, FT2024-1 Jun 30, 2023

amilan17 assigned JohnEyre Sep 19, 2023

amilan17 modified the milestones: FT2024-1, FT2024-2 Jan 18, 2024

meulenvd self-assigned this Feb 7, 2024

joergklausen removed their assignment Apr 9, 2024

joergklausen assigned amilan17 and unassigned JohnEyre May 16, 2024

amilan17 added a commit that referenced this issue Jun 13, 2024

update branch for issue #391

c10b2a1

joergklausen linked a pull request Jul 3, 2024 that will close this issue

update branch for issue #391 #538

Merged

amilan17 added a commit that referenced this issue Jul 3, 2024

update branch for issue #391

865c325

amilan17 added a commit that referenced this issue Aug 20, 2024

add flash definitions (#545)

3f4f7f8

#391

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

1-01-01 Addition of variable definitions (part 2: lightning) #391

1-01-01 Addition of variable definitions (part 2: lightning) #391

fstuerzl commented Apr 29, 2022 •

edited by amilan17

Loading

fstuerzl commented Apr 29, 2022

This comment was marked as outdated.

joergklausen commented May 20, 2022 •

edited

Loading

JohnEyre commented May 24, 2022

sibalm commented May 30, 2022

sibalm commented May 30, 2022

JohnEyre commented May 30, 2022

amilan17 commented Sep 22, 2022 •

edited

Loading

amilan17 commented Oct 6, 2022

amilan17 commented Oct 6, 2022 •

edited

Loading

joergklausen commented Oct 19, 2022 •

edited

Loading

joergklausen commented Nov 3, 2022

amilan17 commented Nov 3, 2022

amilan17 commented Nov 17, 2022

joergklausen commented Nov 22, 2022

amilan17 commented Nov 22, 2022

joergklausen commented Nov 22, 2022

amilan17 commented Nov 22, 2022 •

edited

Loading

amilan17 commented Nov 22, 2022 •

edited

Loading

sibalm commented Nov 22, 2022 •

edited

Loading

amilan17 commented Mar 17, 2023

joergklausen commented Apr 21, 2023

amilan17 commented Jun 1, 2023

joergklausen commented Sep 19, 2023

meulenvd commented Feb 2, 2024

amilan17 commented Feb 15, 2024

JREyre commented Feb 16, 2024

meulenvd commented Feb 19, 2024

amilan17 commented Apr 9, 2024

amilan17 commented May 6, 2024 •

edited

Loading

meulenvd commented May 10, 2024

amilan17 commented May 16, 2024

amilan17 commented Jun 13, 2024

1-01-01 Addition of variable definitions (part 2: lightning) #391

1-01-01 Addition of variable definitions (part 2: lightning) #391

Comments

fstuerzl commented Apr 29, 2022 • edited by amilan17 Loading

Proposal Summary

Summary and Purpose

Proposal

new

deprecate

Reason

Stakeholder(s)

Consultations

Context

Expected Impact of Change

fstuerzl commented Apr 29, 2022

This comment was marked as outdated.

joergklausen commented May 20, 2022 • edited Loading

JohnEyre commented May 24, 2022

sibalm commented May 30, 2022

sibalm commented May 30, 2022

JohnEyre commented May 30, 2022

amilan17 commented Sep 22, 2022 • edited Loading

amilan17 commented Oct 6, 2022

amilan17 commented Oct 6, 2022 • edited Loading

joergklausen commented Oct 19, 2022 • edited Loading

joergklausen commented Nov 3, 2022

amilan17 commented Nov 3, 2022

amilan17 commented Nov 17, 2022

joergklausen commented Nov 22, 2022

amilan17 commented Nov 22, 2022

joergklausen commented Nov 22, 2022

amilan17 commented Nov 22, 2022 • edited Loading

amilan17 commented Nov 22, 2022 • edited Loading

sibalm commented Nov 22, 2022 • edited Loading

amilan17 commented Mar 17, 2023

joergklausen commented Apr 21, 2023

amilan17 commented Jun 1, 2023

joergklausen commented Sep 19, 2023

meulenvd commented Feb 2, 2024

amilan17 commented Feb 15, 2024

JREyre commented Feb 16, 2024

meulenvd commented Feb 19, 2024

amilan17 commented Apr 9, 2024

amilan17 commented May 6, 2024 • edited Loading

meulenvd commented May 10, 2024

amilan17 commented May 16, 2024

amilan17 commented Jun 13, 2024

fstuerzl commented Apr 29, 2022 •

edited by amilan17

Loading

joergklausen commented May 20, 2022 •

edited

Loading

amilan17 commented Sep 22, 2022 •

edited

Loading

amilan17 commented Oct 6, 2022 •

edited

Loading

joergklausen commented Oct 19, 2022 •

edited

Loading

amilan17 commented Nov 22, 2022 •

edited

Loading

amilan17 commented Nov 22, 2022 •

edited

Loading

sibalm commented Nov 22, 2022 •

edited

Loading

amilan17 commented May 6, 2024 •

edited

Loading