# Should Addresses be used as Names / Sollten Adressen als Namen verwendet werden **URL:** \ **Category:** Website\ **Created:** [July 13, 2020, 8:25am UTC](https://forum.kurviger.com/t/should-addresses-be-used-as-names-sollten-adressen-als-namen-verwendet-werden/3789 "2020-07-13T08:25:03Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![rumbrummer](https://forum.kurviger.com/user_avatar/forum.kurviger.com/rumbrummer/32/113_2.png) [@rumbrummer](https://forum.kurviger.com/u/rumbrummer)\ **Post date:** [July 14, 2020, 9:37am UTC](https://forum.kurviger.com/t/should-addresses-be-used-as-names-sollten-adressen-als-namen-verwendet-werden/3789/10 "2020-07-14T09:37:27Z")
> [@devemux86](#): > > Probably mean only for the website, as the application works differently. Hi, I agree, as already mentioned here: > [@Website: Waypoint names](https://forum.kurviger.com/t/website-waypoint-names/216/35): > > Hi, yes, I know, and I wrote it: But to say it clear: I think, the solution of the app is much better: Entering a point using the search result automatically sets the waypoint name. I have some doubts if anybody wants to have the coordinates as name - but if you want to have the useful names, you save a lot of clicks. Regards Markus I just did a few tries with the app: If I search an address in a city, the app copies the street name to waypoint name. From my point of view this is a good compromise between given information and short waypoint name - I think usually there are not multiple addresses with same street name within one route. I think Robins proposal is a good solution: > [@boldtrn](#): > > In the export modal, users could opt-in to automatically get the address as name, if no name is set. Regards Markus --- _[View the full topic](https://forum.kurviger.com/t/should-addresses-be-used-as-names-sollten-adressen-als-namen-verwendet-werden/3789)._