You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it might be good to enhance the "Single-field Search" Geoclient parser to ignore/remove the user input address with apartment number or floor number. For example, a real live example of valid address "37 WEST 26TH STREET - 6TH FLOOR, 10010" will return "REJECTED" status.
The text was updated successfully, but these errors were encountered:
Apologies for the late reply. Things here in NYC have been hectic recently :-| as I'm sure you know.
I really like this idea and it shouldn't be too difficult to implement. Assuming it hasn't gathered too much dust, the geoclient-parser subproject was pretty self-contained. Way back I had written a crude but effective, configuration-based, regex-expression test class for the purpose of validating new parser/lexer functionality.
I'll try to take a closer look in the next few days, and if it's easy, I'll add this feature. However, if it's more involved, I won't be able to work on it in the near future. If you're a developer and feel like submitting a PR, I'll do my best to work with you if you have questions.
it might be good to enhance the "Single-field Search" Geoclient parser to ignore/remove the user input address with apartment number or floor number. For example, a real live example of valid address "37 WEST 26TH STREET - 6TH FLOOR, 10010" will return "REJECTED" status.
The text was updated successfully, but these errors were encountered: