search

DATEX-II-EU / DatexII

Main repository for issues and bugs for the DATEXII standard
0 stars 0 forks source link

Enumerations for environmental particulates are too restrictive (Bugzilla Bug 279) #279

Closed datexii closed 3 months ago

datexii commented 4 years ago

This issue was created automatically with bugzilla2github.py

Bugzilla Bug 279

Date: 2019-11-14T09:14:10+01:00 From: Ian Snell <ian.snell@siemens.com> To: @JoergFst

Last updated: 2024-05-17T08:39:52+02:00

datexii commented 4 years ago

Comment 1400

Date: 2019-11-14 09:14:10 +0100 From: Ian Snell <ian.snell@siemens.com>

The current enumerations are for PM10 and Primary particulates. Some detectors do not provide data that easily fits into these categories, e.g. data is missing for PM1 particles and hence the data won't properly make use of the Primary enumeration. Can additional enumerations be added to make data representation align better with the data sources?

datexii commented 4 years ago

Comment 1401

Date: 2019-11-14 09:25:19 +0100 From: @JoergFst

Adding new literals or enumerations is possible only in major releases, unfortunatly not in between. But we will keep this request in mind, of course. In between, you can help yourself with a Level B extension, either by creating a new Enumeration or by extending the existing one.

I suppose, you talk about the "PollutantTypeEnum"? So, to exact phrase your request: You like to add a new literal "particulates1"? Is one new literal sufficient, or do you need more? You talked about a new enumeration, in this case, you should detail your request more precisly, please.

datexii commented 3 months ago

Comment 1942

Date: 2024-05-17 08:39:52 +0200 From: @JoergFst

Acknoledged. In DATEX II version 4, the following literals will be present: pm0_1 pm1 pm2_5 pm2_5to10 pm10