Tag Info

Hot answers tagged

3

The two most likely causes (that I can think of) are; 1) The SDE Geodatabase configuration keyword includes a PRECISION statement and you likely have converted the feature class form high precision to single precision. -- In most storage projections (we use Stateplane, for example) there is insufficient precision to get fine detail so vertices coalesce and ...


2

It turns out that it was a problem of tolerance and resolution. When we created the feature datasets in the SDE geodatabase, we were simply accepting the default XY tolerance and XY resolution, which was not as precise as we needed it to be. We created new feature datasets and manually set the tolerance and resolution to match that of the feature class as it ...


2

If it's a file/personal based geodatabase - you can't access raster (yet). One of the developers for the http://www.gdal.org/drv_openfilegdb.html has mentioned working on that ability if funding was available. As far as SDE goes - I'm unsure.


2

Relational database software generally permits multiple tables with the same name if they are: Owned by different users, or Placed in different databases (for RDBMSes which support multiple containers within an instance) The usual way to distinguish which table is being referenced is by prefixing it with the owner name (and a period separator). The ...


2

To copy shapefiles from multiple folders into a single geodatabase, you could do this: import arcpy import os ws = #path to input folder dst = #path to output geodatabase for dirpath, dirnames, filenames in arcpy.da.Walk(ws,datatype="FeatureClass"): for file in filenames: print file filepath = os.path.join(dirpath,file) outpath = ...


2

You don't have to worry since the changes you perform in the geodatabase domain will be reflected in all feature classes which has fields using this domain. For instance, you have a gdb domain called StatesNames. It is of coded values type and has a couple of code-value pairs: TX - Texxas CA - Callifornia NY - New YYork When users created features, they ...


2

I would agree that the ideal solution would be to upgrade to ArcGIS Server so you can take advantage of replication capabilities built into ArcSDE technology. You can get more information about ArcGIS's Distributed Data capabilities at http://resources.arcgis.com/en/help/main/10.1/index.html#/Understanding_distributed_data/003n000000ts000000/ In general ...


1

Posted this in comments, but got scolded for too long a discussion in comments. May get scolded for posting this in answers, but not sure where else to place it. Chat was suggested, but it's not my thread, so anyway... Ok, point taken, but the value in the field is the string 'CKT69KV', not '69'. If it was 69, you'd see 69 - CKT69 in the Unique Values box. ...


1

Your workflow will not technically be supported, so yes it is dangerous. Consider this documentation: Replication and geodatabase releases (10.2.x) http://resources.arcgis.com/en/help/main/10.2/index.html#//003n000000z3000000 Geodatabases built using previous versions of ArcGIS do not support some of the newer functions of ArcGIS. Consequently, if ...


1

QGIS doesn't support ESRI Geodatabase raster. The only solution is to open the database in ArcGIS an export the raster GeoTiff. Right click in arcCatalog, Export/Raster to different Format... Then choose a folder and fileaname to write to if the extension is .tif, it will be readable in QGIS


1

Are you talking about a two-way replica? Go into ArcCatalog and right click on the database. Go to Distributed Geodatabases and Manage Replicas. You can right click on the replica name and remove it. As far as changes to the original database. Depending on what you mean, you can use the Export Replica Schema tool on the original database and them import ...



Only top voted, non community-wiki answers of a minimum length are eligible