You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The OTP-UI LocationField is building strings based on name, city, state, etc...
We want not to do this in our apps. So need a method for controlling how Pelias records are rendered (e.g., for TriMet, always simply use the "label" attribute from Pelias' results).
For a regional app, we don't need to see state and zipcode in the geocoder results. Thus, we (TriMet's instance of Pelias) do things to clean and shorten address and other data. The geocode record's result string we want to see used is represented in the "label" attribute for all our Pelias records. Ala, this result from Pelias:
The text was updated successfully, but these errors were encountered:
This will be the relevant line. Apologies for not making this a breaking change! I think a fix could either be supporting a custom layerDisplayMap or a new prop that just disables generateLabel altogether.
The OTP-UI LocationField is building strings based on name, city, state, etc...
We want not to do this in our apps. So need a method for controlling how Pelias records are rendered (e.g., for TriMet, always simply use the "label" attribute from Pelias' results).
For a regional app, we don't need to see state and zipcode in the geocoder results. Thus, we (TriMet's instance of Pelias) do things to clean and shorten address and other data. The geocode record's result string we want to see used is represented in the "label" attribute for all our Pelias records. Ala, this result from Pelias:
The text was updated successfully, but these errors were encountered: