Latest Contributions by VinceAngelo

Anything can get corrupted, especially when you replace an existing with a new one.  The mixed release levels probably isn't helping.  Have you tried using a 10.5 client? ... View more

It's important to keep in mind that enterprise geodatabases contain tables, not files, and that some of the usual practices which are casual about deletion and re-population in file-based storage mechanisms would be better off being redesigned to be less brutal on table elimination and creation in databases. For example, if the shapefile schema isn't changing with each release, using Truncate Table and Append would be less burdensome on the database, and would have the side effect of not needing an explicit delete or initializing the environment to permit target overwrite. - V ... View more

File geodatabase format itself hasn't changed in a long time, but geodatabase capabilities of ArcGIS have changed. So the answer is likely to be "Yes, it will work, if you're not using a 10.5-specific data structure." ... View more

Unfortunately, "folder" has multiple potential meanings. Are you referring to a feature dataset, which is symbolized as a folder in ArcGIS browser tools?  Note that this is a graphical representation of a specific set of relationships between data tables in a geodatabase, not a true container -- there are those that use FDS membership as a folder, but this can cause performance issues, and is not recommended.  The feature classes in a feature dataset are required to share a Spatial Reference, which makes it possible for them to participate in a topology. It's not possible for shapefiles to participate in a feature dataset. - V ... View more

This is expected behavior.  The objectid column is fed by an increasing value (the exact technique depends on the data source type).  You cannot change the objectid field, and really ought not use it for any purpose (except as a rowid column). - V ... View more

GROUP BY doesn't make much sense within the context of an UPDATE.  It's also not clear from your question whether this is a modern Data Access UpdateCursor or the deprecated kind, what version of ArcGIS is in use, and whether your data is file geodatabase, non-geodatabase (shapefile or other) or RDBMS. - V ... View more

Server has existed only as 64-bit for a long time (there are no supported ArcGIS Server builds which are not 64-bit). You can certainly invoke a 32-bit binary as you wish, but there really isn't any such thing as a "32-bit geoprocessing task" any more. - V ... View more

Yes, it's a pain that ArcGIS Server and Portal upgrades require you to press a button to continue the upgrade process (Portal further needs a Full Reindex), but it's not all that likely that a web browser isn't available to finish administration of a web-based application. If you have network connectivity issues due to a firewall on a VM or cloud node, and you're using a PuTTY session to install, you can use the tunneling capability of PuTTY to associate your client port 6443 with "localhost:6443" to circumvent the firewall. Alternatively, you could write some Java or Python code to access the "continue update" page and invoke the Web request associated with the button. If you want the code of someone who has done this, you should specify so in the question, with the preferred language, to reduce confusion. - V ... View more

Actually, your initial understanding is inaccurate (or at least incomplete). GEOGRAPHY stores LONGITUDE/LATITUDE data (X,Y order), and GEOMETRY stores geographic or projected coordinate system data (the exact coordinate system defined by the SRID assigned to the geometry). GEOGRAPHY has limits on extent (antipodal distance) that make GEOMETRY desirable even when the data is geographic (e.g., WGS 1984) As Asrujit indicated, the keyword availability doesn't indicate data in both formats is present (in fact, it could be present even if the keywords weren't), keywords are a metadata property of tables created by ArcGIS (but because Query Layers can exist that aren't registered, the table properties of GEOGRAPHY data might not indicate a GEOGRAPHY keyword), and finally, a GEOMETRY keyword isn't required to create a GEOMETRY-based table (it could be any other keyword, or it could have GEOGRAPHY which was altered to create GEOMETRY tables). Basically, you can't rely upon the keyword if you haven't been the one in charge of all table creations. - V ... View more

The data source of a query layer is a query against a database table (or set of tables) which returns one or more rows that have a rowid column and a geometry. Tables cannot have spaces in their names (nor can columns), so your table is not named "Latest LNAPL" -- This might be the layer name (Table of Contents identifier, which can contain spaces).  If you right-click to bring up the layer properties, then click on the "Source" tab, then press the "Change Query" button, you will see the full content of the SQL query (in the form "SELECT column_list FROM table_list [join_clauses] [WHERE where_clause]").  This is your source SQL. If the layer fails to validate because the table "Thisckness_1" is not present, then either: The table is not present or, You connected with a different login which can't see the original table (i.e., the table is not present) - V ... View more

The system requirements for 10.5.x don't mention Oracle 12.2 or 13.x. It's unlikely that Esri will announce a time when they will be supported. Contacting Tech Support to get on a list is your best recourse. - V ... View more

The system requirements for 10.3 do not mention Oracle 12.2, just 12.1. In fact, ArcGIS 10.5.1 doesn't mention Oracle 12.2 either. I wouldn't expect the latest builds of Oracle to operate with an old version of ArcGIS. - V ... View more

The first rule of publishing large/complex features: Don't do it. The second rule of publishing large/complex features (experts only): Don't do it, yet. Any time I have to publish a large/complex layer, I create a generalized layer to display at reasonable scales above it, and I process the data to display optimally at the scales where it is visible. In the case of contours, this would mean intersecting it with a fishnet polygon, so that individual features only exist in some reasonable distance from the viewfield (at least a 10x5 fishnet, but 20x10 is better), then sorting on the grid cell location (spatially defragmenting the layer) before the polygon ID is discarded. (For points, it would be intersecting by a fishnet, then unioning to make multipoint clusters for overview, and sorting for defragmentation.) Given a scale-dependent, split, defragmented dataset, if it still draws too slowly, your server is too old/under-powered for continued operation. - V ... View more