Latest Contributions by BruceHarold

In an earlier post I enumerated common data source types that you will encounter when bringing data into ArcGIS.  This document discusses one of these data patterns - common file types available on your computer or by simple manual download. The particular scenario discussed in the attached document is a CSV file with commonly found ETL requirements:  Controlling the output geodatabase feature class schema and creating geometry from a column.  ModelBuilder in ArcGIS Pro 3.3 is the automation environment - it has everything you need, and preserves work for on-demand re-use. The post attachment includes the discussion document and Model, but not the subject data, which you can download yourself. Please use this post to ask questions or comment. ... View more

In an earlier post I enumerated common data source types that you will encounter when bringing data into ArcGIS.  This document discusses one of these data patterns - calling an API that requires pagination to retrieve a complete dataset.  Pagination is a technique used by data publishers to manage load on their servers. Response payloads are typically JSON or CSV. Please read the attached document and use this space to ask questions. The post attachment also includes the ArcGIS Pro 3.3 toolbox discussed, but not the subject data. ... View more

One-page "cheat sheet" documents are always popular, for example in the context of ArcGIS a perennial favorite has always been the functionality matrix for ArcGIS Enterprise. When considering your inbound ETL options there are high level decision criteria, this document (available as PDF in the post download) is a brief summary of two of them, namely where your source data comes from and how often you need to bring it in. This is only light guidance, in many cases you will have multiple implementation options, so treat this as an invitation to have a discussion, including in this community space. ETL Patterns   ... View more