What populates the geography hierarchy and location/address REST LOVs?
We are noticing the option to select invalid city, state, and county combinations in our UI (see example below& by "invalid" I mean the combination does not exist within our manage geographies hierarchy, I realize it may be valid per google).
When we referenced our geography hierarchy we are unable to find an instance where the combination pictured below exists - does anyone know how these REST LOVs are populated? I would have assumed manage geographies would govern what is populated here...but that does not appear to be the case.
Note the below image includes the cities within Kent County MI per the geography hierarchy - notice Walker is not included