Latest Contributions by DarrenCook1

‎07-17-2022

The U.S. 2022 Business Analyst dataset is the first release to use the updated Census 2020 administrative boundaries. These new boundaries have changed significantly at all levels, in all areas of the country, from those in Business Analyst datasets prior to 2022. Geography levels such as Counties or Block Groups, may have gained or lost area, been split into multiple polygons with new IDs, or been removed all together. It is critical that you update your standard geography trade areas prior to using this dataset. Doing so ensures that the output data, returned from your analysis, represents the current administrative boundaries, which are included in the 2022 dataset. Business Analyst users of ArcGIS Pro and ArcMap can connect to this dataset now by signing into ArcGIS.com and selecting United States: Esri 2022. As illustrated in the image above, the U.S. Esri 2021 dataset continues to be available for selection on ArcGIS.com. This "past year" dataset remains available to provide a transition period to migrate workflows, trade areas and other geographic data to the significantly changed U.S. Business Analyst 2022 dataset, based on Census 2020 boundaries. The U.S. Esri 2021 dataset is based on the older Census 2010 boundaries. Therefore, the need to ensure that your standard geography trade areas match the boundaries of the Business Analyst dataset in use, is bi-directional. You can run the Generate Standard Geography Trade Areas tool, from the Trade Areas toolbox of the Business Analyst toolset in ArcGIS Pro, to re-create your standard geography trade areas. Our recommendation is to add the dataset year that the trade areas are built from, to the Output Feature Class name. Boundary changes to Census Geography levels only occur once every decade. During this period of transition, it is critical to ensure that standard geography market areas are built with boundaries from the Business Analyst dataset to be used in your analysis. The risk of inadvertently returning incorrect data, in this context, is completely mitigated by ensuring the same Business Analyst dataset is used to create standard geography boundaries and conduct analysis. Please find links to related background information in blogs from Garry Burgess and Helen Thompson, respectively: https://www.esri.com/arcgis-blog/products/bus-analyst/data-management/standard-geography-sites-in-20... https://www.esri.com/arcgis-blog/products/bus-analyst/data-management/migrate-business-analyst-conte... Please contact us here with any questions or concerns. We are available to help! Thank you, Darren Cook Product Engineer - ArcGIS Business Analyst

‎01-18-2019

Hi Katie, Thanks for the question. Unfortunately, there is no way to calculate MOE 'on the fly' within the Business Analyst Custom Data workflow. Thank you for letting us know that this would be a useful enhancement. We have shared and discussed this feedback with our Product Management team. Additionally, we invite you to submit this feedback to the https://community.esri.com/community/arcgis-ideas website as an enhancement request for a future release. Please let us know if you have follow up questions or if we can help in any other way. Thank you, Darren Cook

‎04-03-2018

Hi Brandon, As you have noted, the 'Target Groups' parameter does not exist within the 'Segmentation Penetration Map' gp tool. However, I have discussed this scenario with one of our developers and he suggested an alternative approach. You could create a Python tool that will accept the 'Target Group' XML file and 'Target Name' inside the 'Target Group.' In Python code, open the Target Group XML file, find the required target, read the segments inside that target and pass them to 'Segmentation Penetration Map.': arcpy.TargetMap_ba(SegmentationBase="Total Households", SegmentaionClusters="'Top Tier';'Professional Pride';Boomburbs", SegmentationLayer="US.ZIP5", SegmentationAnalysisResultFolder="C:/My Output Data/Projects/Default Project/Segmentation/Segmentation Analyses/Target Map", CreateReport="CREATE_REPORT", CreateFeatureClass="CREATE_OUT_FEATURECLASS") C:\My Output Data\Projects\Default Project\Segmentation\Target groups\Target Group\TargetGroup.xml <?xml version="1.0" encoding="utf-8"?> <TargetGroupData xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" SegmentationSystem="Tapestry 2014"> <Target name="MaxTarget1"> <Cluster code="1A" name="Top Tier" /> <Cluster code="1B" name="Professional Pride" /> <Cluster code="1C" name="Boomburbs" /> </Target> </TargetGroupData> We hope this is helpful and will keep an eye out for follow up questions. Thank you, Darren

‎04-03-2018

Hi Brandon, Great to hear that you are diving into Model Builder! You may have already picked up on this but if not, the Iterator toolset would be applicable to your needs. The Iterator toolset contains twelve iterators that help repeat a process or set of processes on a set of inputs. An overview of the Iterator toolset—Help | ArcGIS for Desktop Thank you, Darren

‎02-15-2018

Hi Brandon, There is a second approach that you should be able to immediately employ and it sounds like it will meet your needs. You can use a spatial join to assign closest store to each of your customer records and the output layer will contain closest store ID (plus any additional selected fields) appended to each customer record. 'Spatial Join' is a GP Tool. You can access it by searching the geoprocessing menu or by right clicking on your customer file within the Table of Contents, and then selecting 'Joins and Relates' from the contextual menu and subsequently clicking 'Spatial Join.' Either approach will launch the tool and the parameters should be set as follows: The 'Target Feature' should be your customer layer and 'Join Features' should be your stores/facilities (joining stores to customers based on spatial location). 'Output Feature Class' will be the the new file, which will contain each customer record with closest store information. The 'Join Operation' should be set to 'Join One to Many,' so that stores can be assigned to more than one customer. Lastly, 'Match Option' should be set to 'Closest Geodesic.' We hope that this helps and will keep an eye out for follow up questions. Thank you, Darren

‎05-17-2017

Hi Heather, Thank you for contacting us to share your feedback as well as your questions. We are glad to hear that you are having success with the locators within Business Analyst! The geocoding documentation is included within the StreetMap Premium help and can be found on the drive where your local data is installed. Assuming the data is installed on your C: drive, the path would be as follows: C:\ArcGIS\Business Analyst\US_2016\Documentation\2016 StreetMap Premium\help.htm. Note that the link assumes 2016 data is installed locally. If you are using and older version, please replace '2016' with the correct year. Once you open the html help, please expand ‘Geocoding Addresses,’ towards the top of the left pane and double click ‘About the address locators for geocoding.’ The information within this page is relevant to your questions but if further details are needed, just let us know. As for the input records containing ZIP4 IDs that are not matching with the ZIP + 4 Locator, one possibility that the underlying locator data is older than the ZIP 4 IDs. We would be happy to investigate specific (ZIP 4) input values that are not matching and provide details if you are able to send examples. Thanks again for contacting us. We will 'stay tuned' for any follow up questions. Darren ArcGIS Business Analyst Team

Online Status	Offline
Date Last Visited	‎01-31-2024 09:39 PM

My Ideas

Latest Contributions by DarrenCook1

Update your ArcGIS Pro standard geography trade areas before using the Business Analyst 2022 Dataset

Re: Calculating Margin of Error for Custom Data

Re: Automating BA tasks

Re: Automating BA tasks

Re: ArcGIS Pro BA Workflow

Re: Documentation for BA Address Locators

Re: Documentation for BA Address Locators

Re: Calculating Margin of Error for Custom Data

Re: Automating BA tasks

Re: Automating BA tasks

Re: ArcGIS Pro BA Workflow