Latest Contributions by BruceHarold

Hi Slobodan The Geocode Addresses geoprocessing tool is the core tool for this, using the World service.  Most likely you were not signed in to ArcGIS Online when you tried this or you do not have geocode privilege in your organization or you have insufficient credits.  Check with your org admin. ... View more

I replaced the download with external source. ... View more

You can see the code, just right click on the tool in the toolbox and edit. The code is embedded, not passworded. ... View more

Hi, see if this sample works for you - it is a bit old now, but should function: ... View more

Sarah in the meantime you can use this sample for any datum adjustment work.  Until we ship NZVD2016 you still cannot write vertical datum metadata for a feature class, but the sample will let you get the coordinates right. ... View more

Well that covers off the problem being different vertical datums. I asked around, this problem is called Z-fighting - some DEM points are higher than the construction features. Someone suggested adding a zero-elevation (or lower anyway) source with shape taken from the roadway footprint.  One option is to make a TIN from your construction elements.  There may be interference artifacts at the base of the walls.  If it looks bad go with burning the flat area into your DEM. ... View more

Try the value ‘CreationDate’ for the variable dateField. ... View more

Hamish, taking a wild guess you are working on SH 1 a little north of Kaikoura, on the coast (i.e. sea level matters). If your data has ellipsoidal heights (like from GPS) and you are using the default World DTM elevation surface, which is orthometric, then you should apply a cartographic offset equal to the geoid offset, or 12.68m around there. I didn't pick the number out of thin air. See the attached too, included in the download, but edited for the locality lat-long. I added the shapefile created by the tool to a scene, applied a cartographic offset of 12.68m and the point sits exactly at sea level. This is a whole lot easier than reprojecting your data vertically (which can be done too). The layer elevation properties: ... View more

Using ArcGIS Pro, the output of Geocode Addresses includes fields with the prefix 'IN_', these are the input address fields.  If you correct the misspellings in the relevant 'IN_' field and run Rematch Addresses the affected records will be re-geocoded. ... View more

Mike can you describe your workflow, for example the type of fieldwork that is happening off-line. The Tasks framework has plans for en embedded control for example that may satisfy your requirement. ... View more

Mike, can you list the functions (find candidates, geocode (single and batch), reverse geocode, get suggestions etc.) that you are looking for?  If you have a geocode service these things are already available via the REST API.  Do you need these functions with a file-based locator without standing up a service? ... View more

Hello You will need to dig into the data model for HERE's raw supply and figure out where to get the left and right city and state names.  My first guess is the ADMINID field will join the streets to the Admin table where ORDER1_NAME will be State and ORDER8_NAME will be City but I'm very rusty on this. ... View more

Hi, Attribute Assistant might be what you are looking for, take a look at Intersecting Feature. ... View more

The capability to read non-native data sources as connections within a project's Catalog pane is planned for ArcGIS Pro.  If you create a Spatial ETL tool or open the Workbench application from the Analysis ribbon you can read your data now, but this requires running a geoprocessing step to access the data and move it into a workspace already known to Pro. ... View more

Ryan In Data Interoperability jargon, real time reading of data sources would be handled by default format read capability or interoperability connections, and these are not yet implemented in Pro.  If you are not familiar with how they work in ArcCatalog or the catalog window in ArcMap, a non-native format or interoperability connection presents a data source as a node in the Catalog tree containing whatever child elements the data source supports, like feature classes and tables. ... View more