This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Workflow Dependencies is a great feature. It would be even better if you can save several configurations so that you can switch between them with 1 click only, saving the effort to copy and paste. For example:
Something similar to the Field Configuration (Field Type Files) for Select Tool.
Another option is you save several dependencies there so that you can choose them in the drop-down list of Input and Output tools.
When city is not provided StreetGeocoder tool returns the first one in alphabetical order associated with provided ZIP code. For example, if you submit "380 New York St, 92373" the geocoder will return you "MARIGOLD, CA", instead of Redlands, CA which is the primary place name for 92373 ZIP code.
So if an address has multiple city names within the geocode table, can we provide the recommended city name?
StreetGeocoder when finds an address returns its fields in CAPITAL CASE which is no good for showing to user. Can it return in a correct title case? AFAIK, source data are in valid title case, but the tool or data preparation team make a standardization which actually makes all letters capital.
For those with large web and streaming-media server logs, the ability to geocode IP addresses be an excellent feature, similar to Alteryx's ability go geocode street addresses. Several IP geocoding services exist, with different levels of accuracy and cost. Ideally, the user should be able to choose their own service if they have one, in addition to a default service built-in to Alteryx.
It would helpful if you have a tool which will help us to filter out the data using CASS results column in a meaningful way. On the other day, I CASS'ed 2MM customers and ended up with 1500 combination of CASS result codes. I don't think we would have time to sit walk through all the 1500 combination to find out which I should call it as correct addresses and not the right ones. If you have one already that I didn't know of, please guide me.
I have records of with several address fields per store: address 1, address 2, address 3.(e.g. po box 123, 456 main st, suite 600). I geocode each address field in different iterations, but I want my final input to contain the best geocoding level. e.g. Actual before Zip9. Can we rank the geocoding levels like this below? Then it will be easier to filter out the best geocoding level.
How about adding the ability to split intersecting trade areas at the points of intersection to create two new spatial objects. The two objects could then be used to process customer records and divide them into "territories" based on the line of intersection.