You can use the field ID to group and derive field-based features such as area or maximum NDVI. But you cannot derive any features from the field ID (as a numeric column) itself
When making a prediction for a field, you must use the image data only. No variables to do with fields that have similar IDs, no information from nearby fields. This also means that you cannot use the field locations (pixel locations or otherwise) as features. This is to ensure that the solution is applicable elsewhere, outside of the area covered by this dataset.
Thanks for your clarifications. We are still unclear about the rules and would appreciate if Zindi could update their rule set. There are a variety of useful clarifications in this thread which are not explicitly covered by the rules in our opinion. It would be great if the rules could be updated so people don't have to read through all the posts to understand the nitty-gritty details of the rules expected by Zindi. Which data can be used in preprocessing and training? The current wording "Models that use metadata such as dates or spatial coordinates" is not definite.
There is also still a confusion apparently evident in this post: https://zindi.africa/competitions/iclr-workshop-challenge-2-radiant-earth-computer-vision-for-crop-recognition/discussions/788 whether we can use any new features derived on calculations using the field ID (e.g. aggregating values per field ID).
I did this without noticing - is there any way I can remove my score?
Yes, please email zindi@zindi.africa with the submissions you would like us to remove.
Thanks at Zindi Anyone using the Field should cancel his submission let make the Leaderboard looks real.
May dates be used? Photosensitivity changes over time for crops.
Unfortunately, dates cannot be used. We want to reiterate that this is a computer vision challenge, therefore your models should not use metadata.
Can the dates be used as IDs to reconstruct the 2x2 grid (00 01 02 03) into a single mosaic?
Yes, if you are taking the approach of viewing the mosaic as a 'single image'. However, you cannot use the dates a feature in your modeling.
Can field location (not ID) be used as an input?
Yes.
Many thanks for your speedy responses. May I suggest such statements are reflected in rules as you make them.
@DrFad something about the location is here
Can we use Field ID in preprocessing? to get features as min or max value in field ID
No, you may not.
But I believe area of a field can be used as confirmed by the host on another discussion??
You can use the field ID to group and derive field-based features such as area or maximum NDVI. But you cannot derive any features from the field ID (as a numeric column) itself
Thanks so using row_loc, col_loc as a feature does not violate the rule?
It should violate it because it signifies the coordinates of the field which they've said is not allowed as a feature.
waiting for @Zindi reply on this
When making a prediction for a field, you must use the image data only. No variables to do with fields that have similar IDs, no information from nearby fields. This also means that you cannot use the field locations (pixel locations or otherwise) as features. This is to ensure that the solution is applicable elsewhere, outside of the area covered by this dataset.
Thanks for the clarification
Dear Zindi Team,
Thanks for your clarifications. We are still unclear about the rules and would appreciate if Zindi could update their rule set. There are a variety of useful clarifications in this thread which are not explicitly covered by the rules in our opinion. It would be great if the rules could be updated so people don't have to read through all the posts to understand the nitty-gritty details of the rules expected by Zindi. Which data can be used in preprocessing and training? The current wording "Models that use metadata such as dates or spatial coordinates" is not definite.
There is also still a confusion apparently evident in this post: https://zindi.africa/competitions/iclr-workshop-challenge-2-radiant-earth-computer-vision-for-crop-recognition/discussions/788 whether we can use any new features derived on calculations using the field ID (e.g. aggregating values per field ID).
Thank you!
Thank you all for pointing out these questions. Please see the clarification we just added to the other discussion (https://zindi.africa/competitions/iclr-workshop-challenge-2-radiant-earth-computer-vision-for-crop-recognition/discussions/806) to address these questions. If there is any remaining questions, feel free to post.