1、Designation: E 2560 07Standard Specification forData Format for Pavement Profile1This standard is issued under the fixed designation E 2560; the number immediately following the designation indicates the year oforiginal adoption or, in the case of revision, the year of last revision. A number in par
2、entheses indicates the year of last reapproval. Asuperscript epsilon (e) indicates an editorial change since the last revision or reapproval.1. Scope1.1 This specification describes a data file format for pave-ment profile.1.2 This specification describes the variable sizes of all datathat will be s
3、tored in the file. The file is in binary format, andis fully documented in this specification.1.3 This specification is designed to be independent ofhardware platforms, computer languages, and Operating Sys-tem (OS)1.4 The values stated in SI units are to be regarded as thestandard. The values given
4、 in parentheses are for informationonly.1.5 This standard does not purport to address all of thesafety concerns, if any, associated with its use. It is theresponsibility of the user of this standard to establish appro-priate safety and health practices and determine the applica-bility of regulatory
5、limitations prior to use.2. Referenced Documents2.1 ASTM Standards:2E 867 Terminology Relating to Vehicle-Pavement Systems2.2 IEEE Standards:3IEEE 754 Binary Floating-Point Arithmetic (1985, Reaf-firmed 1990)3. Terminology3.1 Terminology used in this specification conforms to thedefinitions included
6、 in Terminology E 867.3.2 Definitions of Terms Specific to This Standard:3.3 Int32data type for a 32bit, signed integer.3.4 singledata type for a 32bit, signed real number, suchas, single precision IEEE floating point.3.5 4-byte stringan ASCII string of 4 characters in length.No null character is in
7、cluded at the end of the string.3.6 8-byte stringan ASCII string of 8 characters in length.No null character is included at the end of the string.3.7 array, (Int32, single)Sequence of data of the specifieddata type. Only the values are stored, but no information aboutthe array is stored.3.8 array (s
8、ingle)ASCII strings separated by a tab. Thereis no tab after the last string.3.9 Symbols:3.9.1 ntotal channels of elevation data.3.9.2 mtotal number of test locations (that is, data points).4. Profile Data Specifications4.1 File Structure4.1.1 The general file structure is divided into five sections
9、:(1) File Header, (2) Metadata; (3) Longitudinal Profile Data;(4) Transverse Profile Data; and (5) File Trailer. The fivesections are stored sequentially. (See Fig. 1.)4.1.2 Each of these portions of the file is described in thefollowing sections as well as the data types and other descrip-tors that
10、 will be required by the file. The data will be written tothe file sequentially, with the offsets listed in the file header asguides to find various portions of the file. It is important to notethat all offsets are relative to the beginning of the file. Becauseoffset values may not be known at the t
11、ime of writing the fileheader, these values need not be written. However, spare spacemust still be reserved for the offsets so that values can beupdated when known.4.2 File Header4.2.1 File header contains the information pertaining to thedata file type, software version information, and information
12、about the data contained (Table 1).4.3 Metadata4.3.1 Metadata is structured, descriptive information about aresource, or data about data. Using metadata in the binary fileformat will allow generic operating on the data informationabout which the reader software has no prior knowledge. Also,1This tes
13、t method is under the jurisdiction of ASTM Committee E17 on Vehicle- Pavement Systems and is the direct responsibility of Subcommittee E17.31 onMethods for Measuring Profile and Roughness.Current edition approved April 1, 2007. Published April 2007.2For referenced ASTM standards, visit the ASTM webs
14、ite, www.astm.org, orcontact ASTM Customer Service at serviceastm.org. For Annual Book of ASTMStandards volume information, refer to the standards Document Summary page onthe ASTM website.3Available from Institute of Electrical and Electronics Engineers, Inc. (IEEE),445 Hoes Ln., P.O. Box 1331, Pisc
15、ataway, NJ 08854-1331, http:/www.ieee.org.1Copyright ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.metadata will allow scalable evolution of the data descriptionwithout requiring simultaneous upgrades to all reader software.4.3.2 The first va
16、lue in the metadata portion will provide thenumber of metadata entries (MDE) and the information regard-ing each of them. Table 2 shows the information required toconstruct an appropriate MDE.4.3.3 The metadata tags are listed in Table 3, and can beused in any number or order. If no metadata tags ex
17、ist, numberof MDEs = 0.4.3.4 The names of the standard metadata entries (see Table8) are not stored in the metadata entry to conserve space andmore importantly, to allow for localization, that is, the file isnot tied to one written language. User-defined metadata entriescannot be arrays and the data
18、 type is always String.4.3.5 The storage convention for empty arrays is to store aone-byte value of the same data type as the array. For example,an array of singles 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-wis
19、e 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-processing to speed upsoftware reading and writing.4.4.2 If the data storage format, from metadata tag #522 inTable 9, equals 1 (that is, lo
20、cation-wise), the longitudinal datawill be stored as a sequence of current longitudinal distancefollowed by corresponding elevations of longitudinal sensors atFIG. 1 Layout of the File StructureTABLE 1 File HeaderVariable Name Data Type Data Default ValueSignature 4-byte string identifies file as be
21、ing written in the Standard Pavement ProfileFormat”SPPF”Version 4-byte string identifies the version number of the file format “1.01”SW version 8-byte string identifier of the software that produced the fire for example, “TGPA1.00”Metadata offset Int32 offset in bytes to the beginning of the metadat
22、a N/ALongitudinal offset Int32 offset in bytes to the beginning of the longitudinal profile data N/ATransverse data offset Int32 offset in bytes to the beginning of the transverse profile data N/ATABLE 2 MetadataVariable Name Data Type DataNumber of MDEs Int32 Number of MDEsE2560072NOTEAny tags not
23、listed below 1024 are reserved 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(yy
24、yymmdd) String262 Time data was 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 Near
25、by city name String281 Roadway 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
26、 Reference marker or milepost 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 origina
27、l file format(yyyymmdd) String298 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 String
28、512767: Longitudinal and Transverse 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
29、longitudinal data points Single517 longitudinal distance between transverse profiles Singleyes 518 Longitudinal sensor spacing from vehicle center (negative values tothe left of vehicle center, positive to the right)Array (single)519 Transverse sensor spacing from vehicle center (negative values tot
30、he left of vehicle center, positive 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 Pr
31、ofile offset (if linear distance adjustment or correlation isperformed)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 Unit
32、s Informationyes 768 Units for 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 Reserv
33、ed for user defined metadata entries StringE2560073this location, beginning at the left side of the vehicle. The nextblock of storage will store longitudinal distance and allelevation data for the next location, and so on. However, thelocation may not need to be stored if a specific data interval is
34、given. (See Fig. 2.)4.4.2.1 In general, if a location and elevation channels arerecorded for each test location, every set of n+1 Singles (onedistance data and n channels of elevation data) will be read asone profile location. If a specific data interval is included in themetadata, only n Singles wi
35、ll be read for each location. Forexample, if a standard interval exists and a single channel ofprofile data is present, only one Single will be read for eachlocation. If two are present, then two Singles will be read perpoint.4.4.2.2 The location-wise format is recommended for pro-filer data acquisi
36、tion software. Storing the data after everysampling location allows for immediate writing to protectagainst data loss and reduce memory requirements.4.4.3 If the data storage format from metadata #522 in Table9 equals 2 (that is, array-wise), then the longitudinal data willbe stored as a sequence of
37、 the longitudinal distance arrayfollowed by the elevation array of each longitudinal sensor,beginning at the left side of the vehicle for all locations. (SeeFig. 3.)4.4.3.1 In general, if distance and elevation channels arerecorded for each test location, n+1 sets (one distance channeland n channels
38、 of elevation data) of m Singles will be stored insequence. If a specific data interval is included in the metadata,only n sets of m Singles will be stored sequentially, withdistance being calculated from the beginning of the testlocation by the software. For example, if a standard intervalexists an
39、d a single channel of profile data is present, only oneset of Singles will be stored. If two are present, then two setsof m Singles will be stored sequentially.4.4.3.2 This data format is recommended for software thatreads and writes the data during post-processing. Data stored asone continuous arra
40、y (array-wise) can be read and processedmuch faster than the location-wise storage format.4.5 Transverse Profile Data4.5.1 The transverse elevation readings are treated the sameas the longitudinal data.4.6 File Trailer4.6.1 The file trailer is used to signal the end of the file. (SeeTable 12.)5. Key
41、words5.1 longitudinal profile; pavement profile; profile data speci-fications; transverse profileTABLE 4 UnitsValue of Tags 7681024 UnitDistance and Elevation73 Mils1 Inches2 Feet4 Miles5 Milimetres6 Centimetres7 Metres8 KilometresSpeed24 Feet/second28 Miles/hour27 Metres/second26 Kilometres/hourTem
42、perature35 Degrees Fahrenheit33 Degrees CentigradeTime36 SecondsTABLE 5 Pavement Surface TypesValue of Tag 285 Pavement Surface Type0 Undefined1 Portland cement concrete2 asphalt concrete3 UnpavedTABLE 6 Current Climactic ConditionsValue of Tag 293 Climactic Conditions0 Undefined1 Sunny2 Hazy/fog3 P
43、artly cloudy4 Mostly cloudy5 Overcast6 Light rain/snow7 Moderate rain8 Heavy rainTABLE 7 Data TypesIndexAData Type Size (bytes) Description8 String varies one byte ASCII (no unicode support)3 Int32 4 32-bit signed integer4 Single 4 Single precision IEEE floating pointAData type index values follow M
44、icrosoft programming conventions.E2560074TABLE 8 Metadata EntriesVariable name Data type DataTag of MDE Int32 metadata tag (see Table 3)Data type of MDE Int32 data type index of MDE (see Table 7)Array size Int32 “-1” if not an array. “0” if array is empty. numbers greater than 0 specify the number o
45、f elements inthe array. Even though arrays of strings are stored differently thanother types of array, an array size should still be specified here.Count Int32 for data type “string” and array (“string”), count = the number ofbytes in the string. for other data types, count = 1.Name length Int32 for
46、 metadata entries listed in Table 3,thisis0.foruser-defined entries, this value is the length of the name.Name String name of the metadataMDE varies information associated with tag of MDETABLE 9 Data Storage FormatValue of Tag 522 Data Storage Format1 Location-wise2 Array-wiseTABLE 10 Profiler TypeV
47、alue of Tag 300 Description1 High speed2 Light weight3 ManualTABLE 11 Channel TypesValue of Tag 523 Description1 Left wheel path2 Right wheel path3 CenterlineTABLE 12 File TrailerVariable Name Data type Data Default ValueEnd of file 3-byte string indicates the end of the file “”E2560075ASTM Internat
48、ional takes no position respecting the validity of any patent rights asserted in connection with any item mentionedin this standard. Users of this standard are expressly advised that determination of the validity of any such patent rights, and the riskof infringement of such rights, are entirely the
49、ir own responsibility.This standard is subject to revision at any time by the responsible technical committee and must be reviewed every five years andif not revised, either reapproved or withdrawn. Your comments are invited either for revision of this standard or for additional standardsand should be addressed to ASTM International Headquarters. Your comments will receive careful consideration at a meeting of theresponsible technical committee, which you may attend. If you feel that your comments have not received a fair hearing you shouldmake your views
