Context Navigation

Changes between Initial Version and Version 1 of Ticket #23126, comment 9

initial	v1
1		I have thought about this again and changed my ~~opinion~~. The more detailed you map `area:highway` the more tags you need to add. Think about a road with different surfaces and likely different values for smoothness per lane. It would still be possible to use `surface:lanes` and `smoothness:lanes` but a little duplication might not harm.
	1	I have thought about this again and changed my mind. The more detailed you map `area:highway` the more tags you need to add. Think about a road with different surfaces and likely different values for smoothness per lane. It would still be possible to use `surface:lanes` and `smoothness:lanes` but a little duplication might not harm.
2	2
3	3	Writing Validator rules in case of conflicting values of optional tags between `highway=` and its corresponding `area:highway=` seems to be a complex task beyond my skills and I think this could only be done with java code (if it is possible at all).
	4
	5	Edit: This is about `smoothness`. I am still opposed to `step_count` as the information on the `highway=steps` should be sufficient and for complex steps you need to use a different system, anyway. Similar is true for the other mentioned tags `*=yes/no` which are duplicates and a look at the linear object should tell you all you need.