Update records with ArcPy update cursor? Geodatabase format
I try to update thousands of rows when all records get the same value.
My code has a loop that runs thousands of times.
Is it possible for the program to make the change to all the columns in one command and save run time ?
For example, php+mySQL can do this:
mysql_query("UPDATE all_records SET Xcenter = $val1, Ycenter = $val2 WHERE ID > 100");
This is my code:
for row in rows:
row.setValue("Xcenter", val1)
row.setValue("Ycenter", val2)
rows.updateRow(row)
arcpy arcmap
New contributor
add a comment |
I try to update thousands of rows when all records get the same value.
My code has a loop that runs thousands of times.
Is it possible for the program to make the change to all the columns in one command and save run time ?
For example, php+mySQL can do this:
mysql_query("UPDATE all_records SET Xcenter = $val1, Ycenter = $val2 WHERE ID > 100");
This is my code:
for row in rows:
row.setValue("Xcenter", val1)
row.setValue("Ycenter", val2)
rows.updateRow(row)
arcpy arcmap
New contributor
Please Edit the question to specify the data storage format of the target (file geodatabase, RDBMS, shapefile,...) and provide a sample of your existing code.
– Vince
2 hours ago
1
By thousands of fields, you actually mean thousands of rows/records?
– BERA
2 hours ago
1
Please add more code, since that fragment is missing cursor creation. Note that there are no versions of ArcGIS which aren't retired for which non-DataAccess cursors are appropriate. setRow is not supported on DataAcess cursor rows, and DataAcess cursors are much faster than the old, deprecated cursors. You also have indent issues.
– Vince
2 hours ago
exactly. I mean thousands of records. I updated. Thanks
– Oz1988
2 hours ago
What's wrong with a for loop? In essence, it's exactly what's going one behind the scenes of any other method, except, with a da cursor, it should be more efficient than using an unnecessary intermediary like CalculateField.
– Tom
1 hour ago
add a comment |
I try to update thousands of rows when all records get the same value.
My code has a loop that runs thousands of times.
Is it possible for the program to make the change to all the columns in one command and save run time ?
For example, php+mySQL can do this:
mysql_query("UPDATE all_records SET Xcenter = $val1, Ycenter = $val2 WHERE ID > 100");
This is my code:
for row in rows:
row.setValue("Xcenter", val1)
row.setValue("Ycenter", val2)
rows.updateRow(row)
arcpy arcmap
New contributor
I try to update thousands of rows when all records get the same value.
My code has a loop that runs thousands of times.
Is it possible for the program to make the change to all the columns in one command and save run time ?
For example, php+mySQL can do this:
mysql_query("UPDATE all_records SET Xcenter = $val1, Ycenter = $val2 WHERE ID > 100");
This is my code:
for row in rows:
row.setValue("Xcenter", val1)
row.setValue("Ycenter", val2)
rows.updateRow(row)
arcpy arcmap
arcpy arcmap
New contributor
New contributor
edited 2 hours ago
BERA
14.8k52041
14.8k52041
New contributor
asked 2 hours ago
Oz1988Oz1988
112
112
New contributor
New contributor
Please Edit the question to specify the data storage format of the target (file geodatabase, RDBMS, shapefile,...) and provide a sample of your existing code.
– Vince
2 hours ago
1
By thousands of fields, you actually mean thousands of rows/records?
– BERA
2 hours ago
1
Please add more code, since that fragment is missing cursor creation. Note that there are no versions of ArcGIS which aren't retired for which non-DataAccess cursors are appropriate. setRow is not supported on DataAcess cursor rows, and DataAcess cursors are much faster than the old, deprecated cursors. You also have indent issues.
– Vince
2 hours ago
exactly. I mean thousands of records. I updated. Thanks
– Oz1988
2 hours ago
What's wrong with a for loop? In essence, it's exactly what's going one behind the scenes of any other method, except, with a da cursor, it should be more efficient than using an unnecessary intermediary like CalculateField.
– Tom
1 hour ago
add a comment |
Please Edit the question to specify the data storage format of the target (file geodatabase, RDBMS, shapefile,...) and provide a sample of your existing code.
– Vince
2 hours ago
1
By thousands of fields, you actually mean thousands of rows/records?
– BERA
2 hours ago
1
Please add more code, since that fragment is missing cursor creation. Note that there are no versions of ArcGIS which aren't retired for which non-DataAccess cursors are appropriate. setRow is not supported on DataAcess cursor rows, and DataAcess cursors are much faster than the old, deprecated cursors. You also have indent issues.
– Vince
2 hours ago
exactly. I mean thousands of records. I updated. Thanks
– Oz1988
2 hours ago
What's wrong with a for loop? In essence, it's exactly what's going one behind the scenes of any other method, except, with a da cursor, it should be more efficient than using an unnecessary intermediary like CalculateField.
– Tom
1 hour ago
Please Edit the question to specify the data storage format of the target (file geodatabase, RDBMS, shapefile,...) and provide a sample of your existing code.
– Vince
2 hours ago
Please Edit the question to specify the data storage format of the target (file geodatabase, RDBMS, shapefile,...) and provide a sample of your existing code.
– Vince
2 hours ago
1
1
By thousands of fields, you actually mean thousands of rows/records?
– BERA
2 hours ago
By thousands of fields, you actually mean thousands of rows/records?
– BERA
2 hours ago
1
1
Please add more code, since that fragment is missing cursor creation. Note that there are no versions of ArcGIS which aren't retired for which non-DataAccess cursors are appropriate. setRow is not supported on DataAcess cursor rows, and DataAcess cursors are much faster than the old, deprecated cursors. You also have indent issues.
– Vince
2 hours ago
Please add more code, since that fragment is missing cursor creation. Note that there are no versions of ArcGIS which aren't retired for which non-DataAccess cursors are appropriate. setRow is not supported on DataAcess cursor rows, and DataAcess cursors are much faster than the old, deprecated cursors. You also have indent issues.
– Vince
2 hours ago
exactly. I mean thousands of records. I updated. Thanks
– Oz1988
2 hours ago
exactly. I mean thousands of records. I updated. Thanks
– Oz1988
2 hours ago
What's wrong with a for loop? In essence, it's exactly what's going one behind the scenes of any other method, except, with a da cursor, it should be more efficient than using an unnecessary intermediary like CalculateField.
– Tom
1 hour ago
What's wrong with a for loop? In essence, it's exactly what's going one behind the scenes of any other method, except, with a da cursor, it should be more efficient than using an unnecessary intermediary like CalculateField.
– Tom
1 hour ago
add a comment |
2 Answers
2
active
oldest
votes
Try the da.UpdateCursor:
import arcpy
feature_class = r'C:data.gdbfeatures1'
val1 = 123
val2 = 456
sql = """{0} > 100""".format(arcpy.AddFieldDelimiters(feature_class, 'ID'))
fields_to_update = ['Xcenter','Ycenter']
with arcpy.da.UpdateCursor(feature_class, fields_to_update, sql) as cursor:
for row in cursor:
row = val1, val2
cursor.updateRow(row)
First of all thank you Also in your program there is a loop that runs thousands of times (as many records) I'm looking for something to do it at once. The values I put are identical to all records so I do not want to run thousands of times in a loop
– Oz1988
2 hours ago
1
@Oz1988: The data access cursors (da.UpdateCursor etc.) are very fast so thousands of rows should not be a problem, it should finish in a few seconds. This is what they are designed to do. I know no other way.
– BERA
2 hours ago
1
@Oz1988 If you had a large number of rows (tens to hundreds of millions), it would actually be much faster to set multiple values per row than to use the Field Calculator one column at a time. Your stated goal and intended methodology are incongruous.
– Vince
2 hours ago
add a comment |
I have a weird feeling that you are looking for arcpy.CalculateField_management
It is simple and quick calculate field help
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "79"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Oz1988 is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f307790%2fupdate-records-with-arcpy-update-cursor-geodatabase-format%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Try the da.UpdateCursor:
import arcpy
feature_class = r'C:data.gdbfeatures1'
val1 = 123
val2 = 456
sql = """{0} > 100""".format(arcpy.AddFieldDelimiters(feature_class, 'ID'))
fields_to_update = ['Xcenter','Ycenter']
with arcpy.da.UpdateCursor(feature_class, fields_to_update, sql) as cursor:
for row in cursor:
row = val1, val2
cursor.updateRow(row)
First of all thank you Also in your program there is a loop that runs thousands of times (as many records) I'm looking for something to do it at once. The values I put are identical to all records so I do not want to run thousands of times in a loop
– Oz1988
2 hours ago
1
@Oz1988: The data access cursors (da.UpdateCursor etc.) are very fast so thousands of rows should not be a problem, it should finish in a few seconds. This is what they are designed to do. I know no other way.
– BERA
2 hours ago
1
@Oz1988 If you had a large number of rows (tens to hundreds of millions), it would actually be much faster to set multiple values per row than to use the Field Calculator one column at a time. Your stated goal and intended methodology are incongruous.
– Vince
2 hours ago
add a comment |
Try the da.UpdateCursor:
import arcpy
feature_class = r'C:data.gdbfeatures1'
val1 = 123
val2 = 456
sql = """{0} > 100""".format(arcpy.AddFieldDelimiters(feature_class, 'ID'))
fields_to_update = ['Xcenter','Ycenter']
with arcpy.da.UpdateCursor(feature_class, fields_to_update, sql) as cursor:
for row in cursor:
row = val1, val2
cursor.updateRow(row)
First of all thank you Also in your program there is a loop that runs thousands of times (as many records) I'm looking for something to do it at once. The values I put are identical to all records so I do not want to run thousands of times in a loop
– Oz1988
2 hours ago
1
@Oz1988: The data access cursors (da.UpdateCursor etc.) are very fast so thousands of rows should not be a problem, it should finish in a few seconds. This is what they are designed to do. I know no other way.
– BERA
2 hours ago
1
@Oz1988 If you had a large number of rows (tens to hundreds of millions), it would actually be much faster to set multiple values per row than to use the Field Calculator one column at a time. Your stated goal and intended methodology are incongruous.
– Vince
2 hours ago
add a comment |
Try the da.UpdateCursor:
import arcpy
feature_class = r'C:data.gdbfeatures1'
val1 = 123
val2 = 456
sql = """{0} > 100""".format(arcpy.AddFieldDelimiters(feature_class, 'ID'))
fields_to_update = ['Xcenter','Ycenter']
with arcpy.da.UpdateCursor(feature_class, fields_to_update, sql) as cursor:
for row in cursor:
row = val1, val2
cursor.updateRow(row)
Try the da.UpdateCursor:
import arcpy
feature_class = r'C:data.gdbfeatures1'
val1 = 123
val2 = 456
sql = """{0} > 100""".format(arcpy.AddFieldDelimiters(feature_class, 'ID'))
fields_to_update = ['Xcenter','Ycenter']
with arcpy.da.UpdateCursor(feature_class, fields_to_update, sql) as cursor:
for row in cursor:
row = val1, val2
cursor.updateRow(row)
edited 2 hours ago
answered 2 hours ago
BERABERA
14.8k52041
14.8k52041
First of all thank you Also in your program there is a loop that runs thousands of times (as many records) I'm looking for something to do it at once. The values I put are identical to all records so I do not want to run thousands of times in a loop
– Oz1988
2 hours ago
1
@Oz1988: The data access cursors (da.UpdateCursor etc.) are very fast so thousands of rows should not be a problem, it should finish in a few seconds. This is what they are designed to do. I know no other way.
– BERA
2 hours ago
1
@Oz1988 If you had a large number of rows (tens to hundreds of millions), it would actually be much faster to set multiple values per row than to use the Field Calculator one column at a time. Your stated goal and intended methodology are incongruous.
– Vince
2 hours ago
add a comment |
First of all thank you Also in your program there is a loop that runs thousands of times (as many records) I'm looking for something to do it at once. The values I put are identical to all records so I do not want to run thousands of times in a loop
– Oz1988
2 hours ago
1
@Oz1988: The data access cursors (da.UpdateCursor etc.) are very fast so thousands of rows should not be a problem, it should finish in a few seconds. This is what they are designed to do. I know no other way.
– BERA
2 hours ago
1
@Oz1988 If you had a large number of rows (tens to hundreds of millions), it would actually be much faster to set multiple values per row than to use the Field Calculator one column at a time. Your stated goal and intended methodology are incongruous.
– Vince
2 hours ago
First of all thank you Also in your program there is a loop that runs thousands of times (as many records) I'm looking for something to do it at once. The values I put are identical to all records so I do not want to run thousands of times in a loop
– Oz1988
2 hours ago
First of all thank you Also in your program there is a loop that runs thousands of times (as many records) I'm looking for something to do it at once. The values I put are identical to all records so I do not want to run thousands of times in a loop
– Oz1988
2 hours ago
1
1
@Oz1988: The data access cursors (da.UpdateCursor etc.) are very fast so thousands of rows should not be a problem, it should finish in a few seconds. This is what they are designed to do. I know no other way.
– BERA
2 hours ago
@Oz1988: The data access cursors (da.UpdateCursor etc.) are very fast so thousands of rows should not be a problem, it should finish in a few seconds. This is what they are designed to do. I know no other way.
– BERA
2 hours ago
1
1
@Oz1988 If you had a large number of rows (tens to hundreds of millions), it would actually be much faster to set multiple values per row than to use the Field Calculator one column at a time. Your stated goal and intended methodology are incongruous.
– Vince
2 hours ago
@Oz1988 If you had a large number of rows (tens to hundreds of millions), it would actually be much faster to set multiple values per row than to use the Field Calculator one column at a time. Your stated goal and intended methodology are incongruous.
– Vince
2 hours ago
add a comment |
I have a weird feeling that you are looking for arcpy.CalculateField_management
It is simple and quick calculate field help
add a comment |
I have a weird feeling that you are looking for arcpy.CalculateField_management
It is simple and quick calculate field help
add a comment |
I have a weird feeling that you are looking for arcpy.CalculateField_management
It is simple and quick calculate field help
I have a weird feeling that you are looking for arcpy.CalculateField_management
It is simple and quick calculate field help
answered 2 hours ago
ChrisLChrisL
354312
354312
add a comment |
add a comment |
Oz1988 is a new contributor. Be nice, and check out our Code of Conduct.
Oz1988 is a new contributor. Be nice, and check out our Code of Conduct.
Oz1988 is a new contributor. Be nice, and check out our Code of Conduct.
Oz1988 is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Geographic Information Systems Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f307790%2fupdate-records-with-arcpy-update-cursor-geodatabase-format%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Please Edit the question to specify the data storage format of the target (file geodatabase, RDBMS, shapefile,...) and provide a sample of your existing code.
– Vince
2 hours ago
1
By thousands of fields, you actually mean thousands of rows/records?
– BERA
2 hours ago
1
Please add more code, since that fragment is missing cursor creation. Note that there are no versions of ArcGIS which aren't retired for which non-DataAccess cursors are appropriate. setRow is not supported on DataAcess cursor rows, and DataAcess cursors are much faster than the old, deprecated cursors. You also have indent issues.
– Vince
2 hours ago
exactly. I mean thousands of records. I updated. Thanks
– Oz1988
2 hours ago
What's wrong with a for loop? In essence, it's exactly what's going one behind the scenes of any other method, except, with a da cursor, it should be more efficient than using an unnecessary intermediary like CalculateField.
– Tom
1 hour ago