Latest Contributions by George_Thompson

‎05-13-2014

If you guys are just deleting all the features out of the table and not deleting a selection of the table, I would try to use the Truncate Table tool. This tool will removed all the records/rows in a table. Truncate Table (Data Management): http://resources.arcgis.com/en/help/main/10.2/index.html#//00170000016z000000 *This will not work on a versioned data....... Be sure to test this on a test geodatabase with data first. Not on your production. 🙂 Hope this helps. -George

‎05-12-2014

This link may be what you are looking for. You basically use an OLE DB Connection. Connecting to a Microsoft Access database in ArcGIS: http://resources.arcgis.com/en/help/main/10.2/index.html#//005s00000023000000 George

‎05-07-2014

Hi Jerome, Thanks for the update. Based on the fact that the data is from 2007, the Non-Regulatory products would not be available. I do not know how to complete the entire process that you need, but am very familiar with the FEMA data.

‎05-05-2014

Jerome, I would not use the BFE lines to calculate the flood elevation at any point. These lines are estimates that are rounded up/down to the nearest foot. I would only use the Cross Section (S_XS) line to calculate the flood depth. You can rasterize the XS as a single elevation (using the 1% annual chance elevation), once you clip them to the floodway in your case, and then interpolate the depth between them. This will leave some room for error since there could be a large drop of elevation and there is not a XS nearby. For the flood data that you are using, was it done recently? Do you happen to have any Non-Regulatory products as part of the final deliverables? One other thing to look for may be to get the engineering models that were used to calculate the flood depths and use those rasters. Hopefully some of this helps.... George

‎04-30-2014

Just the geoprocessing history part of the metadata gets deleted. This can become rather large over time. The Documentation field is located in the SDE.GDB_ITEMS table, it is an XML field. I just tested this on a local instance of SQL Server(2012), using ArcGIS Desktop 10.1 SP1 w/QIP installed, and it just deleted the Geoprocessing History for the feature classes that I selected. I verified in the Metadata, for those feature classes, that the geoprocessing section is now empty. I only tested this on a 10.x geodatabase, not a 9.3.x version. System Tables of a Geodatabase in SQL Server Here is a link to a KB article that talks about how to do it via Python: Automate the process of deleting geoprocessing history I would recommend doing this after you have a full, verified backup of the geodatabase or on a test instance. This is in case there are any hiccups during the process. Hopefully this helps clear up some questions.

‎04-30-2014

Matt, I wonder if the geoprocessing history for those two feature classes is getting very large. Every time that you perform a GP process it adds to the metadata. The metadata is stored in a geodatabase system table. You may want to look into this add-in: Delete Geoprocessing History from Metadata Got the link from this post: http://forums.arcgis.com/threads/43399-metadata-geoprocessing-history I would only do this after you have a verified back of the geodatabase. Try it on the two feature classes in question -George

‎04-24-2014

How was the data copied over to the new SQL Server SDE geodatabase? Is the data in the feature dataset versioned? If so, you can not create a network on versioned data. See the tip section: http://resources.arcgis.com/en/help/main/10.2/index.html#/in_ArcCatalog/002r00000009000000/ Can you post a screenshot of the feature classes within the feature dataset that you are creating the network in?

‎04-24-2014

I am wondering if it has to do with the fact that most of the roads are a single polygon and it is creating the errors. There are also a bunch of very small polygons that barely have geometry to them. I think that they may get collapsed when loaded into the SQL geodatabase as part of the check when loading data. I have read you other post (http://forums.arcgis.com/threads/107598-Error-�??line-string-or-poly-boundary-is-self-intersecting�?�-error) and think that these issues are all related. What is you try to split the massive road polygon into smaller pieces for loading?

‎04-23-2014

Jamal, I tested in SQL Server and Oracle and got a different message when copying/pasting into the feature class in either. See attached screenshot. This error seems related to the other forum post that you have. My process was: Start an edit session, open the file geodatabase feature class table, select all features, copy, then paste into the SDE feature class. Hope this helps..... George

‎04-23-2014

Jamal, I noticed that in the third image (from the SDE geodatabase) that there are not feature extent coordinates (Top, bottom, left and right). The the second image (from the file geodatabase) has feature extent coordinates. That may be a direction to look into. I did see that the projections are the same. Just an observation...... George

‎04-18-2014

Hi Kelly, You can use the append geoprocessing tool to combine the tables to a single output table. This may be helpful. I would only recommend running this inside of a model and not in Python, because of the field matching. I tested loading a table in an enterprise geodatabase from tables in two different locations on my PC using the append tool with no issues. http://resources.arcgis.com/en/help/main/10.2/#/Append/001700000050000000/ Hope this helps! I just made it after Richards post..... George T.

‎04-15-2014

Hi Emad, This is expected behavior. Versioned views are created in every feature class that is versioned by design. The below is an exerpt from the help documentation: If you decide to register a feature dataset, stand-alone feature class, or table as versioned with the option to move edits to base, right-click it in the Catalog tree, point to Manage, then click Register As Versioned to open the Register As Versioned dialog box. Check Register the selected objects with the option to move edits to base. Checking this option causes edits that have been saved to the DEFAULT version, whether edited directly or merged from other versions, to be saved in the base (business) tables. Edits to other versions remain in the delta tables when you save. http://A quick tour of registering and unregistering data as versioned -Under the section Registering as versioned with the option to move edits to base. The underlined portion is the important section, if the edits are made to the DEFAULT version they will get pushed to the base table, but if they are made in other versions they remain in the delta tables. What is a versioned view? - http://resources.arcgis.com/en/help/main/10.2/index.html#/What_is_a_versioned_view/006z0000000q000000/ ...Versioned views are automatically created for tables or feature classes that are registered as versioned in ArcGIS 10.1 or later releases..... Hopefully this help! George

‎04-08-2014

Hi Holly, -What version of SQL Server are you using? -What ArcGIS client is being used to copy the feature classes? -What version is your SDE geodatabase in?(10.1, 10.2, 10.2.1, etc..)

‎04-03-2014

Angeleta, What RDBMS and O/S are you using for your 10.0 SDE? Thanks! George

‎03-04-2014

Jose, It sound like you SQL Server database is not a geodatabase. You can have feature classes in your SQL database, the feature geometry is stored as SQL Server Geometry. If you would like to use the full functionality of a geodatabase, I would recommend enabling it. This will allow you to import/export the raster data that you need. Enabling geodatabase functionality in an existing SQL Server database: http://resources.arcgis.com/en/help/main/10.2/#/Enabling_geodatabase_functionality_in_an_existing_SQL_Server_database/002q000000rq000000/

Online Status	Offline
Date Last Visited	11 hours ago

My Ideas

Latest Contributions by George_Thompson

Re: Delete Rows in model builder hangs

Re: onnect to MS Access Database

Re: Extrapolating Raster Data to fill a target area

Re: Extrapolating Raster Data to fill a target area

Re: Non-versioned data slowing way down

Re: Non-versioned data slowing way down

Re: Failed to build Geometric Network in SDE

Re: Error: �??the coordinates or measure are out of bound�?�,

Re: Error: �??the coordinates or measure are out of bound�?�,

Re: Error: �??the coordinates or measure are out of bound�?�,

Re: I need to merge two dbf tables

Re: versioned view creation - versioning not to base table

Re: Copy Feature SQL DBMS Error Invalid Precision Value

Re: Could not load data from the data source

Re: Upload a raster into SQL Server 2008 using ArcCatalog

Re: recent increase in timeouts from AGOL hosted f...

Re: Is there an outage? Can't open or create any ...

Re: Cannot edit branch versioned data

Re: Are Shape_Length and Shape__Length really the ...

Re: System Log Parser - How does it work?

Esri Certified Individuals

Cloud Computing