Latest Contributions by HugoBouckaert

Hi    I have a python script that outputs to a feature layer.  The input is a CSV, but also could be something else. Using this on the desktop in ArcMap works. I then publish this as a geoprocessing service. However when I add the geoprocessing services as a geoprocessing widget in webappbuilder I get an error that I need to specify the feature layer output.   What I really want to do is to load a shapefile or a CSV and add that to the map. I had a look at https://github.com/magis-nc/esri-webappbuilder-widget-FileImporter but to create a geoprocessing service, here also I have three output layers (point, line and polygon). The GP service cannot be created in webappbuilder because the feature layer outputs cannot be defined in webappbuilder (in the tool the output must be set to feature layer). Do I have to connect the feature layer output to an existing layer in Portal perhaps?   Anyway  the short question is when the output of a geoprocessing service is a feature layer, how can this be made to work in webappbuilder with the layer added to a map.  A code example that I can use to get me started (i.e. something I can publish as a geoprocessing service) would be great of course.    Thanks   Hugo  ... View more

Hi I am uploading a File geodatabase using the new arcgis.gis API. Because my Portal is 10.4.1, I should be able to publish the contents of the file geodatabase as feature services. I can upload and publish a shape file, but with similar code, uploading a file geodatabase works, but publishing fails. Here is the code for the uploading the file geodatabase:  from arcgis.gis import * gis = GIS("http://<myportalserver>/arcgis","<username", "<password>") data = "C:\\temp\\fgdbtest.zip" # File geodatabase zipped up item_properties = {} item_properties ["type"] = "fileGeodatabase"  # I need the type definition, otherwise add did not work fgdbdata = gis.content.add(item_properties, data)# this works, the item is uploaded fgdbdata.publish() # ERROR: I get an error that Nonetype has no attribute publish(), so obviously fgdbdata is empty or None. Yet almost the same code does work when uploading a shape file. Does anyone have an example where a File geodatabase is uploaded as a new item and then the feature classes within published as feature services? Thanks Hugo ... View more

Hi I am trying to import a CSV file into annotation. As a start I tried to make up a CSV file to see if I could import it. I get all sorts of errors though. Is there an example out there somewhere of how to import a CSV file into feature linked annotation? Thanks Hugo ... View more

Hi I have a problem with accessing Data Interoperability (FME) workbenches version 10.0 from python (arcpy) using ArcGIS Desktop 10, service pack 1. The purpose is to run several FME translators as batch scripts without having to open ArcCatalog. It should be possible to import the ArcGIS toolbox in the arcpy environment and then run the workbenches in the toolbox. For example I have a toolbox named "SDE Loads.tbx" which contains several FME workbenches. To import in arcpy then would do the following: arcpy.ImportToolbox("D:/FME/SDE Loads.tbx") A toolbox has a name alias and each FME workbench in the toolbox also has an alias. The way that python is supposed to call an FME workbench (to execute the FME translation) is with the following format: FMEworkbenchAlias_ToolboxAlias(input parameters) However for me this rarely works as most times, the workbench aliases in the toolbox cannot be found. If other objects are created in the toolbox, such as models, they can always be found. This proves that both the toolbox as well as tools in the toolbox can be found by arcpy, with the exception of FME workbenches. Note that the way I check whether models, scripts or FME workbenches can be found in the toolbox is with the following code (necessary python indents may disappear when uploading this message): tools = arcpy.ListTools("*_ToolboxAlias") for tool in tools:      print tool      print arcpy.Usage(tool) Sometimes (and it is not known why) the workbench tools are listed in the ???print tool??? and print arcpy.Usage(tool) enumeration, but almost all cases, they are not listed at all, only other model tools in the toolbox. When FME workbenches are not listed, the workbenches cannot be executed as they cannot be found. There seems to be no discernable pattern when FME workbenches cannot be found using arcpy (in most cases), or can be found (rarely). Closing and reopening the toolbox, ArcCatalog or even the Windows login account on the computer where this is run from makes no difference. Note that in all cases, in arcpy, I am checking out the date interoperability license extension and include a message that I have successfully obtained the license extension. This is the code : try:   if arcpy.CheckExtension("DataInteroperability") == "Available":     arcpy.CheckOutExtension("DataInteroperability")     print "Checked out \"DataInteroperability\" Extension" else:   raise LicenseError   except LicenseError:   print "Data Interoperability license is unavailable" except:   print arcpy.GetMessages(2) Hence not having a license extension is not the cause of not finding the workbench aliases. It must be something else. Would someone be able to help? Thanks very much. Hugo ... View more

I have a problem with accessing Data Interoperability (FME) workbenches version 10.0 from python (arcpy) using ArcGIS Desktop 10, service pack 1.  The purpose is to run several FME translators as a batch script without having to open ArcCatalog, the toolbox, and in the toolbox, the Data Interoperability workbenches themselves. This is so the process of importing (and translating) data can be automated. The way that this works (from the documentation) is that you import the ArcGIS toolbox in your arcpy environment and then run the workbenches in the toolbox. For example I have a toolbox named "SDE Loads.tbx" which contains several FME workbenches. To import in arcpy I do the following:  arcpy.ImportToolbox("D:/FME/SDE Loads.tbx") A toolbox has a name alias (right click on toolbox, -> properties with the name to be found in the �??Name�?� properties box). Each FME workbench in the toolbox also has an alias (right click on FME workbench, -> properties with the name to be found in the �??Name�?� properties box). The way that python then is suposed to call the FME workbench (to execute the FME translation) is with the following format: FMEworkbenchAlias_ToolboxAlias(input parameters) However this rarely works as most times, the workbench aliases in the toolbox cannot be found. However note that if other objects in the toolbox are created, such as models, they can always be found. This proves that both the toolbox as well as tools in the toolbox can be found, with the exception of FME workbenches. Note that the way I check whether models, scripts or FME workbenches can be found in the toolbox is with the following code: tools = arcpy.ListTools("*_ToolboxAlias") for tool in tools:         print tool         print arcpy.Usage(tool) Sometimes (and it is not known why) the workbench tools are listed in the �??print tool�?� and print arcpy.Usage(tool) enumeration, but in most cases, they are not listed at all, only other model tools in the toolbox. When FME workbenches are not listed, the workbenches cannot be executed as they cannot be found. There seems to be no discernable pattern in when FME workbenches cannot be found using arcpy (in most cases), or can be found (sometimes). Closing and reopening the toolbox, ArcCatalog or even the Windows login account on the computer where this is run from makes no difference. Note that in all cases, in arcpy, I am checking out the date interoperability license extension and include a message that I have successfully obtained the license extension. This is the code : try:         if arcpy.CheckExtension("DataInteroperability") == "Available":             arcpy.CheckOutExtension("DataInteroperability")             print "Checked out \"DataInteroperability\" Extension"         else:             raise LicenseError     except LicenseError:         print "Data Interoperability license is unavailable"     except:         print arcpy.GetMessages(2)  Hence not having a license extension is not the cause of not finding the workbench aliases. It must be something else. Would someone be able to help? Thanks very much. Hugo ... View more