Replies: 1 comment 2 replies
|
Hello, thank you for reaching out and making a discussion thread I think this is a very good idea. I am looking into how this would be implemented. Currently how it works is that when you search for a city we don't actually just trust the extractor on what is returned, we actually run a string based search to make sure that only the correct cities are being returned Having a distance based check would just be one extra step of converting these strings into latitude/longitude points and then comparing those instead. So this does feel like it is technically feasible. I will make an issue about this and I will explore this soon |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I actually set this up for a friend of mine that is having hard time finding a job in Louisville, KY USA. He's not a tech guy, so I host jobops and transferred his resume to rxresume and configured jobops for him. The part I don't really understand is how you tell jobops you want it to find job that are around where you live. Currently I have set 5 or 6 cities that surround his address. This this the correct way to handle this, or is there an easier more efficient way to tell jobops that I want you to find jobs within 50 miles of my city. I feel like if I list specific cities, then i'm going to miss a lot of opportunities because I can't really enter very since city in a 50 mile radius of his address. And since he is right across the river from Indiana, there might be jobs that are still candidates, but then I don't know how to tell jobops to include the multiple states and cities.
All reactions