Posted  by 

Opl Iso

  1. Opl Iso Naming
  2. Opl Iso Ps2
  3. Opl Iso
  4. Opl Iso Download
  5. Opl Iso Format

Table of Contents

  1. Open PS2 Loader (OPL) is a 100% Open source game and application loader for the PS2 and PS3 units. It now supports.ISO images on HDD, Ethernet SMB shares, and USB while also maintaining compatibility with USB Advance/Extreme format. It's now the most compatible homebrew loader and it should work without ps2load or change DNASXXX.IMG tricks.
  2. With this tool managing your OPL game collection was never so easy! With just some clicks you can: fix/change iso files names download game cover,disc, and screen-shots (batch and per game).

Open PS2 Loader (OPL) is a 100% Open source game and application loader for the PS2 and PS3 units. It now supports.ISO images on HDD, Ethernet SMB shares, and USB while also maintaining compatibility with USB Advance/Extreme format. It's now the most compatible homebrew loader and it should work without ps2load or change DNASXXX.IMG tricks.

This format is preliminary, it might change. Please send feedback if you usethis format!

The OPL (“Object Per Line”) format was created to allow easy access to andmanipulation of OSM data with typical UNIX command line tools such as grep,sed, and awk. Each object is on its own line with a linefeed at the end.

This makes some ad-hoc OSM data manipulation easy to do, but it is not as fastas some specialized tool.

OPL files are only about half the size of OSM XML files, when compressed (withgzip or bzip2) they are about the same size.

Opl Iso Naming

Osmium can read and write OPL files.

Each line of the file contains one OSM object (a node, way, or relation) or anOSM changeset. Lines end in a newline character.

Each line is made up of several fields separated by a space character.Each field is introduced by a specific character defining the type of thefield.

When OPL files are written by Osmium, the fields always appear in the sameorder in a line and are always all present (except when the file is writtenwithout metadata, see below).

Opl Iso Ps2

When Osmium parses a line, fields can appear in any order and all fields exceptthe first one are optional.

Fields in OSM data files

One of these fields is always the first:

Then in the given order:

If the file was written without metadata (using the option add_metadata=falsein Osmium), the fields v, d, c, t, i, and u are missing.

The t, N, M, and T fields can be empty. If the user is anonymous, the ‘User ID’will be 0 and the ‘Username’ field will be empty: .. i0 u ... If thenode is deleted, the ‘Longitude’ and ‘Latitude’ fields are empty. All otherfields always contain data.

Fields in OSM changeset files

For changesets the fields are:

The field e is empty when the changeset is not closed yet. The fields x,y, X, Y can be empty when no bounding box could be derived. The field kcan be 0. The field T can be empty if there are no tags.

Changeset discussions do not appear in the OPL format!

Numbers

Numbers, such as IDs and version numbers are written as decimal digits.

Timestamps

Timestamps are written in the same ISO 8601 format used in OSM XML files:yyyy-mm-ddThh:mm:ssZ. The time zone is always Z.

If the timestamp is not set, it will show up empty.

Deleted flag

The ‘Deleted flag’ shows whether an object version has been deleted (dD) oris visible (dV). For normal OSM data files this is always dV, but changefiles and osm history files can contain deleted objects.

Text in user names, tags, and roles

User names, tags, and relation member roles can contain any valid Unicodecharacter. Any characters that have special meaning in OPL files (space,newline, ‘,’ (comma), ‘=’ (equals), ‘@’, and ‘%’) have to be escaped as well asany non-printing characters.

Escaped characters are written as %xxxx%, ie a percent sign followed by thehex code of the Unicode code point followed by another percent sign. Thenumber of digits in the hex code is not fixed, but must be between 1 and 6,because all Unicode code points can be expressed in not more than 6 hex digits.

Any code reading OPL files has to cope with encoded and non-encoded characters(except that characters used in the OPL file with special meaning will alwaysbe encoded).

Currently there is a hard-coded list in the Osmium source of all the charactersthat don’t need escaping. This list is incomplete and subject to change.Currently two hex digits are used for code points less than 256 and at leastfour hex digits for numbers above that.

(An older version of OPL tried to encode characters as %xxxx with always 4hex digits, but this doesn’t work because Unicode code points can need moredigits.)

Tags

Tags are written in the form key=value. Several tags are joined by acommas (,). Any equal sign or comma in the key or value is escaped.

Nodes in ways

Nodes in ways are written as a comma-separated list of nID combinations.

Relation members

Relation members consist of the type n, w, or r, the ID, an at-sign (@)and the role. Several members are joined by commas (‘,’). Any at-sign or commain the roles is escaped.

Some lines have been broken in this description for easier reading, in thefile format they are not.

Here are some examples how the OPL format can be used to easily get some dataout of an OSM file.

Note that some of these commands generate quite a lot of output. You mightwant to add a less or redirect into a file. For larger OSM files some ofthese commands might take quite a while, so try them out on small files first.

Find all objects tagged highway=..: Toram skill guide.

Find all IDs of ways tagged highway=..:

Find all nodes with version > 9:

Opl Iso

Opl iso download

Find the first fields of the relation with the highest version number:

Find all objects with changeset ID 123:

Count how many objects were created in each hour of the day:

Find all closed ways:

Find all ways tagged with area=yes that are not closed:

Find all users who have created post boxes:

Opl Iso Download

Find all node IDs used in via roles in relations:

Opl Iso Format

Find all nodes having any tags igoring created_by tags:

Count tag key usage:

Order by object type, object id and version (ie the usual order for OSM files):

Create statistics on number of nodes in ways: