-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add Constraints (Auflagen) to PlantProtectionProduct #3
Comments
Auflagen come from infoPhyto and are currently described in freetext format. These should be parseable. Examples: Can not be used within 10 metres from water. |
montanajava
changed the title
Add Constraints (Auflangen) to PPP
Add Constraints (Auflangen) to PlantProtectionProduct
Nov 15, 2023
montanajava
changed the title
Add Constraints (Auflangen) to PlantProtectionProduct
Add Constraints (Auflagen) to PlantProtectionProduct
May 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Usage constraints or restrictions are very valuable to know when, for instance, applying phytosanitary or plant protection product on a field. Such constraints, are, however, fully free text and are not parseable.
Constraints, or Restrictions (de=Auflage) should be machine-parsable and added as a 0-n attribute to a plant protection product.
The description of how that looks should flow from infoPhyto.
The text was updated successfully, but these errors were encountered: