search

HSLdevcom / digitransit-ui

Digitransit UI ("Reittiopas.fi")
https://www.reittiopas.fi/
Other
238 stars 132 forks source link

Disable stop and station layers parameters in Pelias request #5086

Open kalon33 opened 1 week ago

kalon33 commented 1 week ago

I use a Pelias instance that has no stop nor station layers available (available layers are coarse,address,venue,street,intersection,postalcode,locality,neighbourhood,county,localadmin,region,macrocounty,country,macroregion,dependency,borough,macrohood,marinearea,disputed,empire,continent,ocean).

How can I disable these requests? That currently prevents it from returning any results when geocoding an address.

Thanks for your help.

vesameskanen commented 5 days ago

We can fairly easily move search targets into UI configuration, and location search will then work. However, there are many stop searches in the UI - the stop/route search of the front page, stops near you page etc. These will not work unless stops are indexed into Pelias.

Implementing an option to search these from OTP is a considerable developmeet effort.

kalon33 commented 5 days ago

Implementing an option to search these from OTP is a considerable developmeet effort.

Sure, I imagine, but that would allow others to more easily use Digitransit with external Pelias providers (that frequently if not always don't have any consideration for GTFS data).

At least the first part in UI configuration will enable to partly use Digitransit in this situation, currently without geocoding it prevents any migration from v1 and OTP 1.x.

Thanks for what you could do on this.

vesameskanen commented 18 hours ago

I added the control into configuration, see:

https://github.com/HSLdevcom/digitransit-ui/pull/5097

This will be merged into v3 bridge anch next week.

kalon33 commented 17 hours ago

I added the control into configuration, see:

https://github.com/HSLdevcom/digitransit-ui/pull/5097

This will be merged into v3 branch next week.

Thanks a lot! Will try as soon as it will be merged.