Closed timburgess closed 6 years ago
Hi @timburgess, I had a look just now at our geocode.earth servers and I get the following results:
/v1/search?text=41 Thompson St Aitkenvale QLD Australia
1) 41 Thompson Street, Aitkenvale, QLD, Australia
2) 41 Thompson St, Aitkenvale, QLD, Australia
the top hit is from the au/countrywide
file from openaddresses and the second is from the au/qld/statewide
file from openaddresses.
.. which is odd because it looks like you're importing the country-wide file.
could you please try two things for me:
Queensland
instead of QLD
to see if it's a parsing error.placeholder service disabled
, this additional parser will give you improved query matching.The confidence scores all being 1 is a known issue, @orangejulius do you remember why this is the case?
here's a copy of the results I'm seeing: https://gist.githubusercontent.com/missinglink/5969b4b407ec3a62167bd1b54ec5d3ac/raw/0660b7c0f9a90a1212673a0a3381c5c31d8fc6d5/api_issue_1164.json
Are these two results included in your resultset but lower down the list? I'm trying to figure out if it's a matching issue or a sorting issue.
@missinglink Thanks! With the existing setup and query as above, I get 10 features back in the FeatureCollection object, but none of those are the two in your gist - which appear to me to be valid results.
1 - Trying http://108.61.96.7:3100/v1/search?text=41+Thompson+St+Aitkenvale+Queensland+Australia
, I don't get them in the resultset.
2 - I haven't tried using placeholder
yet. I'll set that up and see if I can get your result.
I've got placeholder
running as a service now and with api
using that. I get the expected single record from my query: id au/countrywide:d9ee08a0d2958c89 :+1:
I've runup pelias / elasticsearch 2.4 / nodejs 6.14 / libpostal and have loaded WOF and openaddresses. I've dealt with a few things like elasticsearch tweaks/memory, getting the libpostal 8080 server going, ensuring that
lookupAdmin
is configured, etc., but I now have every piece running without error. I am usingproduction
branch where it is present in a repo.As you can see with the
pelias.json
I'm using I've loaded up Australia specifically. WOF and opensaddresses pull the requisite data and I see the _count in elasticsearch that I would expect.However on doing a query like
http://localhost:3100/v1/search?text=41+Thompson+St+Aitkenvale+QLD+Australia
which is a fairly common street name, I get a response which is a FeatureSet that incorporates each street in the country that has that name all with a confidence of 1. I was expecting that I would get a result with the street name of the neighbourhood as the highest confidence. Looking at the response, libpostal is identifying theneighbourhood
correctly but that seems to be disregarded in the elasticsearch query.The initial part of the query response is:
The api startup is:
and my
pelias.json
is: