We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use reverse geocoding to search bus stops nearby point reverse geocoding does not find the bus stops closest to the research point
I'm using reverse parameters for te requests https://github.com/pelias/documentation/blob/master/reverse.md#reverse-geocoding-parameters in particular layers: 'stops'
my peelias config is:
"api": { "targets": { "layers_by_source": { "transit": [ "stops" ] } }, "customBoosts": { "layer": { "street": 1, "address": 3 }, "source": { "transit": 1, "openstreetmap": 1, "openaddresses": 3, "whosonfirst": 1 } }, "transit": { "datapath": "/data/transit", "feeds": [ { "layerId": "stops", "url": "https://www.trentinotrasporti.it/opendata/google_transit_urbano_tte.zip", "filename": "stops.txt", "agencyId": "tte", "agencyName": "trentino trasporti esercizio", "layerName": "stops" } ] }
never find bus stops even if I search above for the exact point where there is a stop yet I would say that it is a very useful thing
The text was updated successfully, but these errors were encountered:
Please use the issue template
Sorry, something went wrong.
No branches or pull requests
Use-cases
use reverse geocoding to search bus stops nearby point
reverse geocoding does not find the bus stops closest to the research point
Attempted Solutions
I'm using reverse parameters for te requests
https://github.com/pelias/documentation/blob/master/reverse.md#reverse-geocoding-parameters
in particular layers: 'stops'
my peelias config is:
Proposal
never find bus stops even if I search above for the exact point where there is a stop
yet I would say that it is a very useful thing
The text was updated successfully, but these errors were encountered: