Difference between revisions of "Type Location"
Jump to navigation
Jump to search
| Line 48: | Line 48: | ||
| <code>signature</code> | | <code>signature</code> | ||
| <code>[LocationTypeID]</code> | | <code>[LocationTypeID]</code> | ||
| − | | | + | | Should contain a [[Location Types|defined constant]] value |
| − | | | ||
| − | |||
| − | |||
| − | |||
|- | |- | ||
| <code>offset</code> | | <code>offset</code> | ||
Revision as of 12:53, 12 May 2021
| Defined Constant | Type_Location
|
| File Type Value | 54 |
| Parent Type | None |
| Carve | No |
| Format Details | No |
| MIME Type | application/octet-stream
|
This represents a geographic coordinate.
Description
The message with this file type is specially encoded to hold the information in a [Location] record.
| Message Field | Database Column | Remarks |
|---|---|---|
file_type
|
Holds the value of Type_Location
| |
file_id
|
[FileID]
|
|
media_id
|
[MediaID]
|
|
parent_id
|
[ID]
|
|
signature
|
[LocationTypeID]
|
Should contain a defined constant value |
offset
|
[Latitude]
|
Multiplied by 1,000,000,000,000 |
length
|
[Longitude]
|
Multiplied by 1,000,000,000,000 |
types[0] - types[3]
|
[Altitude]
|
Multiplied by 1,000,000,000,000 |
types[4] - types[7]
|
[When]
|
In Windows FILETIME ticks |
depot_filename
|
[Label]
|
