Address Importing Best Practices
Hello, looking to crowd source some best practices for importing and standardizing addresses in Quickbase. I know QB uses MapBox but they have some odd formatting practices. For example, they spell ...
Forum Discussion
MarkShnier__You
Qrew Legend
Qrew LegendI doubt that there is a magic bullet here. I suggest that you import your raw data into a staging table in your app. Then use formula using the SearchAndReplace function to successively standardlze non standard elements, for example,
Change Street into St.
Change St into St.
some will be a judgment call.
for example,
123 North St. is probably correct
but 123 Main St. North should probably 123 Main St. N
so my suggestion is to use a staging stable with a human review before pushing into your main table and then to keep improving the formula as you learn about new formats to standardize.
You will also want to document what your standard is so your users can follow it and all be in agreement both for the manual entries and those running the imports.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
- Thanks @Mark Shnier (Your Quickbase Coach) for the suggestion. My main concern is how the QuickBase address field creates the addresses. They don't seem to use a standard convention that we normally see in Google Maps, or more importantly, USPS guidelines.
Unfortunately, I'm importing a few thousand addresses so I'm desperately trying to avoid the human review. I'm also trying to plan for the future, for when end users enter addresses into the database. I'm trying to control accuracy and consistently of the newly entered addresses.
Is it possible to plug in the Google Address Autocomplete into QuickBase?
Or QuickBase, is it possible to change the formatting of your Address Autocomplete?
------------------------------
David Semitekol
------------------------------
