The Conversion toolbox contains tools that convert data between various formats.
| Toolset | Description |
|---|---|
The Excel toolset contains tools to convert Microsoft Excel files to and from tables. | |
|
With the tools in the From Raster toolset, you can convert the information in a raster dataset to a different type of data structure, such as a feature class, or to a different type of file, such as a binary or text file. | |
|
This toolset provides a tool to convert the features from WFS into a feature class to provide more functionality for those features. | |
The GPS toolset contains tools to convert between GPS Exchange Format (GPX) and feature classes. | |
The JSON toolset contains tools to convert features between JSON (JavaScript Object Notation) or GeoJSON and feature classes. JSON and GeoJSON are text-based, lightweight interchange data formats that are used to share GIS data between ArcGIS and other systems. These formats are language-agnostic, and most programming languages—such as Python, C#, Java, JavaScript, and so on—provide libraries to read, manipulate, and write JSON and GeoJSON. | |
The KML toolset contains tools to convert from Keyhole Markup Language (KML) to features in a geodatabase. | |
The LAS file format was designed to store discrete returns from lidar surveys in an efficient binary data structure, but over time, it has also been used to store point clouds from sources other than lidar. LAS files can be converted between different LAS file versions, point record formats, and compression types. It can also be exported to a raster to generate a surface model or an image from either the lidar intensity or the red-green-blue values associated with each point. | |
The SAS toolset contains tools to convert SAS datasets to and from tables. | |
Tools in the To CAD toolset convert geodatabase features to native CAD formats. You can use these tools in geoprocessing models and scripts to define your own conversion procedures. | |
COLLADA—which stands for COLLAborative Design Activity—is an open-standard XML format for storing 3D models. It is often used as an interchange format for 3D applications, and is the format for 3D textured objects stored inside KML. COLLADA files have the .dae file extension and can reference additional image files that act as textures draped onto the 3D object. Exporting multipatch features to COLLADA allows the sharing of complex analysis results with others and also provides a mechanism for updating textured 3D GIS data, such as buildings, using third-party software like SketchUp or 3DS Max. | |
dBASE tables are used to store attributes that can be joined to shapefile features by an attribute key. The Table to dBASE tool can be used to migrate INFO tables or even other dBASE tables so that they can be used by specific shapefiles. | |
The To Geodatabase toolset contains tools to convert and write data to a geodatabase. | |
The To GeoPackage toolset contains a tool to convert datasets into the OGC GeoPackage format. | |
Raster information can be stored in several data file formats that can be read by ArcGIS. With the To Raster toolset, you can convert these files into raster datasets. The toolset also contains tools that allow you to convert different types of feature information into rasters. | |
A shapefile is a simple, nontopological format for storing the geometric location and attribute information of geographic features. Geographic features in a shapefile can be represented by points, lines, or polygons (areas). | |
The tools in the Transit Feed (GTFS) toolset support the conversion of General Transit Feed Specification (GTFS) datasets into feature classes and tables that can be visualized in a map, used as input for further analysis, or used to construct a network dataset. Some of the tools allow you to create or update GTFS files. GTFS is the only worldwide standardized format for public transit data. It includes the locations of transit lines and stops as well as the schedules. |