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
Nominatim has the capability to save any OSM tag as extra information with a place object and to return this via the API. Photon currently ignores this information completely even though it might be interesting for special purpose installations (e.g. a search engine for restaurants also wants to return the cuisine information if available.)
Returning arbitrary tags is a bit difficult with ElasticSearch but we could add a fixed set of selected tags. These would not be searchable but only be returned as extra information, just like Nominatim does. I'd suggest an additional property extra, which contains the tags that are available. If there is not extra infromation for a place, the property would be omitted completely, e.g
Nominatim has the capability to save any OSM tag as extra information with a place object and to return this via the API. Photon currently ignores this information completely even though it might be interesting for special purpose installations (e.g. a search engine for restaurants also wants to return the
cuisine
information if available.)Returning arbitrary tags is a bit difficult with ElasticSearch but we could add a fixed set of selected tags. These would not be searchable but only be returned as extra information, just like Nominatim does. I'd suggest an additional property
extra
, which contains the tags that are available. If there is not extra infromation for a place, the property would be omitted completely, e.gImplementation steps:
-extratags
for the import that selects the tags to add to the Photon database.CC @hbruch
The text was updated successfully, but these errors were encountered: