Latest Contributions by BruceHarold

Hello.  Data Interoperability extension has a transformer - FeatureMerger - that will join the shapefile and your other table using multiple columns.  You can obtain an evaluation of the extension if you do not already have it. ... View more

Hi Brett, sorry about the delay responding, I totally missed your comment. The check throwing the error is coded as a string comparison comparing the two spatial references. In your Pro session's Python window key in code like below, replacing the inputs with your layer names. If the spatial references differ you may see where by inspecting the strings. A good way to force agreement in spatial references is to put both data sets into a feature dataset. old = "OldAddress" new = "NewAddress" newSR = arcpy.Describe(new).spatialReference.exportToString() oldSR = arcpy.Describe(old).spatialReference.exportToString() newSR != oldSR # False ... View more

OK! Regularize Building Footprint—Help | Documentation  Requires 3D Analyst extension. ... View more

I can't quite picture what you're looking to do but making squared off boundaries and rotating features is in this sample: https://pm.maps.arcgis.com/home/item.html?id=9398bd2232cb4c8490b0b05015364d28  ... View more

Oh my word, a doc bug!  Thanks for reporting it, I'll send it on. Data Interoperability is an extension like Network Analyst, Spatial Analyst etc., you can evaluate it at no cost. ... View more

OK full disclosure I'm the Product Manager for Data Interoperability 😉 ... View more

All, this pain is totally avoidable, just obtain the Data Interoperability extension and go directly from MySQL to File GDB.  In Data Interop the reader is called MariaDB, in fact there are two, one spatial, one not.  Bouncing data through CSV will throw the schema overboard as even writing a schema.ini file can't handle all data types. ... View more

The ETL approach requires Data Interoperability extension and the ability to author the processing, but we have big sites taking this no-code approach to maintaining hosted feature services from arbitrary source data on a regular schedule, so it works. ... View more

Nice one Joe, however it may be a requirement with this update frequency to have no downtime, in which case I would lean to the ETL approach which operates one feature at a time or to the feature service REST API so you only operate on the feature service change set in milliseconds.  Sorry to be pedantic ;-). ... View more

This topic describes using the arcgis API: Overwriting feature layers | ArcGIS for Developers  ... View more

Hi An ETL approach can operate directly on both the CSV file and the feature service: https://community.esri.com/community/open-platform-standards-and-interoperability/blog/2019/05/31/automate-your-etl-processes-on-a-schedule  You could script it entirely too a few ways.  Is the geometry in the data or are you geocoding? ... View more

if you are working in Pro you also have available arcpy.time.EsriTimeDelta() ... View more

Hi, if USGS have gone to the trouble of maintaining geodetic control for the master LiDAR data and say the raster is in the 2011 realization I'm guessing the shapefile is the dataset to investigate and don't assume they got the datum wrong. This thread NAD83 vs. NAD83(2011)  mentions a transformation to use (NAD_1983_HARN_To_NAD_1983_2011) if the shapefile is in the original NAD 83 datum so try that first. ... View more

Hi K Sathish, at present the licensing issues seem like a hard limit, so no, we cannot say i.dgn support is planned.  If you have Data Interoperability extension there is a cross-grade product that will add the format, see FME Desktop ArcGIS Data Interop Edition here: ArcGIS Data Interoperability & FME Desktop Comparison  ... View more

Hi, Data Interoperability extension does not support .i.dgn files, due to licensing issues, please use the FME product. ... View more