Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Yield in dt/ha statt wie bisher kg/m2 #27

Open
anjaaeschlimann opened this issue Jun 25, 2024 · 1 comment
Open

Yield in dt/ha statt wie bisher kg/m2 #27

anjaaeschlimann opened this issue Jun 25, 2024 · 1 comment
Labels
jira Tag to activate JIRA integration v2

Comments

@anjaaeschlimann
Copy link

Input aus Review zum Berechnungsservice:

fertilisationStandardType, Attribute standardYield und maximumYield sind heute in kg/m2; effectiveYield in kg anzugeben. Fachlich wird aber dt/ha bzw. dt bevorzugt.

--> Ist durch Fachgruppe zu diskutieren und entscheiden. Umsetzung NäbiService Stand Juni 24 gemäss eCH in kg/m2

ACHTUNG: wenn dies geändert würde, müsste auch Masseinheit für Flächen erweitert / geändert werden
wenn, dann sinnvoll auch zugelassene Masseinheiten für Flächen auf ha anpassen damit in Berechnung Nährstoffbedarf / Ertrag keine Umrechnung erfolgen muss. Umrechnung kann Rundungsdifferenzen verursachen.

@montanajava
Copy link
Collaborator

Please note that a key element of the AgrarStandards has been to have one and only one unit of measure for a measurement type (e.g., kg for mass, m for distance). If a base SI unit is available, that unit or unit combination is to be chosen. The reason for this is system interoperability. The standard in no way specifies or restricts the measurement unit a system chooses to present to a user in a user interface, nor does it restrict internal persistence choices although compliance with the standard is recommended.

If the working group chooses nonetheless to accept the suggestion from the review group, then my recommendation is to not put it in eCH-0261, but have it located in this standard -- and only for the required and specific use case. That would unfortunately cause duplication not only of the unit type but presumably also of the measurement type.

@AFoletti AFoletti added jira Tag to activate JIRA integration and removed jira Tag to activate JIRA integration labels Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira Tag to activate JIRA integration v2
Projects
None yet
Development

No branches or pull requests

3 participants