The shape files, known as .shp files, will be Quaternary formats in a matter of technology but we cannot avoid that they have been popularized as much as ArcView 3x was. This is the reason why they are still widely used, to the extent that most geospatial platforms have developed routines to operate with them. Inclusive GvSIG can Read and edit them.
An alternative widely used before was to export from ESRI to dxf, with the disadvantage of losing the tabular data. In this case, we will see how to interact with these Velociraptors using
AutoCAD AutoCAD Map, I learned about this process through a gentle response from Txus in the Cartesia forum.
1. Not just any AutoCAD
A shape file consists of a geometry, contained in the .shp extension file, then the tabular data contained in the .dbf file and the index that links it to the .shx.
To read a file of these is required AutoCAD Map, or Civil 3D; It is also worth clarifying that unlike Bentley Map GvSIG
It is not possible to read the file natively but it is viable via an FDO connection.
The example I'm doing with AutoCAD Civil 3D 2008.
2. Importing .shp files
To do this you have to do it in the menu:
"map / tools / import", it allows you to choose both .shp and E00 files and even coverages of the initial ArcInfo workstation.
It also allows importing from programs such as Mapinfo (.mif .tab) and Microstation Geographics (.dgn). It seems to me a good opening of AutoCAD to foreign formats, because when importing from a dgn in this way it is possible to capture the mslink and other customizations such as exploiting complex objects and converting cells to blocks at once.
The panel then requests to be assigned projection and the possibility of importing only one zone.
It is also possible to specify whether polygons are to be converted to closed polylines.
3. Exporting .shp
To export the process is similar, "map / tools / export", then the export must be done separately, the lines, points, polygons and texts. The selection can be done manually, by layers or by feature classes and if you have defined topologies, the better.
It is also necessary to define the attributes of the objects that will construct the dbf columns, the projection of the output file and the conversion of closed polylines to polygons.
In this to import and export exists the alternative to create a profile to not be defining conditions every time, this would be saved as a .ipf file that can be loaded every time the process will be done.