Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

Location Data Knowledge Base

Data methodologies, and Release schedules.
We have identified that the Census information for this data is partially updated with 2020 Census data and IDs. Here we present two solutions for those using Census ID with Allocate using either Spatial Match Tool or our new US_2010CensusID_Geocoder Install containing Census IDs from Q1 2021 package.
View full article
The Q2 2021 Business and Location Insights data packages are now available to plug into your analytic processes.
View full article
Have some Latitude/Longitude points and not much else? Working with Spatial Objects and need more information than a simple map point? Time to call in the Reverse Geocoding macro. Reverse Geocoding can give some robust information to help make important business decisions when working with spatial data. Case in point: Your “friend” has hacked the Pokémon Go APK and hands you a list of Pokémon with the associated Latitude/Longitude. You can’t make an informed decision on your next weekend Poke-session without first understanding more than just the location on a map!
View full article
A guide to submitting corrected map or geocoding information to the vendor
View full article
If you need more geographical information on a coordinate, try converting it into a spatial object and using the Find Nearest Tool to find coinciding Experian geographical data from an Allocate Input Tool.
View full article
The Q2 2020 Business and Location Insights data packages are now available for your analysis. The packages include analytics-ready data from a variety of vendors as well as data-specific analysis tools which will empower users to get the most from the packaged data. Here’s what you have to look forward to in this release!
View full article
 Unfortunately at this time, non-U.S. and Canadian geocoding is performed via API calls, and as such, requires an Internet connection.
View full article
Why is my geocoding workflow hanging? It used to run fine – but now it seems to be stuck indefinitely!
View full article
In June of 2012, the USPS made a change to how a P.O. Box operates.  That change now allows for a street address to be used in lieu of a P.O. Box.  This format, known as a P.O. Box Street Address (PBSA), is actually the address of the post office of where the P.O. Box is located. How does this affect Alteryx?  One client brought to our attention that this could potentially affect address and demographic analysis.  Let's say a user has a small list of competitors and they want to run a competitive analysis.  The only issue is that several of these records are using a PBSA.  The demographics for these records will revolve around the post office, not the actual business.   How do we combat this?  The first thing to keep in mind is that Alteryx is perfect for this sort of scenario.  The USPS has posted a list of their post office locations as a .txt file.  Attached to this post you will find an Alteryx Zip Package that informs you of where you can find the file (hint: here) and parses it.  Once it is parsed, one option would be to merge that with the D&B Business Matching Macro to validate or invalidate your list of businesses.  Another option would be to take your business list and compare it to this file to find out if any businesses are using a PBSA.  Either way, we have options! One final note is that it is important to remember that these are valid street addresses.  While the Alteryx Street Geocoder will mark a P.O. Box as invalid, it will see these and most likely geocode them all the way to the street level.   If you would like to read more about this USPS feature, click here.  Until next time! Chad Follow me on Twitter! @AlteryxChad Also, HUGE THANKS to John H. for his help with this post!
View full article