Closed lukeduran closed 2 months ago
@lukeduran Thank you for the specific list and including 3 examples! This is related to #42, as well. There is a step in our data transformations that takes the County name (e.g. SAINT LOUIS) and reformats it into the syntax you listed above (supposed to be "MO, St Louis County"). Your initial ticket #42 allowed us to identify a handful of locations where this transformation wasn't working. As part of the v2.0.0 release, we've implemented new logic to handle places like DC, all parishes in LA (that aren't actually called counties), and "__ City County" regions (like Charlottesville City). Your list in this ticket is showing more places where additional logic is necessary, such as places that have different casing (e.g. DeKalb) and Saints (which can be listed as St., St, or Saint). These changes will all be incorporated into v2.0.0 and will hopefully resolve the vast majority of edge cases.
This request is now working in our v2.0.0 development environment.
We are getting quite a few errors that seem to be related to not being able to fined max option look up for various regions. In the small sample from which I have tested, I have received errors for the following seven regions:
I would like to understand this error better so that we can have an idea on if this will be a bigger issues across the US as we broaden the surface area that is using this integration. What causes this error @joshuamzm @kellyatradiantlabs?
Below are three examples, but I have more to offer up!
Example 1
Example 2
Example 3