Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It only takes a minute to sign up.
Sign up to join this community
I would like to use OSM data as shapefile so that I could do some computations. So far, I have successfully loaded the OSM file in ArcMap 10.3.1 using the ArcGIS Editor for OpenStreetMap. The attribute table only shows the primary physical features such as highway, building, natural, etc.
How do I show the other tags, like building:level, building:material, etc., in the attribute table?
In the documentation of OpenStreetMap Toolbox, there is a detailed description on how to extract specific tags, and it mentioned that:
When you download data from OSM using the ArcGIS Editor for OSM tools, you may find that certain information captured in the OSM tags is not downloaded with the features. This is because only information that is used for categorizing and symbolizing the data is downloaded automatically; if all the tag information was downloaded, the result would be an unwieldy attribute table with hundreds of columns, with most of the values being 'Null'.
If in your workflows you are always interested in a specific tag value, you should update the 'Download, Extract, and Symbolize OSM Data' model to include that tag.
Therefore, specific tags should be specified before start downloading of OSM data.
The above answer is unfortunately wrong. It is not true that you need to "specify tags before start downloading of OSM data." in order to be able to access other keys.
If there are missing attributes/keys, you can use the "OSM Attribute Selector", tool to add them to your Feature Class table. This tool is also part of the ArcGIS Editor for OpenStreetMap toolbox.
OSM XML files downloaded and converted using the toolbox contain a special binary field used as a key/value storage similar to PostGreSQL HSTORE. This field contains full tagging info for a specific feature.
By using the OSM Attribute Selector, you can add the missing keys/attributes to your existing Feature Class table, as that tool will extract the required information from the key/value storage and create a physical field for it.
