Browsing Japanese translation

256.

Table layout

257.

The schema is an identifier naming a region on the planet. According to the %splanet splitting map%s the planet is split in rectangular parts to get roughly equally sized dump files. Consider the schema as a prefix for the error_id.

258.

A number identifying errors, starting from 1 for each schema. An error_id is worth nothing if you don't know the schema!

259.

numeric representation of the type of error. Error types are assigned in blocks of 10s (20, 30, 40...). They correspond with the name of the script file doing the checking.

260.

Error types may be sub-typed (281, 282 etc.). Subtyped error checking routines test for different aspects related to a single topic (in the example 280 means "boundaries", 281 means "missing name[ for boundaries]" and 282 means "missing admin level[ for boundaries]"). Subtyped error types are rendered as groups that may be collapsed on the web site.

261.

textual representation (short name) of the type of error. On sub-typed error types you may want to prepend the error_name that belongs to the main number to make the name complete.

262.

one of node/way/relation

263.

an OSM node_id, way_id or relation_id

264.

one of new, reopened, ignore_temporarily, ignore. You won't see any 'cleared' errors because the dump contains active errors only. Temporarily ignored errors are issues fixed by a user who really hopes to have fixed it. Temporarily ignored errors will jump back in the 'new' state with the next update if the error isn't really fixed. Ignored errors are issues that are simply false positives and should never come back just because KeepRight is wrong and this exception cannot be included in the ruleset.

265.

Errors that were once cleared and come back at some point in time later are put in the <em>reopened</em> state. Please note that this may happen due to runtime-errors in the scripts. So you may just consider <em>new</em> and <em>reopened</em> the same.