OAR Format 0.1

From OpenSimulator

(Difference between revisions)
Jump to: navigation, search
m (Added "turtle track" navigation, added the "What is the OAR 0.1 format?" main title, and also added the "See Also" heading with page links. Please ignore.)
m (Robot: Replacing 'OpenSim' to 'OpenSimulator', which is the precise name)
 
(19 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
{{Template:Quicklinks}}
+
{{Quicklinks}}
<br />
+
  
[[Technical Reference | Technical Reference]] -> [[Technical Reference/terms | Terms]] -> [[OAR_Format | OAR Format]] -> [[Technical Reference/terms/OAR_format_0.1 | OAR format 0.1]]
+
= What is the OAR 0.1 format? =
 
+
=What is the OAR 0.1 format?=
+
  
 
== Detail ==
 
== Detail ==
  
At the present time, a region archive is a gzipped tar file (tar.gz) in the the original unix tar format (not USTAR). This can be extracted and created with standard tools ([http://www.7-zip.org/ 7-zip] on Windows). The structure of the archive is as follows
+
A region archive is a gzipped tar file (tar.gz) with the extension .oar. This can be extracted and created with standard tools ([http://www.7-zip.org/ 7-zip] on Windows). The structure of the archive is as follows
  
 
  archive.xml
 
  archive.xml
Line 18: Line 15:
 
=== archive.xml ===
 
=== archive.xml ===
  
This is the archive control file. At the moment it contains only a major and minor version number, to allow compatibility with future format changes.
+
This is the archive control file. At the moment it contains only a major and minor version number, to allow compatibility with future format changes.
  
 
=== assets/ ===
 
=== assets/ ===
  
This directory contains all the assets in the archive. Each filename has the following format
+
This directory contains all the assets in the archive. Each filename has the following format
  
  ''uuid''_''asset type''.''asset extension''
+
  <uuid>_<asset type>.<asset extension>
  
The ''uuid'' section must always be present and form a valid uuid - it is used directly as the uuid for that asset. The ''asset type'' and ''asset extension'' are used to identify the type of asset and the ''asset extension'' allows the asset to be associated with different editors on platforms such as Windows. For instance, a script will always have the asset type and extension script.lsl. A full list of asset types and extensions can be found in the file  
+
The ''uuid'' section must always be present and form a valid uuid - it is used directly as the uuid for that asset. The ''asset type'' and ''asset extension'' are used to identify the type of asset and the ''asset extension'' allows the asset to be associated with different editors on platforms such as Windows. For instance, a script will always have the asset type and extension script.lsl. A full list of asset types and extensions can be found in the file  
  
  OpenSim/Region/Environment/Modules/World/Archiver/ArchiveConstants.cs
+
  OpenSim/Framework/Serialization/ArchiveConstants.cs
  
in the OpenSim distribution.
+
in the OpenSimulator distribution.
  
 
=== objects/ ===
 
=== objects/ ===
  
Each individual file in here is an object in the region (where an object [linkset] can be composed of many prims). The file format used is OpenSim's XML2 format. Each filename has the following structure by default
+
Each individual file in here is an object in the region (where an object [linkset] can be composed of many prims). The file format used is OpenSim's XML2 format (which unfortunately is not yet documented). Each filename has the following structure by default
  
  ''Object name''_''x''-''y''-''z''__''uuid''.xml
+
  <Object name>_<x>-<y>-<z>__<uuid>.xml
  
Unlike asset filenames, any component of this name can be changed without affecting any attributes of the object itself - this information is taken from the xml instead. Indeed, this file can have any name - there is no need for any of the sections to be present. An example object file name is
+
Unlike asset filenames, any component of this name can be changed without affecting any attributes of the object itself - this information is taken from the xml instead. Indeed, this file can have any name - there is no need for any of the sections to be present. An example object file name is
  
 
  Primitive_154-121-062__9be68fdd-f740-4a0f-9675-dfbbb536b946.xml
 
  Primitive_154-121-062__9be68fdd-f740-4a0f-9675-dfbbb536b946.xml
Line 44: Line 41:
 
=== terrains/ ===
 
=== terrains/ ===
  
This contains the terrain file for the region, stored in RAW format. The filename must end with .r32. For example,
+
This contains the terrain file for the region, stored in RAW format. The filename must end with .r32. For example,
  
  OpenSim Test.r32
+
  OpenSimulator Test.r32
  
 
= See Also =
 
= See Also =
  
* [[Status|Main Status Page]]
+
* [[OpenSim Archives|How to use OpenSimulator Archives (OAR)]]
* [[Technical_Reference|Technical Reference Page]]
+
* [[OAR Format 0.1]]
* [[OAR_Format| What is OAR Format?]]
+
* [[OAR Format 0.2]]
* [[OpenSim_Archives|How to use OpenSim Archives (OAR)]]
+
* [[OAR format 0.1 | OAR format 0.1]]
+
* [[OAR format 0.2]]
+
  
 
[[Category:Users]]
 
[[Category:Users]]
 
[[Category:Support]]
 
[[Category:Support]]
[[Category:Tech Reference]]  
+
[[Category:Tech Reference]]
 
[[Category:Help]]
 
[[Category:Help]]
 
[[Category:Configuration]]
 
[[Category:Configuration]]
[[Category:Getting_Started]]
+
[[Category:Getting Started]]
 
[[Category:Development]]
 
[[Category:Development]]

Latest revision as of 23:45, 3 March 2012

[edit] What is the OAR 0.1 format?

[edit] Detail

A region archive is a gzipped tar file (tar.gz) with the extension .oar. This can be extracted and created with standard tools (7-zip on Windows). The structure of the archive is as follows

archive.xml
assets/
objects/
terrains/

[edit] archive.xml

This is the archive control file. At the moment it contains only a major and minor version number, to allow compatibility with future format changes.

[edit] assets/

This directory contains all the assets in the archive. Each filename has the following format

<uuid>_<asset type>.<asset extension>

The uuid section must always be present and form a valid uuid - it is used directly as the uuid for that asset. The asset type and asset extension are used to identify the type of asset and the asset extension allows the asset to be associated with different editors on platforms such as Windows. For instance, a script will always have the asset type and extension script.lsl. A full list of asset types and extensions can be found in the file

OpenSim/Framework/Serialization/ArchiveConstants.cs

in the OpenSimulator distribution.

[edit] objects/

Each individual file in here is an object in the region (where an object [linkset] can be composed of many prims). The file format used is OpenSim's XML2 format (which unfortunately is not yet documented). Each filename has the following structure by default

<Object name>_<x>-<y>-<z>__<uuid>.xml

Unlike asset filenames, any component of this name can be changed without affecting any attributes of the object itself - this information is taken from the xml instead. Indeed, this file can have any name - there is no need for any of the sections to be present. An example object file name is

Primitive_154-121-062__9be68fdd-f740-4a0f-9675-dfbbb536b946.xml

[edit] terrains/

This contains the terrain file for the region, stored in RAW format. The filename must end with .r32. For example,

OpenSimulator Test.r32

[edit] See Also

Personal tools
General
About This Wiki