OpenStreetMap は地理的なオブジェクトに意味づけするためにキー=値という形のタグを使います。 taginfo はこのようなタグに関する情報を様々な情報源から収集し、どのような意味なのか、どのように使われているかを分かりやすくします。
more: taginfo についての詳細... international: see: 他の taginfo サイトを表示... about: about_taginfo: title: taginfo について text: |OpenStreetMap uses tags to add meaning to geographic objects. There is no fixed list of those tags. New tags can be invented and used as needed. Everybody can come up with a new tag and add it to new or existing objects. This makes OpenStreetMap enormously flexible, but sometimes also a bit hard to work with.
Whether you are contributing to OSM or using the OSM data, there are always questions like: What tags do people use for feature X? What tags can I use for feature Y so that it appears properly on the map? Is the tag Z described on the wiki actually in use and where?
Taginfo helps you by showing statistics about which tags are actually in the database, how many people use those tags, where they are used and so on. It also gets information about tags from the wiki and from other places. Taginfo tries to bring together all information about tags to help you understand how they are used and what they mean. See a list of sources taginfo uses.
about_site: title: このサイトについて building_on_taginfo: title: Building on taginfo text: |You can use the data from taginfo in your own projects:
Taginfo data can be accessed through a REST API. See the API documentation for the details, some general information is on the OSM wiki. The servers running the taginfo API do not have unlimited resources. Please use the API responsibly. If in doubt contact the maintainers of the site you are using or talk to us on the mailing list.
If you want to play around with the data used by taginfo, you can download the regularly updated Sqlite database files. All the preprocessing is done for you. See the download page for a list of files. Note that some of these files can get quite large. If you want to download them regularly, contact the maintainers of the site you are using or talk to us on the mailing list.
The data available through taginfo is licenced under ODbL, the same license as the OpenStreetMap data.
software: title: The taginfo software text: |The taginfo software was created and is maintained by Jochen Topf. The web design was created by Christian Topf.
We need translators for the taginfo user interface. See the translations overview for languages that need some work. More information on how to help is on the OSM wiki.
All the software behind the taginfo sites is Open Source. You can get it on GitHub. For an overview see the page about the taginfo architecture on the OSM wiki.
You can run your own taginfo site, for instance with data for just your own country. Instructions are on the OSM wiki.
Bug reports and feature requests should be directed to the GitHub issue tracker. Or you can come talk to us on the mailing list.
Contact us on the taginfo-dev mailing list if you have questions or want to help.
sources: intro: |Taginfo collects data about OSM tags from several sources and brings them together for easy browsing and discovery.
Note that taginfo only displays this data. If you want to change it, you have to go back to the source.
list: title: List of Sources intro: Here is a list of currently used sources. More sources might be integrated in the future. description: db: |Statistics about keys, tags, and relation types are generated from the OSM database (or an extract) as well as the maps that show the geographic distribution of nodes and ways.
wiki: |The OSM Wiki is read and all Key:*, Tag:*, and Relation:* pages (in all the different languages) are analyzed. Descriptions, images, related tags, etc. are extracted from them.
languages: |Taginfo gets information about the different languages of the world, their codes, names, etc. from several IANA and Unicode registries.
projects: |Projects that use OSM tags in some way, such as editors, maps, routers, etc. See the project list.
updates: title: Updates intro: The taginfo data is updated regularly from the sources. data_until: Data until last_update_run: Last update run data_until_explanation: All edits until this time will be in the data, later edits might be. to: to download: intro: |Here you can download the databases used by taginfo. All the data is stored in Sqlite databases. The database files are then packed with bzip2.
If you don't want to download these databases, but need automated access to the data, you can also use the API.
file: File packed: Packed unpacked: Unpacked description: Description reports: intro: | Reports show the tag data from different angles. They often bring together data from several sources in interesting ways. Some of the reports can help with finding specific errors. list: List of all reports data_sources: Data sources used search: title: Search results you_were_searching_for: You were searching for fulltext: Full text no_keys: No keys found. no_values: No values found. no_tags: No tags found. no_match: No matches. compare: nothing_to_compare: There are no keys/tags to compare. Go to any key or tag page and add them. keys: intro: | This table shows all tag keys that exist in the database or in any of the other sources. tags: intro: | This table shows the most common tags in the database. relations: name: Relation types intro: Information about the different types of relations (indicated by the type tag). relations_of_type_tooltip: Number of relations of this type (and as percentage of all relations). prevalent_roles: Prevalent roles prevalent_roles_tooltip: Prevalent roles for this type of relation. no_information: No information roles_less_than_one_percent: no roles with more than 1% empty_role: empty role projects: intro: | This table shows all projects known to taginfo that use OSM tags in some way.Keys containing only lowercase latin letters (a to z) and the underscore (_). First and last characters must be letters. Most simple keys should fall into this category.
colon: tab: Colon title: Keys with colon intro: |Keys that have one or more colon (:) characters inside in addition to the letters (a to z) and underscores (_). The colon is often used as a hierarchy separator character.
letters: tab: Letters title: Keys with uppercase letters or letters from other scripts intro: |Lowercase letters from the latin script are usually preferred for keys, but sometimes uppercase letters are used (for instance for known abbreviations) or letters from other scripts (for instance for keys only relevant to an area where that script is used predominantly).
space: tab: Whitespace title: Keys with whitespace intro: |Keys that contain whitespace characters such as space, tab, new line, carriage return, or whitespace characters from other alphabets. Whitespace in keys can be confusing, especially at the beginning or end of the key, because they are invisible. Generally the whitespace should be removed or the underscore (_) used instead.
problem: tab: Problematic title: Keys with possibly problematic characters intro: |Keys that contain possibly problematic characters: =+/&<>;'"?%#@\, or control characters. These characters can be problematic, because they are used to quote strings in different programming languages or have special meanings in XML, HTML, URLs, and other places. The equal sign is used often as separator between tag keys and values. Keys that appear in this list are not necessarily wrong though. But in many cases they are just results of some error and should be fixed.
rest: tab: Rest title: All other keys intro: |Keys that don't fit in any of the other categories.
database_statistics: name: Database statistics objects_in_db: Number of objects in the database tags_in_db: Number of tags in the database distinct_keys: Number of distinct keys distinct_tags: Number of distinct tags nodes_in_db: Number of nodes in the database nodes_with_tags_in_db: Number of nodes with at least one tag nodes_with_tags_in_db_percent: Percentage of nodes with at least one tag tags_on_nodes: Number of tags on nodes avg_tags_per_tagged_node: Average number of tags per tagged node ways_in_db: Number of ways in the database closed_ways_in_db: Number of closed ways tags_on_ways: Number of tags on ways avg_tags_per_way: Average number of tags per way relations_in_db: Number of relations in the database tags_on_relations: Number of tags on relations avg_tags_per_relation: Average number of tags per relation frequently_used_keys_without_wiki_page: name: Frequently used keys without wiki page intro: |This table shows keys that appear more than 10 000 times in the OSM database but have no wiki page describing them. If you know anything about one of these keys, please create the wiki page by clicking on the link in the leftmost column and describe the key. Sometimes it might make sense to create a redirect to a different wiki page instead. To do this put just one line with #REDIRECT [[page name]] in the wiki page.
also_show_keys: Also show keys that have no English language wiki page but a page in some other language. table: create_wiki_page: Create wiki page... key_lengths: name: Key lengths intro: | Tag keys can be between 0 and 255 (Unicode) characters long. Very short or very long keys are often, but not always, errors. table: number_of_objects: Number of objects histogram: name: Histogram intro: This histogram shows how many keys there are of each length. key_length: Key length number_of_keys: Number of keys language_comparison_table_for_keys_in_the_wiki: name: Language comparison table for keys in the wiki icons: template: Page in wiki available and contains standard template. error: Page in wiki available and contains standard template, but couldn't be parsed. page: Page in wiki available but doesn't contain standard template. redirect: Page is a redirect. intro: | This table shows all tag keys for which there are wiki pages available and in what languages they are. languages: name: Languages intro: | OpenStreetMap is an international project. Tags and their descriptions can be in any language. This table lists the languages taginfo knows about and how many wiki pages there are in these languages documenting keys and tags, respectively. code: Code native_name: Native name english_name: English name wiki_key_pages: Wiki key pages wiki_tag_pages: Wiki tag pages wiki_pages_about_non_existing_keys: name: Wiki pages about non-existing keys intro: | This table shows keys for which a wiki page exists but there is not a single instance in the database. This is not necessarily an error (maybe somebody added the documentation in the wiki as preparation for using a key or the wiki page documents a now obsolete key), but it can also be a typo or other error. wiki_pages: Wiki pages name_tags: name: Variants of name tags intro: |This report shows information related to the naming of objects in OSM using the name tag and its variants.
overview: tab: Overview title: Overview bcp47: tab: BCP47 Subtags title: BCP47 Subtags filter: label: Show only subtags of type all: All language: Language script: Script region: Region variant: Variant intro: |The IETF defines language tags in its standard Tags for Identifying Languages (BCP47). Language tags consist of one or more subtags describing the language, script, variants, etc. The following list shows the subtags currently registered that are relevant for OSM. For more information see also the Wikipedia entry on IETF language tags and the langtag.net site.
Note that the data shown in this table is not from OpenStreetMap, it just shows the building blocks that can be used to describe languages irrespective of whether they are actually used in OSM.
similar_keys: name: Similar keys intro: | This report shows keys used very often and similar keys used very rarely. This exposes many misspellings of common keys, but is not perfect. Take care when fixing the data! Do NOT just mechanically edit those keys with search-and-replace. Look at each case individually and also fix other problems that you see. key_common: Commonly used keys key_rare: Rarely used keys count_common: Count count_rare: Count similarity: Similarity historic_development: name: Historic development intro: | Development of some important statistics over time. This data has been collected by taginfo, gaps are possible when taginfo didn't run on a day for some reason. keys: title: Unique keys tags: title: Unique tags relation_types: title: Unique relation types wiki_images: name: Wiki images intro: | Images used in the wiki to symbolize the keys in different languages. Sometimes the image from one or the other language variant is better. But sometimes it makes sense to have different images because of different cultural backgrounds or so.