1、Designation: E2560 07E2560 13Standard Specification forData Format for Pavement Profile1This standard is issued under the fixed designation E2560; the number immediately following the designation indicates the year oforiginal adoption or, in the case of revision, the year of last revision. A number
2、in parentheses indicates the year of last reapproval. Asuperscript epsilon () indicates an editorial change since the last revision or reapproval.1. Scope1.1 This specification describes a data file format for pavement profile.1.2 This specification describes the variable variables and sizes of all
3、data that will be stored in the file. The file is in binaryformat, and is fully documented in this specification.1.3 This specification is designed to be independent of hardware platforms, computer languages, and Operating System(OS)(OS).1.4 This standard does not purport to address all of the safet
4、y concerns, if any, associated with its use. It is the responsibilityof the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatorylimitations prior to use.2. Referenced Documents2.1 ASTM Standards:2E867 Terminology Relating to Vehicle
5、-Pavement Systems2.2 IEEE Standards:3IEEE 754IEEE 7542008 (2008) Binary Floating-Point Arithmetic (1985, Reaffirmed 1990)3. Terminology3.1 Definitions: Terminology used in this specification conforms to the definitions included in Terminology E867.3.1.1 Terminology used in this specification conform
6、s to the definitions included in Terminology E867.3.2 Definitions of Terms Specific to This Standard:3.2.1 signedinteger capable of representing negative values.3.2.2 unsignedinteger only capable of representing non-negative values.3.2.3 Int8data type for an 8-bit, unsigned integer.3.2.4 Int32data t
7、ype for a 32bit,32-bit, signed integer.3.2.5 singleSingledata type for a 32bit,32-bit, signed real number, such as, single precision IEEE floating point.3.2.6 Stringdata type for a variable-lengthASCII string. No null character is included at the end of the string.Aseparate fielddefines the length o
8、f the string.3.2.7 3-byte Stringan ASCII string of 3 characters in length. No null character is included at the end of the string.3.2.8 4-byte stringStringan ASCII string of 4 characters in length. No null character is included at the end of the string.3.2.9 8-byte stringStringan ASCII string of 8 c
9、haracters in length. No null character is included at the end of the string.3.2.10 array, (Int32, single)Array (numeric data type)Sequencesequence of data of the specified numeric data type. Onlythe values are stored, but no information about the array is stored.3.2.11 array (single)Array (String)AS
10、CII strings separated by a tab. There is no tab after the last string.1 This test method is under the jurisdiction of ASTM Committee E17 on Vehicle - Pavement Systems and is the direct responsibility of Subcommittee E17.31 on Methodsfor Measuring Profile and Roughness.Current edition approved April
11、1, 2007June 1, 2013. Published April 2007July 2013. Originally approved in 2007. Last previous edition approved in 2007 as E2560 07.DOI: 10.1520/E2560-07.10.1520/E2560-13.2 For referencedASTM standards, visit theASTM website, www.astm.org, or contactASTM Customer Service at serviceastm.org. For Annu
12、al Book of ASTM Standardsvolume information, refer to the standards Document Summary page on the ASTM website.3 Available from Institute of Electrical and Electronics Engineers, Inc. (IEEE), 445 Hoes Ln., P.O. Box 1331, Piscataway, NJ 08854-1331, http:/www.ieee.org.This document is not an ASTM stand
13、ard and is intended only to provide the user of an ASTM standard an indication of what changes have been made to the previous version. Becauseit may not be technically possible to adequately depict all changes accurately, ASTM recommends that users consult prior editions as appropriate. In all cases
14、 only the current versionof the standard as published by ASTM is to be considered the official document.Copyright ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States13.3 Symbols:3.3.1 ntotal channels of elevation data.3.3.2 mtotal number of test lo
15、cations (that is, data points).4. Profile Data Specifications4.1 File Structure4.1.1 The general file structure is divided into five sections: (1) File Header,Header; (2) Metadata; (3) Longitudinal Profile Data;(4) Transverse Profile Data; and (5) File Trailer. The five sections are stored sequentia
16、lly. (See Fig. 1.)4.1.2 Each of these portions of the file is described in the following sections, as well as the data types and other descriptors thatwill be required by the file. The data will be written to the file sequentially, with the offsets listed in the file header as guides tofind various
17、portions of the file. It is important to note that all offsets are relative to the beginning of the file. Because offset valuesmay not be known at the time of writing the file header, these values need not be written. However, spare space must still bereserved for the offsets so that values can be u
18、pdated when known.4.2 File Header4.2.1 File header contains the information pertaining to the data file type, software version information, and information aboutthe data contained (Table 1).4.3 Metadata4.3.1 Metadata is structured, descriptive information about a resource, or data about data. Using
19、metadata in the binary fileformat will allow generic operating on the data information about which the reader software has no prior knowledge. Also,metadata will allow scalable evolution of the data description without requiring simultaneous upgrades to all reader software.4.3.2 The first value in t
20、he metadata portion will provide the number of metadata entries (MDE) and(Table 2 the). Table 3information regarding each of them. Table 2shows the information required to construct an appropriate MDE.4.3.3 The metadata tags are listed in Table 36, and can be used in any number or order. If no metad
21、ata tags exist, number ofMDEs = 0.FIG. 1 Layout of the File StructureTABLE 2 MetadataVariable Name Data Type DataNumber of MDEs Int32 Number of MDEsE2560 1324.3.4 The names of the standard metadata entries (see Table 83) are not stored in the metadata entry to conserve space and moreimportantly, to
22、allow for localization, that is, the file is not tied to one written language. User-defined metadata entries cannot bearrays and the data type is always String.4.3.5 The storage convention for empty arrays is to store a one-byte value of the same data type as the array. For example, anarray of singl
23、es with no elements would store a value of 0.4.4 Longitudinal Profile Data4.4.1 There are two ways to store the profile data: location-wise and array-wise. The first method is appropriate for datarecording during profile data collection to prevent data loss, while the other is appropriate for post-p
24、rocessing to speed up softwarereading and writing.4.4.2 If the data storage format, from metadata tag #522 inspecifies Table 9, equals 1 (that is, location-wise), location-wisestorage, the longitudinal data will be stored as a sequence of current longitudinal distance followed by corresponding eleva
25、tionsof longitudinal sensors at this location, beginning at the left side of the vehicle. The next block of storage will store longitudinaldistance and all elevation data for the next location, and so on. However, the location may not need to be stored if a specific datainterval is given. (See Fig.
26、2.)4.4.2.1 In general, if a location and elevation channels are recorded for each test location, every set of n+1 Singles (one distancedata and n channels of elevation data) will be read as one profile location. If a specific data interval is included in the metadata,only n Singles will be read for
27、each location. For example, if a standard interval exists and a single channel of profile data ispresent, only one Single will be read for each location. If two are present, then two Singles will be read per point.4.4.2.2 The location-wise format is recommended for profiler data acquisition software
28、. Storing the data after every samplinglocation allows for immediate writing to protect against data loss and reduce memory requirements.4.4.3 If the data storage format from metadata tag #522 inspecifies Table 9 equals 2 (that is, array-wise), array-wise storage,then the longitudinal data will be s
29、tored as a sequence of the longitudinal distance array followed by the elevation array of eachlongitudinal sensor, beginning at the left side of the vehicle for all locations. (See Fig. 3.)4.4.3.1 In general, if distance and elevation channels are recorded for each test location, n+1 sets (one dista
30、nce channel and nchannels of elevation data) of m Singles will be stored in sequence. sequence, where m is the number of points. If a specific datainterval is included in the metadata, only n sets of m Singles will be stored sequentially, with distance being calculated from thebeginning of the test
31、location by the software. For example, if a standard interval exists and a single channel of profile data ispresent, only one set of Singles will be stored. If two are present, then two sets of m Singles will be stored sequentially.TABLE 1 File HeaderVariable Name Data Type Data Default ValueSignatu
32、re 4-byte string identifies file as being written in the StandardPavement Profile Format”SPPF”Signature 4-byte String Identifies file as being written in the StandardPavement Profile Format”SPPF”Version 4-byte string identifies the version number of the file format “1.01”Version 4-byte String Identi
33、fies the version number of the file format “1.05”SW version 8-byte string identifier of the software that produced the fire for example, “TGPA1.00”SW version 8-byte String Identifier of the software that produced the file for example, “TGPA1.00”Metadata offset Int32 offset in bytes to the beginning
34、of the metadata N/AMetadata offset Int32 Offset in bytes from the beginning of the file tothe beginning of the metadataN/ALongitudinal offset Int32 offset in bytes to the beginning of thelongitudinal profile dataN/ALongitudinal offset Int32 Offset in bytes from the beginning of the file tothe beginn
35、ing of the longitudinal profile dataN/ATransverse data offset Int32 offset in bytes to the beginning of thetransverse profile dataN/ATransverse data offset Int32 Offset in bytes from the beginning of the file tothe beginning of the transverse profile dataN/ATABLE 74 Data TypesIndexA Data Type Size (
36、bytes) Description8 String varies one byte ASCII (no unicodesupport)17 Int8 1 8-bit unsigned integer3 Int32 4 32-bit signed integer4 Single 4 Single precision IEEE floatingpointAData type index values follow Microsoft programming conventions.E2560 133NOTE 1Any tags not listed below 1024 are reserved
37、 for future use.TABLE 3 Metadata Tags and DescriptionsRequired? Tag Name Data Type256 511: General Profiler and Location Informationyes 258 Section title String259 Profiler trade name and model number String260 Vehicle identification String261 Date data was collected(yyyymmdd) String262 Time data wa
38、s collected(hhmmss) String263 Profiler operator name String264 Average vehicle speed associated with data String265 Original filename before import String271 Agency district name String272 Agency district number Int32273 County name String274 County number Int32275 Nearby city name String281 Roadway
39、 designation String282 Lane identification String283 Station number of beginning point String284 Reference marker or milepost of beginning point String285 Pavement surface type (See Table 5) Int32286 Direction of travel String287 Station number of ending point String288 Reference marker or milepost
40、of ending point String291 Ambient temperature String292 Surface temperature String293 Climactic conditions (see Table 6) Int32294 Data history String295 Date file last modified(yyyymmdd) String296 Time file last modified(hhmmss) String297 Date file imported from original file format(yyyymmdd) String
41、298 Time file imported from original file format(hhmmss) String299 Run number (multiple runssame location on the same day) Int32300 Profiler type (see Table 10) Int32301 County name String302 State/Province Name String303 Wind speed (mph) Single304 Wind direction String512767: Longitudinal and Trans
42、verse Profile Informationyes 512 Number of longitudinal elevation channels Int32yes 513 Number of transverse elevation channels Int32yes 514 Number of longitudinal data points Int32yes 515 Number of transverse profiles data points Int32516 Longitudinal distance between longitudinal data points Singl
43、e517 longitudinal distance between transverse profiles Singleyes 518 Longitudinal sensor spacing from vehicle center (negative values to the left ofvehicle center, positive to the right)Array (single)519 Transverse sensor spacing from vehicle center (negative values to the left ofvehicle center, pos
44、itive to the right)Array (single)520 Names for longitudinal sensors Array (single)521 Names for transverse sensors Array (single)yes 522 Longitudinal data storage format (See Table 9) Int32523 Channel type for each longitudinal profile (see Table 11) Array (Int32)525 Profile offset (if linear distan
45、ce adjustment or correlation is performed) Single526 Profile start index to define the location of lead-in Int32527 Profile stop index to define the location of lead-out Int32528 Event marker index Array (Int32)529 Event marker text Array (string)7681023: Measurement Units Informationyes 768 Units f
46、or longitudinal distances (see Table 4) Int32yes 769 Units for elevation data (see Table 4) Int32770 Units of speed (see Table 4) Int32771 Units of temperature (see Table 4) Int32772 Units of sensor spacing (see Table 4) Int3210242047: User Defined Metadata10242047 Reserved for user defined metadata
47、 entries StringTABLE 6 Metadata Tags and DescriptionsTag Name Data Type Notes256 511: General Profiler and Location Information258 Title String Required259 Profiler trade name and model number String260 Vehicle identification String261 Date data was collected(yyyymmdd) String262 Time data was collec
48、ted(hhmmss) String263 Profiler operator name String264 Average vehicle speed associated withdataString265 Original filename before import String Read-onlyB271 Agency district name String272 Agency district number Int32273 County name String274 County number Int32E2560 1344.4.3.2 This data format is
49、recommended for software that reads and writes the data during post-processing. Data stored as onecontinuous array (array-wise) can be read and processed much faster than the location-wise storage format.4.5 Transverse Profile Data4.5.1 The transverse elevation readings are treated the same as the longitudinal data.4.6 File Trailer4.6.1 The file trailer is used to signal the end of the file. (See Table 125.)4.7 Event Markers4.7.1 Event markers are defined by tags 528 to 531. These four arrays must all be of the same length.4.8 Sections4.
