Field Order Field Name Data Type 1 Flag Decimal number 2 Distance Decimal number 3 Reading_Order Decimal number 4 PS_ON Decimal number 5 PS_OFF Decimal number 6 CP_CRITERIA Decimal number 7 LOC_X Decimal number 8 LOC_Y Decimal number 9 LOC_Z Decimal number 10 DATE 11 TIME 12 Remark Character string 13 Feature_Type Character string Field Order Comments Codelist
1 Format: NNNNNN.N 2 Format: NNNNNNNNNN.NN 3 Format: NNNNNNN 4 Format: N.NNN 5 Format: N.NNN 6 Format: N.NNN 7 Format: NNN.NNNNNNNNNNN 8 Format: NNN.NNNN NNNNNNN 9 Format: NNN.NNNNNNNNNNN 10 Format: MM/DD/YYYY 11 Format: HH:MM:SS (AM or PM) 12 Length: 255 13 Length: 255 ECDAFeatureType
With the scope and needs of the project sketched out, the GIS Workgroup used Leica Geosystems' Codelist Manager (Leica Geosystems, GIS & Mapping Division, Atlanta, Georgia, http://www.gis.leicageosystems.com) to create a codelist to govern the data collection process in the field.
Within Codelist Manager, the personnel defined the code for each feature to be mapped.
For example, the ONIX for Serials Codelists
(EDItEUR Limited, 2012) includes data elements identifying resource type (eBook, print serial, tangible serial, online serial, collection of eBooks, and mixed collections of both eBooks and ejournals in either tangible or online form) in conjunction with elements that identify the title source, e.g., "the full text of the cover title of a serial, or the title on a serial content item or a reviewed resource ...