Latest Contributions by ChrisPedrezuela

Thanks for that. Its should be just as straight forward as you wrote there, but the thing about my sql query is that I have like more than 20 columns from that results. If i will create a table first in the GDB, how can I read the columns and column type of my result and use it in creating the fields dynamically? In the part where we loop through the results of the query, if I have 20 columns, I don't want to write "cursor.insertRow((result[0], result[1], .......result[19])". Thanks ... View more

Tried to right-click on the table but when I go to manage, all is greyed out. This sql database is actually managed by someone else and have tables that are being used in another business process. The table im trying to update will be an input for a reporting process using reporting tool. probably I should be asking our dba for some inputs as well. But since I can use insertcursor, should it be possible for me to use updatecursor to delete rows? or this is very inefficient? ... View more

Hi Vince, If its a sql server table, how do you register it with arcsde since they are non-spatial? Thanks ... View more

Yup sorry too Richard if I didn't fully considered your requirements. Luke has touched on it already. I highly recommend you switching to using arcpy.da (data access modules) that the Luke S mentioned to his reply to you. Its more flexible than how your using it for update cursor. Its pretty much what I used in my code I showed you. so if I update my code to consider your option for entering values or using values off a field, import arcpy import os def updateViaField(featureclass, updateProcess, fields, wc):     with arcpy.da.UpdateCursor(featureclass, fields, where_clause=wc) as cur:         for row in cur:             row[0] = row[1]             cur.updateRow(row) def updateViaValue(featureclass, updateProcess, fields, wc, updateValue):     with arcpy.da.UpdateCursor(featureclass, fields, where_clause=wc) as cur:         for row in cur:             row[0] = updateValue             cur.updateRow(row) if __name__ == '__main__':     '''Inputs'''     workspace = r'C:/DuluthGIS/SchemaUpdate/SDESchemaTest.gdb/Gas'     feature = 'gasDistributionMain'     featureclass = os.path.join(workspace, feature)     updateProcess = 'Field'     updateField = 'OPERATINGPRESURE'     wc = '"MAOP" >= 0'     updateValue = 123     '''Pass the condition'''     if updateProcess == 'Field':         valueField = 'MAOP'         fields = [updateField, valueField]         updateViaField(featureclass, updateProcess, fields, wc)     else:         fields = [updateField]         updateViaValue(featureclass, updateProcess, fields, wc, updateValue) ... View more

I think this is just what you want to do, import arcpy import os def updateField(feature, workspace):     with arcpy.da.UpdateCursor(os.path.join(workspace, feature), ['OPERATINGPRESSURE', 'MAOP'], where_clause='"MAOP" >= 0') as cur:         for row in cur:             row[0] = row[1]             cur.updateRow(row) if __name__ == '__main__':     workspace = r'C:/DuluthGIS/SchemaUpdate/SDESchemaTest.gdb/Gas'     feature = 'gasDistributionMain'     updateField(feature, workspace) ... View more

Thanks heaps for all the feedback guys. Since I don't want to create query layers in an mxd, I could just probably use arcpy.MakeQueryLayer_management and do something with the records while in_memory I guess. But I just want to validate if "GeometryCollection" type can be recognized? In my case this type is just composed of multiple polygon so pretty much like a "MultiPolygon". ... View more

Sorry for the lack of detail earlier, Here is the traceback report, Traceback (most recent call last):   File "Path\ExtractDataToCSV.py", line 37, in <module>     extract = in_connection.execute(sql)   File "C:\Program Files (x86)\ArcGIS\Desktop10.3\ArcPy\arcpy\arcobjects\arcobjects.py", line 27, in execute     return convertArcObjectToPythonObject(self._arc_object.Execute(*gp_fixargs(args))) AttributeError: ArcSDESQLExecute: SreamBindOutputColumn ArcSDE Error -65 \uda10 So this happens when I include the geometry column that has multiple geometry types. Without it, the table loads fine. I can load the geometry type but I have to do something like this, "cast(GeoLocation as varchar(8000)) as GeoLocation" This will load it as string but still I have to work a process to convert them as geometries. Wondering if there is a simpler or better way of reading sql tables like this. Thanks Dan ... View more

A colleague mentioned the GP service was giving off UTC date time format so I'll just create a function for converting UTC datetime input to local time. ... View more

Thanks Vince for all the feedback. Im not really that familiar with server architechture or that experienced in publishing geoprocessing services, so most of your server jargons are pretty new to me, sorry. We think the extracted records, which would probably range from 10 to 50k records per transaction do not need to be kept and could just stay in the scratchgdb till it gets cleaned up somewhere in the process. But due to the current environment setup, the database and table im connecting to and extracting those records from sometimes has another process or service running on it based on other jobs from different teams (non-GIS). So connecting and querying to it sometimes during a day would fluctuate from 5min to 15min alone. I could alternatively write the feature-converted records to an sde database so it'll persist. and separate the 2nd tool to fetch the data from there to run the analysis.  ... View more

Thanks a lot for the response Vince. I could easily merge my two tools to become one service if published. I figured that would remove my concern for re-using scratchworkspaces, which as you pointed out is not an ideal direction to take. However, the only concern I could probably have if my 2 tools act as one service is if the 2nd process (2nd tool) fails, then re-doing it needs to go through the first process. You see my first tool's function is to connect to a DB and extract records and write them as features in the scratchGDB, the second tool then does analysis on these features. So if they are a single service, if something fails on the second process, you'd have to re-extract records again. Looking forward to your thoughts on this. Regards, Thanos ... View more