Latest Contributions by BruceHarold

Hello Alelentz Unfortunately the underlying engine for Data Interoperability 10 is not unicode aware; this is fixed in the next release.  You may want to try PostGIS dumper utility pgsql2shp and see if it correctly creates a codepage file (.cpg extension) and if so you can then import the shapefile into any geodatabase including unicode data. Regards ... View more

Hello Writing rasters is not supported with Landmark ZMAP format, this is true for the FME product too.  In fact no raster writers are supported by Data Interoperability; if you have a particular workflow in mind please describe it and we'll see how to accomplish it. Regards ... View more

Hi Mike Your workflow is of interest; we have a few samples using Python's subprocess and multiprocessing modules to parallelize geoprocessing tasks, but nothing so far using Lidar.  If you can share your data and processing requirements we may be able to figure out an approach for you.  If you can do this, please email me at bharold@esri.com. Regards ... View more

Hi Nathan Try AttributeFilter with the Import option to create separate output ports for each attribute value, set the ID value you want per port and connect all paths back together again. Regards ... View more

Charles, Joe Please see here: http://resources.arcgis.com/gallery/file/geocoding/details?entryID=1A290038-1422-2418-88FC-098400376B88 Regards ... View more

Hello Jason Yes, you can (for example) use the service's REST endpoint from within a Python script. Here is an example request from a tool I'm working on that batch geocodes recordset objects (what the GP service is expecting as an input parameter): response = urllib2.urlopen(serviceEndpoint + "/submitJob?&f=json","&Record_Set="+b).read() "b" is a RecordSet created earlier in the script. JSON responses are easy to handle with Python, here is how I catch my GP service result: response = urllib2.urlopen(u).read() fDict = json.loads(response)["value"]["features"] #Yields a dictionary of JSON encoded features "u" is a URL to each job result I loop through. The details of your sent and received objects will be specific to your GP service, but easily determined from the REST endpoint. Regards ... View more

ConCAVE hull Joe!  🙂 At some point we should make a system tool for this, the dental LIDAR community will be ecstatic (all one of them). Cheers ... View more

Hi Please also see this tool: http://resources.arcgis.com/gallery/file/geoprocessing/details?entryID=E51354B2-1422-2418-A0F6-8E4F8975BDAD The comment re. the tool getting some circles wrong appears to be a bug in the Buffer function, this is still being investigated. Regards ... View more

Hi Brad Can you supply sample data and/or a technical description of it? Regards ... View more

Hi Please try the attached style. Regards ... View more

Hi Please download this technical paper: http://resources.arcgis.com/gallery/file/geocoding/details?entryID=51EE55F8-1422-2418-7F8B-FD82DE958878 Regards ... View more

Sally Please try the Data Interoperability extension to read your GPX data.  You may obtain an evaluation license if you do not already have the extension. Regards ... View more

Hi Please try this tool: http://resources.arcgis.com/gallery/file/geoprocessing/details?entryID=E780BB87-1422-2418-7FD8-A1A0D8167AAF Regards ... View more

Hello Jun If you implement a process which maintains the copy of the address table in your GIS database (say by nightly update), and you have a locator in the same workspace as the table, then you can re-geocode automatically on update by using the option shown in the attached dialog (also available in the Geocode Addresses geoprocessing tool) to create a dynamic feature class related to the table. Regards ... View more

Hi Jun The input to the Geocode Addresses geoprocessing tool must be a table object, not a table view such as Make Query Table outputs.  Add a step to write the view into a workspace and geocode from that. Regards ... View more