SqliteError: UNIQUE constraint failed: docs.id, so I guess that is because the service is already running from bringing the geocoder API up. Is there a way to do everything without running into such issues?
1 reply
@DisyGdi_twitter I'm having the same issue "missing authentication credentials for REST request" - did you manage to resolve this?
Hello @petertoner we are still working on this issue. currently trying to connect to elasticsearch via debugger-Pod. What we have learned so far: you need to adjust the pelias.config in the esclient-Part e.g. as mentioned above(shift+enter for line break)
"esclient": {
"hosts": [{
"host": "x.x.x.2",
"port": xxxx,
"protocol": "https"
}],
"auth": { "ApiKey": <API-KEY> }
...
}
Furthermore, the security-settings for for elasticsearch must set correctly. curl for cluster API works, but queries for the index do not work. Could be a misconfiguration on the elasticsearch component. We have to test that. Yet, it seems that the esconfig-Part is read correctly and send to the elasticsearch-Client (see https://github.com/pelias/api/blob/master/routes/v1.js#L33).
I have installed Pelias with docker. I am trying to find US Census tracts from points I find with the search API (much faster and accurate than Nominatim thanks to rich openaddresses). I have an encoded a polyline file (precision 6, null byte for columns, new line for rows) with the census tracts in California and their FIPS codes. I've tried importing this from my project's pelias.json configuration file but it does not show up in PIP (port 4200) results (only WOF data shows up in this results). Pelias PIP return of WOF data is 10X faster than my existing GDAL/OGR for a Census Tracts shapefile, so I am hoping to implement a Pelias solution. Do you have any suggestions for how to proceed?
This is for a batch process for a research project. I am new to Pelias but determined to get this working.
elias@1-openaddresses-rjk4r:/code/pelias/openaddresses$ ./bin/download
info: [openaddresses-download] Attempting to download all data
error: [openaddresses-download] Failed to download data message=Command failed: unzip -o -qq -d /data/openaddresses /tmp/202123-37-12tjcyy.caci.zip
[/tmp/202123-37-12tjcyy.caci.zip]
End-of-central-directory signature not found. Either this file is not ??
Hi everyone,
I am currently running a pelias instance using custom csv-imported data for Switzerland.
It seems to be working quite well, but some addresses are not found.
For example, the following query:
qry = "Chemin de la Pré-de-la-Raisse 11"
qry = urllib.parse.quote(req)
requests.get(f"{pelias}search?text={qry}&layers=address").json()Yields:
{
"geocoding": {
"version": "0.2",
"attribution": "http://api.yourpelias.com/attribution",
"query": {
"text": "Chemin de la Pré-de-la-Raisse 11",
"size": 10,
"layers": ["address"],
"private": False,
"lang": {
"name": "English",
"iso6391": "en",
"iso6393": "eng",
"via": "default",
"defaulted": True,
},
"querySize": 20,
"parser": "pelias",
"parsed_text": {
"subject": "11 Chemin de la Pré-de-la-Raisse",
"street": "Chemin de la Pré-de-la-Raisse",
"housenumber": "11",
},
},
"engine": {"name": "Pelias", "author": "Mapzen", "version": "1.0"},
"timestamp": 1615458787863,
},
"type": "FeatureCollection",
"features": [],
}With no features.
While if I explore directly elasticsearch using this query:
GET pelias/_search
{
"query":{
"match": {
"address_parts.street": "Chemin du Pré-de-la-Raisse"
}
}
}I do have an exact match with the following document:
{
"_index" : "pelias",
"_type" : "_doc",
"_id" : "admin_ch:address:295517056-0",
"_score" : 17.968594,
"_source" : {
"center_point" : {
"lon" : 6.130037,
"lat" : 46.167932
},
"parent" : {
"continent" : [
"Europe"
],
"continent_id" : [
"102191581"
],
"continent_a" : [
null
],
"country" : [
"Switzerland"
],
"country_id" : [
"85633051"
],
"country_a" : [
"CHE"
],
"region" : [
"Geneva"
],
"region_id" : [
"85682291"
],
"region_a" : [
"GE"
],
"county" : [
"Genève"
],
"county_id" : [
"102062917"
],
"county_a" : [
null
],
"locality" : [
"Plan-les-Ouates"
],
"locality_id" : [
"1125887615"
],
"locality_a" : [
null
],
"localadmin" : [
"Plan-les-Ouates"
],
"localadmin_id" : [
"404328619"
],
"localadmin_a" : [
null
]
},
"name" : { },
"address_parts" : {
"street" : "Chemin du Pré-de-la-Raisse",
"number" : "5",
"zip" : "1228"
},
"source" : "admin_ch",
"source_id" : "295517056-0",
"layer" : "address"
}
}I don't understand why this particular exemple doesn't work, as many of my other test addresses do indeed work.
Does anyone have an idea where to look for? How to debug that?
Thanks in advance :)
Nice, didnt see that page although I did scour through the different repositories.
I guess I needed more clarification on the 'venues' portion.
A good example would be if I wanted to make a request targetting particularly OSM (but others as well if they have it) data on point of interest.
Something like 'all entertainment points of interest in a 50 mile radius of this point'
I can do that with the overpassAPI, I can understand the structure of the data and OSM has a whole wiki on POI.
From what ive seen you cannot do that with pelias.
However the reason I wanted to make sure is because the system in place could easily support this functionality given a bit of legwork, and this seems like a very well organized project!
Could someone advise me how I could include the candaian postal code geocode data from here: https://www.serviceobjects.com/blog/unique-us-canadian-zip-code-files-available-download/ into pelias ?
