search

terraref / drone-pipeline

Generalizing the TERRA REF pipelines for processing data from UAV's
BSD 3-Clause "New" or "Revised" License
2 stars 2 forks source link

Define minimal data fields needed for extracting plots from Orthomosaic #19

Closed Chris-Schnaufer closed 5 years ago

Chris-Schnaufer commented 5 years ago

Determine what the minimum mandatory set of data needed to extract plot-level data from geo-referenced Orthomosaics. Also define default behavior if data is missing.

Chris-Schnaufer commented 5 years ago

@dlebauer At this time, I'm thinking of the following (sample) JSON for providing the basic information for extractors. There needs to be more information added for placing the shapes into BETYdb and that's not defined yet. The JSON would be in a file (tentatively) named "experiment.json" and uploaded to new datasets as metadata (actual metadata format TBD as of this comment)

The following keys are taken from BRAPI with the JSON hierarchy flattened/removed since it would add a bit of overhead: "studyName", "season", "year", "observationTimeStamp". The other keys are made up and can be changed. The value of "observationUnitName" also comes from BRAPI.

{
    "pipeline": {
        "studyName": "My Experiment",
        "season": "Season X",
        "year": "2018",
        "observationTimeStamp": "2018-12-12T22:03:51-04:00",
        "extractors": {
            "plot_column_name": "observationUnitName",
        },
    }
}

For extractor specific data I've thought about adding another level that was context relevant, such as adding a "shapefile" level between "extractors" and "plot_column_name" - I'm still undecided about that, but leaning towards having the additional level for clarity.

Chris-Schnaufer commented 5 years ago

Documented and tested. Next step is to convert to YAML