You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The source attributes include name, url, type and component.
What is your proposed change?
A description field to add details about the source would be useful, especially to explain the relationship between the source and the dataset in object.
E.g. "the source dataset/model has been clipped for the geographic region / resampled to different resolution / reprojected on a different CRS / etc.)
The text was updated successfully, but these errors were encountered:
This could also allow us to describe how the source data has been used in the analysis.
I learned yesterday that Meteor data uses ISO fields lineage > processStep to describe the steps taken in the analysis, in that case for preparing exposure dataset.
Example: LSO_oed_exposure_20200811.xml.zip
Lineage starts at ln683, with a list of biblio references (which RDLS separates into individual sources)
The first of seven processSteps start at ln759
We could use either description field, or an additional field dedicated to describing the use of that source?
We can have just "Description" to hold all content, or "Description" and "Lineage" as separate fields, where lineage specifies any change from the source.
What is the context or reason for the change?
The
source
attributes include name, url, type and component.What is your proposed change?
A description field to add details about the source would be useful, especially to explain the relationship between the source and the dataset in object.
E.g. "the source dataset/model has been clipped for the geographic region / resampled to different resolution / reprojected on a different CRS / etc.)
The text was updated successfully, but these errors were encountered: