Assign Descriptive File Names Assign descriptive file names Avoid using generic file extensions Codes should not be parameter specific but should be consistent across parameters and data files. Consistent formats are particularly important for dates, times, and spatial coordinates. Consistently use the same missing value notations for numeric and text/character fields in the data file. Create a data dictionary Create, manage, and document your data storage system A separate field with specified values may be used to provide additional information about the measured data value Assign Descriptive Data Set Titles Data that are provided in a proprietary software format must include documentation of the software specifications Dates: yyyy-mm-dd or yyyymmdd Define the Contents of Your Data Files Define the Quality of Your Data Define the parameters Definitions of flag codes should be included in the accompanying data set documentation. Describe the units of measurement for each observation Describe the units of measurement for each observation Identify missing values and define missing value codes Identify values that are estimated If a shorthand notation is reported in the data file, the complete units should be spelled out in the documentation If the data files were created with custom code, provide a software program to enable the user to read the files If you are collecting many observations of several different types of measurements at a site, place each type of measurement in a separate data file. Keep Similar Information Together Keep copies of your raw data as collected or as received, before any processing has been done. Maintain consistent data typing Make sure that all location information in a file uses the same coordinate system Perform Basic Quality Assurance Provide Data Set Documentation and Metadata Provide elevation in meters. Provide identifier for dataset used Provide latitude and longitude with south latitude and west longitude recorded as negative values Provide version information for use and discovery Separate data values from annotations Spatial coordinates should be reported in decimal degrees format to at least 4 (preferably 5 or 6) significant digits past the decimal point. To ensure that documentation can be read well into the future requires that it be in a stable non-proprietary format. Use 24-hour notation Use Consistent File Structure and Stable File Formats For Tabular and Image Data Use appropriate field delimiters Use commonly accepted parameter names Use consistent codes Within each data set, choose a format for each parameter, explain the format in the documentation, and use that format throughout the data set. be aware of, and document, any changes in the coding scheme both the begin time and end time should be reported in both local and UTC time consider the potential user community, the final data archive, and the certain Web accessibility of your data data, processing codes, and documentation at all stages of development be routinely copied and backed up on secure and retrievable media determine the likely final destination and likely mode of dissemination of your data have names that describe the contents and are standardized across files, data sets, and the project inquire about integration and interoperability opportunities for archived data and related data products to maximize data reuse it is also important to be able to tell what data were used for the synthesis or model data proper attribution of the source data be included with the derived product select a consistent format that can be read well into the future and is independent of changes in applications specify the standard source for units in your data set to reduce the level of effort required to prepare data for sharing. units of reported parameters need to be explicitly stated in the data file and in the documentation use consistent capitalization (not temp, Temp, and TEMP) use only letters, numerals, and underscores in the parameter name users want to know where your data have been before they were archived Book traversal links for Data description and representation ‹ Identify outliers Up Assign Descriptive File Names › Printer-friendly versionLog in to post comments Create quality metadata for data discovery, preservation, and provenance functions.