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
It seems there are many nodes that have null values as names, for example in http://wheelmap.org/api/nodes?bbox=100.47211034315237,13.78323982481387,100.5647266871044,13.87317184424734&api_key=[API_KEY_HERE].
Looking at OpenStreetMap, they do have a multilingual name attribute. Are multilingual names supported? If not, the import should at least consider using a multilingual name if it's the only name that exists, and maybe prioritize a en: name over other existing languages.
The text was updated successfully, but these errors were encountered:
Thank you @opyh .. just FYI see this image, our search for public_transfer is returning results but most don't have a name, and one has the name in Thai. I don't know how to interrogate OpenStreetMap and their name attribute that you refer to, so I don't think I'm going to help you investigate this without learning a lot more myself about OSM data. Interesting that those that have a name have it in Thai and not the English transliteration (which are very common here, every station has the Thai and English version signposted on them).
I have resorted to using the Category name when the Node name is null as you suggested.
It seems there are many nodes that have
null
values as names, for example inhttp://wheelmap.org/api/nodes?bbox=100.47211034315237,13.78323982481387,100.5647266871044,13.87317184424734&api_key=[API_KEY_HERE]
.Looking at OpenStreetMap, they do have a multilingual name attribute. Are multilingual names supported? If not, the import should at least consider using a multilingual name if it's the only name that exists, and maybe prioritize a
en:
name over other existing languages.The text was updated successfully, but these errors were encountered: