davidmguest's Comments
| Changeset | When | Comment |
|---|---|---|
| 135586982 | almost 2 years ago | I changed it to use the same transliteration as for the the nearby village. way/705445681 |
| 134554058 | about 2 years ago | I've applied the first chunk of reverts.
|
| 134554058 | about 2 years ago | Should I continue checking or do you wish to apply Daniel's revert? |
| 134554058 | about 2 years ago | I did not change any highway tags.
|
| 134554058 | about 2 years ago | 252724820 has been reverted.
|
| 134554058 | about 2 years ago | The use of name tags for numeric names in that are was based on the pre-existing tags for other such roads in the area eg way/122109629 tagged by @eric22. way/252724820 appears in Bing imagery to be a continuation of way/346053155 with no junctions or exits, and with the same grade of highway. I suspect that the highway=tertiary is probably incorrect in this case. |
| 134554058 | about 2 years ago | I have reverted the ref tags, and set the numeric road names as name tags |
| 135504245 | over 2 years ago | amended to use alt_name, alt_name:en etc |
| 135465510 | over 2 years ago | Thanks for spotting my typo. I've now corrected it to name:en1 |
| 133955228 | over 2 years ago | Zeev,
|
| 134628479 | almost 3 years ago | Yes, thanks.
|
| 134148302 | almost 3 years ago | For trees, the name tag should only be used where that particular tree has distinct and significant name. Details of the type of tree should not normally be recorded in the name tag |
| 134125367 | almost 3 years ago | As Hebrew words do not correspond exactly to English words, there can not be just one "correct" translation. This is especially true with proper names.
|
| 134428079 | almost 3 years ago | Thank you, yes.
|
| 52337701 | over 8 years ago | yes - typo now corrected - thanks |
| 52278212 | over 8 years ago | typo - now corrected - thanks |