Latest Contributions by BruceHarold

Matthew, we'll look into truncate performance, it should be using a delete with where clause OBJECTID > 0. ... View more

Data Interoperability extension will write XLSX. Of course it has a cost. ... View more

Hi, please log a support call.  If its Esri code we'll know, or work with Safe if not. Regards ... View more

Hi There is a route through from HTML popup information in KML via XHTML to normal attributes using the Data Interoperability extension, but you'll have to know (or decide) the field typing for each element.  If you can share a sample file I can provide a 10.4 tool, but you'll need Data Interoperability to use it.  If you have control over the KML source it is much better to generate KML with a schema object in it, which will retain data typing, but again you'll need Data Interoperability to work that way. ... View more

Try this: http://www.arcgis.com/home/item.html?id=904786f5db4e4a75afbb2790c7f90d35 ... View more

Hi Creating SDC datasets requires a special compiler which Esri does not ship.  The Data Interoperability extension doesn't handle SDC either.  Dan's advice is good, consider moving to File Geodatabase as your data publishing format; you can compress or license File Geodatabases to control your deliverable.  Please see the File Geodatabase toolset under Data Management. ... View more

There is a lot of confusion around this setting; there is no limit to how many features you can publish to a hosted feature layer in ArcGIS Online, although it may be time consuming publishing from ArcMap over a slow connection, or even fail.  The setting for maximum number of records returned by the server is to do with how many features can be returned at a time for each Query call to the service.  You can see the effect of this when viewing your service in the arcgis.com web map viewer, you get this many features in the map at a time.  In ArcMap or ArcGIS Pro the entire feature layer may be queried, but the setting controls how many features page into the application at a time.  The workflow I have adopted for publishing very large feature layers (millions) is to upload a zipped File Geodatabase as an ArcGIS Online item and publish it manually from My Content, or with this tool if I want to control target spatial reference and maximum record count etc: http://www.arcgis.com/home/item.html?id=ea977181060b431cb46e1b4712078365 Back in Desktop to view the data you need to create the scale threshold and cartographic properties you need for the layer as this workflow doesn't handle pushing that up from a map. ... View more

Please also see this tool: http://www.arcgis.com/home/item.html?id=da1540fb59d84b7cb02627856f65a98d Regards ... View more

Hi In addition to Woody's heads up, you can create a Single Field locator for your data now, but your parcel ID field will need to be string (or copied to a field that is string); you could return the actual integer value as the Additional Field parameter.  Use the Create Address Locator geoprocessing tool and the Single Field locator style. ... View more

I just tried a composite with a field having the full address details (i.e single line) in a field I mapped to the ADDRESS input of a multiline run, and the other zone fields mapped normally, and I got the 000010 error, so its probably just data-dependent luck it works for you. Messages Executing: GeocodeAddresses D:\Work\Product_Management\LINZAddressing\lds-new-zealand-17layers-FGDB\StreetAddress.gdb\HalfMoonBay D:\Work\Product_Management\LINZAddressing\TestComposite "Address SingleLine VISIBLE NONE;Neighborhood <None> VISIBLE NONE;City SUBURB VISIBLE NONE;Subregion <None> VISIBLE NONE;Region MAILTOWN VISIBLE NONE;Postal POSTCODE VISIBLE NONE;PostalExt <None> VISIBLE NONE;CountryCode <None> VISIBLE NONE" D:\Work\Product_Management\LINZAddressing\lds-new-zealand-17layers-FGDB\StreetAddress.gdb\Geocode_Result STATIC Start Time: Mon Feb 01 08:37:02 2016 Executing Geocode Addresses... ERROR 000010: Geocode addresses failed. Failed to execute (GeocodeAddresses). Failed at Mon Feb 01 08:37:07 2016 (Elapsed Time: 5.32 seconds) ... View more

Tiffany, you cannot mix single and multi line handling in a composite locator. ... View more

Tiffany I may have put you wrong earlier, I just did a single line input process and the input fields are stated like this: in_address_fields="'Single Line Input' SingleLine VISIBLE NONE" i.e. there should not be any more fields than just one, and the parameter is 'Single Line Input'. Regards ... View more

Sorry, another thing: the single like parameter is 'SingleLine', e.g.: Executing: GeocodeAddresses HalfMoonBay "GIS Servers\arcgis on geocode.arcgis.com (user)\World.GeocodeServer" "SingleLine SingleLine VISIBLE NONE" C:\Users\bruc5588\Documents\ArcGIS\Projects\GeocodingDemo.gdb\Tiffany STATIC ... View more