|
POST
|
What transaction are you committing? CREATE TABLE is not logged, nor is ALTER TABLE. Both must occur outside a transaction. It seems you are using the transaction environment incorrectly. Please add the relevant pieces of your script to the question, so we have a chance to figure out what is wrong. - V
... View more
06-22-2018
06:28 AM
|
0
|
0
|
1247
|
|
POST
|
Shapefiles are only marginally part of the geodatabase model, mostly because they don't conform to the full range of datatypes and NULL support (not to mention the field naming limitations and byte-sized length limit). Geodatabase, the model, doesn't have limits. File geodatabase, the format, doesn't have limits*. Enterprise geodatabase, the format, only has what limits are imposed by the RDBMS vendor. Admittedly, juggling between these formats can be a PITA, but that's not a limitation of geodatabase. I'm also mystified by the resurrection. - V * Where 2Gb-1 is "effectively unlimited"
... View more
06-17-2018
04:45 PM
|
0
|
1
|
702
|
|
POST
|
No, there is no such limit. As stated, repeatedly, "geodatabase" text fields are unlimited (2^31-1 UTF-16), though the underlying storage format may assert a lower value. - V
... View more
06-17-2018
02:13 PM
|
0
|
3
|
5659
|
|
POST
|
Underscore should be okay, but ALLCAPS and MixedCase are BAD (with or without underscore). - V
... View more
06-04-2018
10:08 AM
|
2
|
1
|
6827
|
|
POST
|
Please remember to specify the exact versions of PostgreSQL and ArcGIS in use. It's been a decade since client libraries were necessary with PostgreSQL, so it's possible that you've corrupted the install, causing the library failure. You should also provide verification that psql on the same host can connect to the same server. - V
... View more
06-01-2018
09:29 AM
|
1
|
0
|
976
|
|
POST
|
This is why lists are not considered best-practice in database design. If you had a second table organized: keycol attrval 1 A1 1 F4 1 A10 2 A1 2 A17 3 F1 3 G6 3 A1 4 A10 4 A1 then you could fashion a query: SELECT * FROM mytable WHERE keycol in ( SELECT keycol FROM secondtab WHERE attrval = 'A1') - V
... View more
05-31-2018
07:00 AM
|
1
|
1
|
3221
|
|
POST
|
You haven't provided enough useful information. What is the name of your user? What is the name of the version? From which version was the new version created. What exact parameter did you change on the connection UI? - V
... View more
05-30-2018
08:51 AM
|
0
|
6
|
3434
|
|
POST
|
Be sure you read up on how Esri's versioning model operates. There is no difference between the child and parent versions if no editing has occurred. The active version is a connnection property. - V
... View more
05-29-2018
11:11 AM
|
1
|
8
|
3434
|
|
POST
|
Uninstall/reinstall couldn't hurt, but I expect the problem is with the data, not the software. - V
... View more
05-23-2018
01:35 PM
|
0
|
0
|
20380
|
|
POST
|
This question is not a logical extension of the post from seven years ago. You should have posted a new question, which would have to include the database which enforces a 320 character limit (I'm not aware of any that do). Shapefiles have a much smaller limit: 254 bytes (fewer UTF-8 codepoints). There are a number of answered questions here which address string field width in various storage formats. - V
... View more
05-23-2018
11:24 AM
|
0
|
0
|
5659
|
|
POST
|
The polygon can still be invalid in other ways (e.g., self-intersection). - V
... View more
05-23-2018
11:15 AM
|
0
|
0
|
4674
|
|
POST
|
If your polygons have invalid ring geometry, Clip may produce bizarre results. Try verifying both your Input and Clip layers with CheckGeometry_management - V
... View more
05-21-2018
06:10 PM
|
1
|
2
|
4674
|
|
POST
|
This is a response to really ancient post. ArcGIS Server has been 64-bit for so long that the last 32-bit incarnation has been retired from support for two and a half years. All of your products are ancient, and fairly dangerous to operate, since the volume of known security flaws is significant. I can't in good faith make any recommendations to utilize such flawed configurations.
... View more
05-09-2018
08:14 AM
|
3
|
0
|
2069
|
|
POST
|
arcpy DA cursors require that the column list be explicit (or a wildcard, which matches all columns in the order of the table, but it's best practice to always explicitly define your columns), and that the values in the array passed into updateRow must be in the order specified in the cursor declaration. Your code does not do this. It passes in a dictionary, which is forbidden, and generates the error. In order to get your code working, you'll need to populate an array: for row in reader:
rowArray = []
for name in ["Name", "OrderCount","Time","Miles"]:
rowArray.append(row[name])
updateCursor.updateRow(rowArray) Be careful, the names might not match by case. The logic still requires that the rows in the shapefile exactly match the CSV. The safe best is to store the small CSV in a dictionary keyed by ID, add the ID column to the name list (if not keyed by name), and use the shapefile's ID to populate extract the appropriate row. - V
... View more
05-02-2018
02:47 PM
|
1
|
0
|
3150
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Tuesday | |
| 2 | 4 weeks ago | |
| 1 | 05-29-2026 12:51 PM | |
| 1 | 06-01-2026 06:03 PM | |
| 2 | 05-29-2026 08:31 AM |