Advent of Code is back! Unwrap daily challenges to sharpen your Alteryx skills and earn badges along the way! Learn more now.
Free Trial

Weekly Challenges

Solve the challenge, share your solution and summit the ranks of our Community!

Also available in | Français | Português | Español | 日本語
IDEAS WANTED

Want to get involved? We're always looking for ideas and content for Weekly Challenges.

SUBMIT YOUR IDEA

Challenge #54: Data Prep Address Parsing

Bobbyt23
12 - Quasar

Still don't enjoy Regex.

Jon-Knepper
8 - Asteroid

Here is my solution!

 

Spoiler
Untitled.png
mshishido
8 - Asteroid

REGEX

danielhoge
8 - Asteroid

 

Spoiler
Screenshot 2024-07-03 134920.png

 

 

danbostrom
8 - Asteroid

 

 

zraposoaandm
8 - Asteroid
Spoiler
Capture.PNG
AndrewPowell
8 - Asteroid
Spoiler
Well that regex drove me mad for a while, guess I'd best getting some more studying done 😉

Screenshot 2024-08-23 173001.png

michael_apau
8 - Asteroid
Spoiler
Screenshot 2024-09-02 170711.png

Mikeimbi
8 - Asteroid

Challenge 54

fluteman
9 - Comet

I made it difficult by really thinking about the syntax of a street address.

 

A reference table for street long and short names was used.

A reference table for state long and short abbrev was used.

 

A comment was made that in the US, we use SE, SW, NE, NW after the street type ST NE (for example).

To build out the reference table further inserting rows for SE SE, SW, SW, NE NE and NW NW should suffice.

 

We also did a check where the state may come in long format (even though it wasn't required).

 

The idea was to get the address into a standardised format.

 

We used reversestring() function and find/replace tool heavily!