exportoracle-dbmsshapefilespatial-database
Shapefile is being imported to Oracle DB. Is there a tool to export this spatial data as a shapefile without writing any SQL (like you have to do with SQL Developer and GeoRaptor)?
EDIT: from all your answers I understand that there is no way for me to do action: import shapefile X to my database and later use some tool to export same shapefile X without using SQL or SQL like filtering… Unless I want to export whole layer which is not my interest.
I can't find the origin of this problem but I finally reached the final objective through another tool, with the GIS:
1) open the DXF file with QGIS
2) convert the DXF to Shapefile (right click on the layer > "Save as...")
3) use the Shapefiles to PostgreSQL converter in the menu option: Database > Split > "Import Shapefiles to PostgreSQL"
Trough this tool I imported the DXF to PostgreSQL without the wrong coordinates problem. I suppose that in the DXF to Shapefiles conversion the origin of the problem is solved.
If anyone have more information about what can origin that situation when I use the ogr2ogr tool it would be nice to know, because right know I cannot make that conversion (DXF to PostgreSQL) automatic (with an script that would execute the ogr2ogr command).
This problem has to do with spatial index. When you export the data into a new workspace, be it a file geodatabase or a shapefile, the export process creates a new feature class in the target workspace. The new feature class is then assigned a spatial index according to the default environment variables in your ArcGIS. There are some rules when setting these spatial index grid parameters, some of them have to do with the size of the grid created by the spatial index. You just have to make sure these parameters are properly set according to the following image.
In ArcMap Menu, point to Geoprocessing, and then select Environments. From the Environment Settings window, expand Geodatabase Advanced link. In the Output Spatial Grid 1 type 50, in the Output Spatial Grid 2 type 150 (make sure it is always larger), if you want to use a third spatial grid type in a number larger than 150, or simply 0 if you don't want to use it. Leave the rest of parameters to default settings.
Of course you can always set them all to zero if you don't want to use a spatial grid.
Then right click on the layer you want to export and point to Data, then Export.
Best Answer
GDAL - specifically ogr2ogr is the proper way to go. The base syntax for exporting one table is like this:
where
localhost:1521/orcl122is your database connection string. Note that you do not actually need to specify the output file format (as OGR assumes you want a shapefile by default):There are many things you can do in addition.
Select the rows to export:
Select the columns to export. Notice you can rename them.
Even use some pseudo-SQL syntax:
Finally, you can also export multiple tables:
In this case,
us_datais the name of a directory that will be created if it does not exist yet, and each table becomes a shapefile in that directory:And not specifying any table name will export all (spatial) tables from the schema you connect as:
EDIT:
Forgot to mention that you can use the same selection techniques (columns, rows, pseudo-sql) also when you import from shapefile (or from any other format).