Latest Contributions by WilliamCraft

Compress a versioned database to state 0 can be done only after deleting the versions (excluding the sde.DEFAULT version). First you have to Reconcile and post all versions which are ready to be applied to the DEFAULT version. Alternatively, delete the versions and Compress the database. This is typically the way in which people achieve state 0, yes.  However, as I eluded to above, it is possible to go to state 0 without deleting child versions of SDE.DEFAULT.  We've done it with replica versions and with other versions.  As long as the state ID of your child versions match the state ID of your SDE.DEFAULT version, compressing will achieve state 0 without having to delete those versions.  For our replica versions, this has typically involved a sequencing of compress followed by replica synchronization followed by compress again.  Doing this allows us to avoid the lengthy task of dropping and rebuilding our replicas when state 0 is needed.  As long as everything is reconciled and posted, this works.  While certainly not the most common workflow, it has proved technically feasible. ... View more

You do need disconnected replication, and your design is correct at a high level.  From what you are indicating, it seems like your server and your client server are not on the same network and can only exchange information via FTP.  My recommendation is that you set up one-way, parent-to-child replication where your child is a file geodatabase.  Using the disconnected replication tools, you will be able to produce an XML document to build your initial replica, then create data messages (e.g., change packets) from the parent, ship them to your client server via FTP, apply them to your child replica thereafter, and send back acknowledgements from the child to the parent.  Eventually, parts of this workflow (or all of it depending on our FTP capabilities) can be automated once you feel comfortable with everything.  If I have your configuration generally correct, then here's how I would approach things: 1. Identify the feature classes that you would like to have participate in the replica, then add Global IDs to them via ArcCatalog.  If any of those feature classes exist in a feature dataset, you'll have to add global IDs at the feature dataset level.  Add global IDs to any tables that will need to participate as well, all of which need to be registered with the geodatabase.  Every object class participating in replication must be registered as versioned, and every object class must be editable (in other words, the owner of the replica... the user account in the SDE connection file you use to pick your participating data... must have RW privileges on the base tables and any delta tables).  Also, make sure your SDE connection file uses the transactional version from which you want to create the replica to begin with, typically SDE.DEFAULT is sufficient for most organizations.  2. Create an empty file geodatabase (it needs to exist beforehand) and then use the Create Replica Wizard from the Distributed Geodatabase toolbar in ArcGIS Desktop in order to produce an XML document: http://resources.arcgis.com/en/help/main/10.2/index.html#/The_Create_Replica_wizard/003n000000w6000000/ 3. Once the XML document is created, move it from your server to your client server via FTP (you may want to zip it depending on its size) and import it into your empty file geodatabase: http://resources.arcgis.com/en/help/main/10.2/index.html#/Replicas_in_a_disconnected_environment/003n000000rm000000/ 4. After versioned edits are made in the parent and then reconciled and posted, you can export a data message on your server which is essentially an XML change packet containing attribute and geometry edits (also, some very basic schema changes are allowed depending on how you have created and configured your replica): http://resources.arcgis.com/en/help/main/10.2/index.html#/Exporting_a_data_change_message/003n000000s2000000/ 5. Copy or move the XML data message from your server to your client server via FTP.  6. From ArcGIS Desktop on your client server, import the data message XML file into your child replica: http://resources.arcgis.com/en/help/main/10.2/index.html#/Importing_a_data_change_message/003n000000sm000000/ 7. From ArcGIS Desktop on your client server, export an acknowledgement XML file which is what will be used to tell your parent replica that the child replica now matches and contains the correct generation number: http://resources.arcgis.com/en/help/main/10.2/index.html#/Exporting_an_acknowledgment_message/003n000000ss000000/ 8. Copy or move the XML acknowledgement file from your client server to your server via FTP. 9. From ArcGIS Desktop on your server, import the acknowledgement XML file from the client server: http://resources.arcgis.com/en/help/main/10.2/index.html#/Importing_a_data_change_message/003n000000sm000000/ This completes a full round of the replication process and synchronization process.  I actually see this being eventually automated into three (possibly two) scripts: Script A: Uses Python (arcpy) and basic FTP commands via command prompt to achieve steps 4 and 5, and runs on your server possibly as a scheduled task.  Script B: Uses Python (arcpy) and basic FTP commands via command prompt to achieve steps 6 through 8, and runs on client server possibly as a scheduled task.  Script C: Uses Python (arcpy) to achieve step 9, and runs on your server possibly as a scheduled task.  Scripts A and C might be able to be combined into one script.  Also, steps 1 through 3 are manually performed one time and aren't part of the repetitive workflow thereafter.  If your FTP server only accepts SFTP (different than FTPS), you will need a third-party SFTP utility that can handle scripted commands.  There are some free ones out there. ... View more

Customizing Portal for ArcGIS can be a lengthy and involved process, and it's different for everyone.  I would suggest reviewing Esri's documentation before making changes: http://resources.arcgis.com/en/help/main/10.2/index.html#/About_configuring_the_portal_website/017s00000075000000/ ... View more

If the version dates seem to sporadically change, I guess I would first ask how reconcile and post is being performed and whether conflicts are resolved in favor of the parent or child versions in each case.  How often are you reonciling and posting?  How often do you compress (even if not to State 0)? ... View more

Thanks for your response!  I converted the xyz points to a "3D aware" feature class like you said and created the TIN.  One question, why does it look completely different from the feature class created just by uploading my points through "display xy data" and then "export as feature class"??  What is the main difference with something that is "3D aware"?  Also, is there a way that I can view the map in 3D? Would I have to have another program?  Thanks again for your help, I was able to create the map I needed, just wanting to know why it is different so it makes more sense to me!  Mitchell What I meant by "3D aware" was simply that the output from step 1 would be a feature class with a field for Z values, mainly because you are using X, Y, and Z values from your text file as input.  It's certainly not a technical term 🙂  I am not sure why it looks different than the alternative workflow you described; however if you're aiming for surface volume then I'd stick with the 3D Analyst tools (either from the 3D Analyst toolbar or from the 3D Analyst geoprocessing toolset in ArcToolbox).  You can view 3D data in a product called ArcScene.  If the workflow I provided gave you the output you wanted, please mark the correct answer with the green check.  Also remember to up-vote helpful answers from others in this thread. ... View more

Why not just query the geodatabases directly with SQL if you have the credentials for the SDE user?  Here's an example of a query that can be used for an Oracle database (tested with 11.2.0.2.0 and ArcSDE 10.2.1): SELECT r.OWNER, r.TABLE_NAME, CASE     WHEN r.OBJECT_FLAGS IN ('3','11','2051','4099','0','24583','8195') THEN 'TABLE'     WHEN r.OBJECT_FLAGS IN ('7','15','16391','16399','114693','114703') THEN 'FEATURE CLASS'     WHEN r.OBJECT_FLAGS IN ('71') THEN 'RASTER' END OBJECT_FLAGS FROM ( SELECT OWNER, TABLE_NAME, OBJECT_FLAGS FROM SDE.TABLE_REGISTRY ORDER BY OWNER, TABLE_NAME) r FULL JOIN SDE.LAYERS l ON l.OWNER = r.owner AND l.TABLE_NAME = r.TABLE_NAME; You would run the query above in every database to get a report of the object classes that are registered with the geodatabase.  It will identify whether the object class is a table, feature class, or raster.  If you want to get fancy and you have Oracle, you can create DB links and UNION multiple queries together (one for each database) in order to run it against all databases at once.  The query above would only require minor edits to work with SQL Server, as well.  If you databases are all in the same instance, you could UNION multiple queries together just like with Oracle... except with SQL Server there are no DB links.  Instead, you'd simply need to qualify your table references in the query above with DATABASE.SCHEMA.TABLE_NAME syntax. ... View more

I have some total station points in x,y,z (.txt) file that I want to make a 3D shape and create a volume from.  The points are taken in small basins (as small as 50 gallons) and I do not need any spatial reference to the surrounding area, just strictly trying to find volume of a 3D surface made from these points.  So far I've kind of figured out some of the tools to use, like Surface Volume Analyst in the 3D analyst toolbar, but I'm having trouble putting it all into a process from start to finish.  Can any pros here help make sense of this?  I have no problem getting the points into ArcGIS, but I am having trouble correctly interpolating and making a surface that I can then calculate volume from.  Also, I'm using ArcMap 10.1.  Thanks for any comments! Mitchell You are correct in that the Surface Volume tools from the 3D Analyst toolbar will get you the surface volume you're looking to create.  Surface volume requires a raster DEM, terrain, or TIN as an input.  Here's one way to do it with a TIN (at a high level) based on your XYZ input text file as your starting point: 1. ASCII 3D to Feature Class (3D Analyst toolbar or GP toolset) - this gets you a "3D aware" feature class http://resources.arcgis.com/en/help/main/10.1/index.html#/ASCII_3D_To_Feature_Class/00q900000041000000/ 2. Create TIN (3D Analyst toolbar or GP toolset) - using your "3D aware" feature class, this generates the TIN; otherwise, use the Terrain Wizard in ArcCatalog to achieve this step http://resources.arcgis.com/en/help/main/10.1/index.html#//00q90000001v000000 3. Surface Volume (3D Analyst toolbar or GP toolset) - calculates your surface volume from the input TIN in step 2 http://resources.arcgis.com/en/help/main/10.1/index.html#//00q900000027000000 ... View more

Yes, I saw this Stack Overflow post while doing some quick research before replying initially.  You could definitely be right about the root cause; I'd be curious to know the resolution once you're able to track it down in your environment.  In taking a bit different of an approach, do you have a firewall or antivirus program that could be blocking the requests on the client?  Try disabling all of those to see if the behavior changes, although I doubt it will given the 499 error.  This probably isn't the cause, but I thought it might be worth asking just in case. ... View more

After upgrading, did you re-authorize your ArcGIS for Server site with a 10.2 license?  As an example, if your 10.1 site had been authorized by a 10.1 Advanced license, then you would need to authorize your 10.2 site with a 10.2 Advanced license.  The services should re-appear after you re-authorize with the new license. ... View more

Here is the answer to your question: Services are not automatically migrated from version 10.0 to later versions. The migration path for these services is to re-create them using the newer version. Source: http://resources.arcgis.com/en/help/main/10.2/index.html#//0154000002p0000000 I'd recommend opening your 10.0 MXDs and performing a Save As to get them into a 10.2 MXD using a 10.2 ArcGIS Desktop client.  From there, you can re-publish them.  Make sure you register the data store(s) behind all of your MXDs with ArcGIS Server BEFORE publishing; otherwise server will attempt to make a copy of the data and ship it up to the server as local data. ... View more

The HTTP 499 responses result in cases where Nginx is used as the HTTP server and reverse proxy.  Typically, it means that the client closed the connection before the server answered the request.  After some brief online research, I've found that it can be caused by client side timeout.  Check your timeout settings for your Nginx configuration if you have access, or ask your system administrator to do so.  By default, the thin timeout is 30 seconds which means your server's response will be cut off at 30 seconds if nothing is returned.  This may simply not be enough for the token authentication.  Try increasing this value, but remember that a very large value could cause issues with the client timing out. ... View more

Which field(s) did you delete? What is the error you are receiving when attempting to view the feature class in ArcCatalog?  In other words, is the error still "general function failure" even when trying to preview it? From the Fields tab of the Properties window (since you still appear to be able to get to it), try re-adding the exact same field(s) you deleted with the exact same data type, character limit, precision, scale, etc. depending on the type of field(s) you deleted.  Before doing anything though, make a backup copy of what you have in case you happen to make the problems worse. ... View more