|
POST
|
Even when I had the ability, I did not use sdetable to create views -- I used SQL scripts in the database exclusively. Where necessary, I would sdelayer -o register layers, but with Query Layers, I find it's not necessary. - V
... View more
03-15-2018
01:17 PM
|
0
|
0
|
2394
|
|
POST
|
A spatial view is a database object. It is not registered with the geodatabase in any way. Therefore, when you access it via a Query Layer, ArcGIS needs to ask for the rowid column and geometry type (this lack of meta-information is the defining characteristic of a Query Layer). The ability to register views to a geodatabase was added at ArcGIS 10.5, so if you're running 10.4.1 or lower, Query Layers is your only mechanism to access views. - V
... View more
03-15-2018
11:45 AM
|
1
|
2
|
2394
|
|
POST
|
Note that this is a cross-post of three additional questions on GIS StackExchange, all of which were closed for lack of code. The best way to get help with code is to provide code. - V
... View more
03-14-2018
09:08 AM
|
1
|
2
|
3854
|
|
POST
|
ArcGIS has never had an "unregister" option for geodatabase objects. There was sdelayer -o delete in the ArcSDE command-line tools, but that has ALWAYS corrupted geodatabase metadata, and inappropriate use like this was one of the reasons the entire command-line toolset was deprecated. The only supported way to "unregister" a view is to delete it from Desktop/Pro/arcpy, after which you can recreate with SQL and re-register (if you must). ALTERing a view could corrupt geodatabase metadata; once registered, you really should not alter a view or table via SQL. - V
... View more
03-09-2018
08:43 AM
|
6
|
1
|
6015
|
|
POST
|
Actually, I never install application software on C: -- Only Microsoft apps are allowed on my C: drive, which I limit to 100-200Gb. My Esri installs are always in a D:\Esri folder (directories with spaces in them make me break out in hives). That said, I only install application software and data on internal disks. External disks are for archiving and transfer, not for GIS data or software.
... View more
03-09-2018
06:56 AM
|
5
|
0
|
4309
|
|
POST
|
If you're just starting with Python, there's really no reason to use anything but the correct indentation scheme -- 4 spaces. Making your code legible is just as important as including the complete error messages, or adding diagnostic arcpy.AddMessage() lines just inside each for loop to trace execution flow. - V
... View more
03-08-2018
08:10 AM
|
1
|
0
|
3110
|
|
POST
|
Not only does it need to be the correct ArcGIS release, but it also needs to be for the correct operating system AND PostgreSQL release, AND in the correct location (which varies by build source) so make sure it's the right file in the right place. For good or for bad, the database is always right when it comes to library compatibility (the Direct Connect client just asks the PG instance if the library is present) - V
... View more
03-06-2018
01:36 PM
|
3
|
1
|
4863
|
|
POST
|
Did you upgrade the Image Server license? Are there any messages in the logs? - V
... View more
02-27-2018
06:11 PM
|
0
|
0
|
1335
|
|
POST
|
Normal views can be accessed as Query Layers; stored procedures cannot. Packets being what they are, I doubt you'd see a measurable difference in network traffic, even if the query only returns one row. - V
... View more
02-26-2018
01:58 PM
|
2
|
0
|
5428
|
|
POST
|
Is there a reason you linked to the documentation of a retired release of ArcGIS? Current documentation also references arcpy.ArcSDESQLExecute, which remains the only within-ArcPy method to execute ad-hoc SQL. Note that this function could be used to corrupt geodatabase metadata (with an injudicious DROP TABLE, for example), so extreme care should be used. That said, I just executed a cascade of 1200+ SQL statements against a PostgreSQL database (thanks to Python dictionaries, string substitution, and nested looping), so the only reason to fall back to ODBC is if your return results are not supported by the API (the most dangerous being long (64-bit) integers and geometry columns). - V
... View more
02-21-2018
08:46 AM
|
2
|
0
|
5428
|
|
POST
|
No, there is no way I can help you. Providing one function call is of little use, since it's unlikely the problem is with that one call -- it's just where some other error can manifest itself. You really ought to assemble a full code sample which reproduces the issue (StackExchange calls it an MCVE), and turn that over to Tech Support, along with complete details about the configuration of the VM and non-VM hosts. You can post the MCVE here, but given the reproducibility issues, there may be challenges ahead. - V
... View more
02-20-2018
06:45 AM
|
0
|
1
|
1078
|
|
POST
|
We'll need more information than a link to archaic documentation. Of critical interest: The RDBMS and version of the source database The RDBMS and version of the target database The geodatabase version of the target database There are no tools to use pure Python to populate SDEBINARY geometry without ArcPy. Attempting to do so will cost far more than a seat of Desktop (and if the database is already SDEBINARY, then the software already exists). - V
... View more
02-18-2018
06:15 PM
|
2
|
0
|
2181
|
|
POST
|
Shapefile is an awful format for database-to-database conversion. Recommend file geodatabase instead, since FGDB won't lose date resolution, numeric nulls, wide tables, UTF-16 strings, wide strings, legible field names,....
... View more
02-18-2018
06:06 PM
|
2
|
0
|
2181
|
|
POST
|
Also asked at GIS Stack Exchange. The organizational preference part is still true. Some sites prefer to upgrade to .1 releases, and skip from 10.4.1 to 10.5.1 to 10.6.1. It really does depend on when you decide to upgrade, and what is available, and what local site testing indicates about the stability of your applications with the candidate version for upgrade. Clients are usually upgraded before Server installs, so larger sites often take a while rolling out an upgrade across their enterprise. Smaller sites have less inertia in the older release. - V
... View more
02-04-2018
07:53 PM
|
1
|
0
|
1421
|
|
POST
|
If you look in the Geoprocessing results log, the Python command for publishing will be present. You can issue that command (or its moral equivalent) using arcpy on an ArcGIS Server host (Windows or Linux). If an SOE is involved, the publishing process is more convoluted (using urllib2 to interact with the admin REST service), but a simple GP tool should be fairly straight-forward. - V
... View more
01-31-2018
08:00 AM
|
1
|
0
|
1464
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a week ago | |
| 2 | a month ago | |
| 1 | 05-29-2026 12:51 PM | |
| 1 | 06-01-2026 06:03 PM | |
| 2 | 05-29-2026 08:31 AM |