1、Designation: E2560 13E2560 17Standard 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 variables and sizes of all data that
3、 will be stored in the file. The file is in binary format, andis fully documented in this specification.1.3 This specification is designed to be independent of hardware platforms, computer languages, and Operating Systemoper-ating system (OS).1.4 This standard does not purport to address all of the
4、safety 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.1.5 This international standard was developed in accordance with internati
5、onally recognized principles on standardizationestablished in the Decision on Principles for the Development of International Standards, Guides and Recommendations issuedby the World Trade Organization Technical Barriers to Trade (TBT) Committee.2. Referenced Documents2.1 ASTM Standards:2E867 Termin
6、ology Relating to Vehicle-Pavement Systems2.2 IEEE Standards:3IEEE 7542008 (2008) Floating-Point Arithmetic3. Terminology3.1 Definitions:3.1.1 Terminology used in this specification conforms to the definitions included in Terminology E867.3.2 Definitions of Terms Specific to This Standard:3.2.1 sign
7、edinteger capable of representing negative values.3.2.2 unsignedinteger only capable of representing non-negative values.3.2.3 Int8int8data type for an 8-bit, unsigned integer.3.2.4 Int32int32data type for a 32-bit, signed integer.3.2.5 Singlesingledata type for a 32-bit, signed real number, such as
8、, single precision IEEE floating point.3.2.6 Stringstringdata type for a variable-length ASCII string. No null character is included at the end of the string. Aseparate field defines the length of the string.3.2.7 3-byte StringstringanASCII string of 3three characters in length. No null character is
9、 included at the end of the string.3.2.8 4-byte StringstringanASCII string of 4four characters in length. No null character is included at the end of the string.3.2.9 8-byte StringstringanASCII string of 8eight characters in length. No null character is included at the end of the string.1 This test
10、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 June 1, 2013June 1, 2017. Published July 2013June 2017. Originally approved in 2007. Las
11、t previous edition approved in 20072013 asE2560 07.E2560 13. DOI: 10.1520/E2560-13.10.1520/E2560-17.2 For referencedASTM standards, visit theASTM website, www.astm.org, or contactASTM Customer Service at serviceastm.org. For Annual Book of ASTM Standardsvolume information, refer to the standards Doc
12、ument 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 standard and is intended only to provide the user of an ASTM standard an ind
13、ication 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 only the current versionof the standard as published by ASTM is to be
14、considered the official document.Copyright ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States13.2.10 Arrayarray (numeric data type)sequence of data of the specified numeric data type. Only the values are stored,stored;no information about the arra
15、y is stored.3.2.11 Array (String)array (string)ASCII strings separated by a tab. There is no tab after the last string.3.3 Symbols:3.3.1 ntotal channels of elevation data.3.3.2 mtotal number of test locations (that is, data points).4. Profile Data Specifications4.1 File Structure:4.1.1 The general f
16、ile structure is divided into five sections: (1) File Header; (2) Metadata; (3) Longitudinal Profile Data; (4)Transverse Profile Data; and (5) File Trailer. The five sections are stored sequentially. (See Fig. 1.)4.1.2 Each of these portions of the file is described in the following sections, as wel
17、l 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 portions of the file. It is important to note that all offsets are relative to the beginning of the file.
18、 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 updated when known.4.2 File HeaderFile header contains the information pertaining to the data file type, s
19、oftware version information, andinformation about the data contained (Table 1).4.3 Metadata:4.3.1 Metadata is structured, descriptive information about a resource, or data about data. Using metadata in the binary fileformat will allow generic operating on the data information about which the reader
20、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 the metadata portion will provide the number of metadata entries (MDE) (Table 2). Table 3 shows theinformation
21、required to construct an appropriate MDE.4.3.3 The metadata tags are listed in Table 4, and can be used in any number or order. If no metadata tags exist, number ofMDEs = 0.4.3.4 The names of the standard metadata entries (see Table 3) are not stored in the metadata entry to conserve space and morei
22、mportantly, to 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, a
23、narray of singles with no elements would store a value of 0.FIG. 1 Layout of the File StructureE2560 1724.4 Longitudinal Profile Data:4.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
24、prevent data loss, while the other is appropriate for post-processing to speed up softwarereading and writing.4.4.2 If the data storage format, from metadata tag #522 specifies location-wise storage, the longitudinal data will be stored asa sequence of current longitudinal distance followed by corre
25、sponding elevations of longitudinal sensors at this location, beginningat the left side of the vehicle. The next block of storage will store longitudinal distance and all elevation data for the next location,and so on. However, the location may not need to be stored if a specific data interval is gi
26、ven. (See Fig. 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 wi
27、ll be read for 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 acqui
28、sition software. Storing the data after every samplinglocation allows for immediate writing to protect against data loss and reduce memory requirements.TABLE 1 File HeaderVariable Name Data Type Data Default ValueSignature 4-byte String Identifies file as being written in the StandardPavement Profil
29、e 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.05”Version 4-byte String Identifies the version number of the file format.This number is incremented if a chang
30、e ismade that breaks compatibility with previousversions of the format.“1.05”SW version 8-byte String Identifier of the software that produced the file for example, “TGPA1.00”Metadata offset Int32 Offset in bytes from the beginning of the file tothe beginning of the metadataN/ALongitudinal offset In
31、t32 Offset in bytes from the beginning of the file tothe beginning of the longitudinal profile dataN/ATransverse data offset Int32 Offset in bytes from the beginning of the file tothe beginning of the transverse profile dataN/ATABLE 2 MetadataVariable Name Data Type DataNumber of MDEs Int32 Number o
32、f MDEsFIG. 2 Location-wise StorageE2560 1734.4.3 If the data storage format from metadata tag #522 specifies array-wise storage, then the longitudinal data will be storedas a sequence of the longitudinal distance array followed by the elevation array of each longitudinal sensor, beginning at the lef
33、tside 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 distance channel and nchannels of elevation data) of m Singles will be stored in sequence, where m is the number of points. If a specific dat
34、a intervalis included in the metadata, only n sets of m Singles will be stored sequentially, with distance being calculated from the beginningof the test location by the software. For example, if a standard interval exists and a single channel of profile data is present, onlyone set of Singles will
35、be stored. If two are present, then two sets of m Singles will be stored sequentially.4.4.3.2 This data format is 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-wi
36、se storage format.4.5 Transverse Profile DataThe transverse elevation readings are treated the same as the longitudinal data.4.6 File TrailerThe file trailer is used to signal the end of the file. (See Table 15.)4.7 Event MarkersEvent markers are defined by tags 528 to 531. These four arrays must al
37、l be of the same length.4.8 Sections:4.8.1 A section is defined by the use of two event markers. The first event marker is the start location of the section and thesecond event marker is the stop location. Special attention should be paid to lead-in and lead-out event markers. These two markersdefin
38、e the section that is bounded by the lead-in and lead-out. Please note: they do not define the lead-in and lead-out, but thesection between them. An example of this follows:TABLE 3 Metadata EntriesVariable name Data type DataTag of MDE Int32 Metadata tag (see Table 4)Data type of MDE Int32 Data type
39、 index of MDE (see Table 5)Array size Int32 “-1” if not an array. “0” if array is empty. Numbers greater than 0 specify thenumber of elements in the array. Even though arrays of strings are storeddifferently than other types of array, an array size should still be specified here.Count Int32 For data
40、 types “String” and “Array (String)”, count = the number of bytes in thestring. for other data types, count = 1.Count Int32 For data types “String” and “Array (String),” count = the number of bytes in thestring. for other data types, count = 1.Name length Int32 For metadata entries listed in Table 4
41、, this is 0. For user-defined entries, thisvalue is the length of the name.Name String Name of the metadataMDE varies Information associated with tag of MDEFIG. 3 Array-wise StorageE2560 174TABLE 4 Metadata Tags and DescriptionsTag Name Data Type Notes256 511: General Profiler and Location Informati
42、on256 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 collected(hhmmss) String263 Profiler operator name String264 Average vehicle spee
43、d associated withdataString264 Average vehicle speed associated withdataSingle265 Original filename before import String Read-onlyB271 Agency district name String272 Agency district number Int32273 County name String274 County number Int32275 Nearby city name String281 Roadway designation String282
44、Lane identification String283 Station number of beginning point String284 Reference marker or milepost ofbeginning pointString No longer usedC285 Pavement surface type (See Table 6) Int32286 Direction of travel String Such as “northbound”287 Station number of ending point String288 Reference marker
45、or milepost of endingpointString No longer used291 Ambient temperature String292 Surface temperature String293 Climactic conditions (see Table 7) Int32294 Data history String Read-only295 Date file last modified(yyyymmdd) String Read-only296 Time file last modified(hhmmss) String Read-only297 Date f
46、ile imported from original fileformat(yyyymmdd)String Read-only298 Time file imported from original fileformat(hhmmss)String Read-only299 Run number (multiple runssamelocation on the same day)Int32300 Profiler type (see Table 8) Int32301 Country name String302 State/Province Name String303 Wind spee
47、d Single304 Wind direction String305 Thumbnail image Array (Int8) Read-only306 Start milepost Single307 Stop milepost Single308 Profiler direction (see Table 9) Int32309 File key String Read-only310 Profile keys Array (String) Read-only311 Section keys Array (String) Read-only312 Section names Array
48、 (String) Read-only313 Comments String314 Default section key String315 Original file key String Read-only316 Coordination system (see Table 10) Int32316 Coordinate system (see Table 10) Int32317 UTM zone Int32318 Start longitude Single Units defined by Table 10319 Start latitude Single Units define
49、d by Table 10320 Start elevation Single In metres321 Stop longitude Single Units defined by Table 10322 Stop latitude Single Units defined by Table 10323 Stop elevation Single In metres325 Route Image Array (Int8)512767 Longitudinal and Transverse Profile Information512 767 Longitudinal and Transverse Profile Information512 Number of longitudinal elevationchannelsInt32 Required513 Number of transverse elevationchannelsInt32 Required514 Number of longitudinal data points Int32 RequiredE2560 175TABLE 4 ContinuedTag Name Data Type Note
