Dan....
I understand your take on that, but the back end is not designed that way. Has to be done on the client.
This was decided early on, deliberately. As part of narrowing down the results. So a narrowing could be done without a new fetch. We figured that folks that had sparser numbers of repeaters would need to increase their radius to get valid results. We figured let them do it without re-fetching. I know your next comment is, OK...then move the DB....however, we aren't changing the design even if/when we get a "round tuit." It makes intuitive sense even in the densest areas, like around NY so you can narrow down to the local machines. The spec is for this to occur on the client.
I asked you to put it on the RFinder Login panel as it is specific to RFinder (or anything else that is geolo enabled) and you run through the data set after that screen, so the distances would be calculated and culled out on the fly.
Alternatively, I believe it really belongs on the Import from File screen, so interactively you can cull the list by distance without another fetch (just like on the Android App). This would require a list refresh, of course. And provide the capability consistently for any geolo enabled data source. What's your take on that?
We finally got our Mac today so we are starting on iOS next week...it will be of consistent design.
Thanks for your support!
Bob ___________________________________________________________ RFinder - The Worldwide Repeater Directory Bob Greenberg W2CYK 516.807.0697 Mobile 631.594.2555 Desk/Mobile Simulring 631.389.2508 Fax "When all else fails...Amateur Radio"
Now...can you please add a radius field to the RFinder login panel and constrain the Import From File window to that radius?
I think that makes far more sense to pass that to the server to limit queries before they make the trip, like I do for repeaterbook. When you get that on the server side, let me know and I'll gladly start passing it the user-selected radius.