You are here

Error message

The page style have not been saved, because your browser do not accept cookies.

Primary tabs

crowston

Type	Title	Author	Replies	Last updated
Data Management Best Practice	Spatial coordinates should be reported in decimal degrees format to at least 4 (preferably 5 or 6) significant digits past the decimal point.	crowston	0	12 years 7 months ago
Data Management Best Practice	both the begin time and end time should be reported in both local and UTC time	crowston	0	12 years 7 months ago
Data Management Best Practice	Use 24-hour notation	crowston	0	12 years 7 months ago
Data Management Best Practice	Dates: yyyy-mm-dd or yyyymmdd	crowston	0	12 years 7 months ago
Data Management Best Practice	Consistent formats are particularly important for dates, times, and spatial coordinates.	crowston	0	12 years 7 months ago
Data Management Best Practice	use only letters, numerals, and underscores in the parameter name	crowston	0	12 years 7 months ago
Data Management Best Practice	use consistent capitalization (not temp, Temp, and TEMP)	crowston	0	12 years 7 months ago
Data Management Best Practice	Use commonly accepted parameter names	crowston	0	12 years 7 months ago
Data Management Best Practice	To ensure that documentation can be read well into the future requires that it be in a stable non-proprietary format.	crowston	0	12 years 7 months ago
Data Management Best Practice	Provide Data Set Documentation and Metadata	crowston	0	12 years 7 months ago
Data Management Best Practice	Assign Descriptive Data Set Titles	crowston	0	12 years 7 months ago
Data Management Best Practice	Define the Quality of Your Data	crowston	0	12 years 7 months ago
Data Management Best Practice	Perform Basic Quality Assurance	crowston	0	12 years 7 months ago
Data Management Best Practice	Assign Descriptive File Names	crowston	0	12 years 7 months ago
Data Management Best Practice	Data that are provided in a proprietary software format must include documentation of the software specifications	crowston	0	12 years 7 months ago
Data Management Best Practice	If the data files were created with custom code, provide a software program to enable the user to read the files	crowston	0	12 years 7 months ago
Data Management Best Practice	Avoid using generic file extensions	crowston	0	12 years 7 months ago
Data Management Best Practice	select a consistent format that can be read well into the future and is independent of changes in applications	crowston	0	12 years 7 months ago
Data Management Best Practice	Use Consistent File Structure and Stable File Formats For Tabular and Image Data	crowston	0	12 years 7 months ago
Data Management Best Practice	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.	crowston	0	12 years 7 months ago
Data Management Best Practice	Keep Similar Information Together	crowston	0	12 years 7 months ago
Data Management Best Practice	Consistently use the same missing value notations for numeric and text/character fields in the data file.	crowston	0	12 years 7 months ago
Data Management Best Practice	specify the standard source for units in your data set	crowston	0	12 years 7 months ago
Data Management Best Practice	If a shorthand notation is reported in the data file, the complete units should be spelled out in the documentation	crowston	0	12 years 7 months ago
Data Management Best Practice	Definitions of flag codes should be included in the accompanying data set documentation.	crowston	0	12 years 7 months ago

Pages