-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
a set of generators & test cases for major POIs generated from wikipedia #71
Conversation
Once again, these are awesome. I thought of the existing scripts in |
"expected": { | ||
"coordinates": [ | ||
-96.34028, | ||
30.61 | ||
], | ||
"distanceThresh": 5000, | ||
"properties": { | ||
"layer": "venue" | ||
} | ||
} | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will probably want an expected name
field. Right now all these tests will pass as long as any venue within 5km of the given point is returned. While that's nice for getting around minor name differences it's probably too lenient :(
poke |
lmk if you want to land this? |
@orangejulius lmk if you want to land this or I can close. Trying to clean up my backlog of open / unfinished tasks |
This is partly here as a PoC
I'm curious if you'd want me to integrate it into the scripts in fuzzy-tester. It seems like it's different enough (doesn't use csvs as input) and relies on a bunch of libraries that I'm not sure if it should be integrated into that existing flow. I'm happy to make it work better with that though.
I was curious to see how we're doing on standalone major POIs so ... I built this. It mostly works. wikipedia is a pain.