After using HERE data in Business Analyst for more than a decade and building maps and processes around this data, Esri has switch all basemaps, geocoding and routing functionality to TomTom with the Business Analyst 2024/2029 data release for the U.S. The change may not have affected some Business Analyst users, but for the use cases that we support, the HERE option is a better fit. Recognizing that contracts are not easily signed or amended, users only have two options with the recent change: 1) switch to TomTom d or 2) pay extra to purchase data or services directly from HERE. Neither of these options are good for Business Analyst users like me.
Rather than pay for TomTom data and HERE data; it would be helpful if we could choose to use HERE geocoding and routing data either by having a different product option or just a different sdlic file for our BA license that excludes the cost of TomTom data (other than what is used for demographic data) and thus allow us to purchase HERE data or services directly or by Esri offering a HERE option within the Business Analyst Pro product.
I realize that formatting two sets of data is an additional cost for Esri, so to minimize that cost, I would be happy if the data downloads remained as they are and that users who select the HERE option would simply get a different sdlic file that didn't unlock the TomTom data (other than demographic map layers) and a lower cost to allow us to buy HERE geocoding and routing data as a replacement. Experienced Business Analyst users can manage using the Network Analyst extension directly with the HERE data without the time-saving features of the Business Analyst tools. It's not ideal, but better than the alternative.
Using the HERE feature classes (rather than a vector tile map), allows us to support users with the following tasks:
-Customizing our analytics maps with a simple click to "Add Data" to place highways above our thematic layers and not having to edit a vector tile layer. Being able to easily edit a highway feature class within Pro is also an advantage for some projects. Vector data is also useful for customizing trade areas with a trace option.
-Using highway exit points as part of a Suitability Analysis for real estate site location.
-Using park data in Suitability Analysis as an amenity for single family residential, affordable housing or multi-family apartment development for real estate analytics.
-Using highway exits, shopping centers, and other points of interest features as part of Location Allocation models to optimize a network of stores, offices, or facilities.
-Using all point ZIP Codes (42,000+ records) for inputs to models that need to account for unique ZIP Codes and not just the ZIP Code areas (~32,000 records). ZIP Code point data is also a good tool for data cleansing before geocoding.
-Using hydrography features in real estate or insurance analysis to minimize risk or understand proximity to river transportation options.
-Using HERE geocoding to return rooftop locations rather than street centerline locations so that customer data can be easily matched to building footprints or parcels. (Rooftop locations would have been better for a recent analysis of customers affected by the Palisades and Eaton fires, since relying on a "closest" option to integrate customer data with the inspection data provided through ArcGIS Online doesn't provide accurate results. Records geocoded with the TomTom data at the "PointAddress" level ended up along the street centerline even though I didn't choose the "routing location" option.)
