![]() While this might be contrived (no argument there) the contrivance is in production data and needs to be cleaned out. Or (X,None) I haven’t come across any like that but we’re still working on tracking down how this got in there in the first place. Hence the check for X=0 and Y=0 and if I’m doing that and finding those cases, I figurred might as well verify we don’t have some odd stuff with (None,Y) ![]() I believe they have possibly been there for years. How those values got into the data, I have no idea. I've concluded that using the SHAPE part of a geodatabase in a da.Cursor query string is just not possible.Īctually Dan, the issue here is we have some squirrely Shape:Point data.įor the Nulls, I can “probably” just check the X value, but given what I’ve seen with the 0 data…įor 0, I’ve come across data of the format (0, yyyyyyyy) and (xxxxxxxxx,0) QueryString = NULL or = 0 or = NULL or = 0' I thought it would be cleaner to have a query string in the UpdateCursor but so far I've had no luck with If row = None or row = 0.0 or row = None or row = 0.0 : ![]() With arcpy.da.UpdateCursor(myFC, fields) as cursor : We have some data with NULLS in the ShapePoint data and I'm flipping them all to 0,0 in our state plane projection by: Now that it's 2015, I'm wondering if that's still correct. I saw a posting from 2012 that answered the question if or or could be used in forming the where_clause in an arcpy.da.XCursor (search, update or insert)
0 Comments
Leave a Reply. |