Children of arbitrary range not returned

[bertday]

Searching for 1410-1430 GERMANTOWN gives a 404. OPA API returns a number of addresses in that range.

http://property.phila.gov/?a=1410-1430%20GERMANTOWN&u=

[mjumbewu]

ugh. i notice as well that the parity of the low number is respected in current property. is that the right behavior?

(e.g. http://property.phila.gov/?a=1411-1430%20GERMANTOWN&u= gives addresses on the odd side of the street)

[bertday]

@mjumbewu I hadn't really anticipated that use of the API, but I guess that's what I would expect to get back -- all the addresses on the same side of the street in that range. Do you think that would be hard to implement?

[bertday]

This seems like part of a bigger issue around handling arbitrary range searches in the API. There are a few questions around the search format/matching process that will have to be addressed first (e.g. do we require users to enter two equal-length numbers like 1410-1430 to signify a range search vs. 1410-30 for an exact ranged address lookup? Should we try the exact lookup first and fall back to the range search?) This could also be addressed with better spatial/map-based lookup tools.