Prepare to use Osmose issue detail strings

- Remove translation description strings, will be using supplied
translations once the API is updated
- Change the way elements and details are presented since they can't be
easily integrated into the 3rd party description strings
This commit is contained in:
SilentSpike
2020-01-25 20:26:00 +00:00
parent 7d76950d55
commit 5d93d3cace
7 changed files with 112 additions and 291 deletions
+6 -88
View File
@@ -829,94 +829,12 @@ en:
QA:
osmose:
title: Osmose Issue
error_types:
0:
description: '{0} and {1} intersect.'
0-3:
description: '{0} is a suspisciously small building.'
0-4:
description: 'A gap exists between {0} and {1} which looks suspiciously small.'
1040-1:
description: '{0} intersects itself.'
1050-1:
description: '{0} looks like a roundabout mapped in the wrong direction for this location.'
1050-1050:
description: '{0} looks like a mini-roundabout with the incorrect "direction" tag for this location.'
1070:
description: '{1} intersects with {0}, but there is no junction node, bridge, or tunnel.'
1150:
description: '{0} and {1} overlap.'
1190:
description: '{0} looks like it could be mapped more accurately.'
1280-1:
description: '{0} should be on the highway or part of an "enforcement" relation.'
2110-21101:
description: '{0} has a name but no feature tag.'
2110-21102:
description: '{0} is missing a "type" tag.'
3040-3040:
description: '{0} has a non-conventional tag value: "{1}".'
3090-3090:
description: '{0} is tagged with an invalid date value: "{1}".'
3161:
description: 'There is no highway leading to {0}.'
3200-32001:
description: '{0} is tagged "area=yes", but this feature is an area by default.'
3200-32002:
description: '{0} has an "area" tag, but no feature tag.'
3200-32003:
description: '{0} is tagged "area=no", but this feature already isn''t an area.'
3220:
description: '{0} has an "access=yes" or "access=permissive" tag which permits use by all transport modes (ski, horse, hazmat, etc.).'
3250-32501:
description: '{0} has an invalid value for the "opening_hours" tag.'
4010:
description: '{0} uses tag "{1}" which is deprecated in favour of "{2}".'
4030-900:
description: '{0} is tagged with both "{1}" and "{2}".'
4080:
description: '{0} and {1} both appear to represent the same object.'
5010-803:
description: 'The "name" of {0} is written in all capitals.'
5010-903:
description: 'The "name" of {0} has excessive space characters.'
5070-50703:
description: '{0} has an unexpected symbol, {2}, in the "{1}" tag.'
5070-50704:
description: '{0} has an unbalanced {1} character in its name.'
5070-50705:
description: '{0} has an unexpected {1} character in its name.'
7040:
description: 'A power line appears to be unfinished at {0}.'
7040-1:
description: '{0} is a power tower or pole with no connected power lines.'
7040-4:
description: 'Power lines should only have nodes at supports and {0} is not tagged as a pole or tower.'
7090-1:
description: '{0} is a level crossing at a non-junction node.'
7090-3:
description: '{0} is highway feature or barrier with no connected highway.'
8300:
description: 'Traffic signs detected by Mapillary suggest there may be an unmapped {0} nearby.'
parts:
1: 'speed limit'
20: 'max height limit'
21: 'max weight limit'
32: 'roundabout'
34: 'set of speed bumps'
39: 'living street'
8360:
description: 'Object detection by Mapillary suggests there may be an unmapped {0} nearby.'
parts:
1: 'bench'
2: 'type of bicycle parking'
3: 'surveillance camera'
4: 'fire hydrant'
5: 'set of traffic signals'
9010-9010001:
description: '{0} is redundantly tagged with "{1}".'
9010-9010003:
description: '{0} appears to have a descriptive name: "{1}".'
elems_title: Issue Elements
details:
values: Issue Values
tags: Issue Tags
chars: Issue Characters
sug_tags: Suggested Tags
improveOSM:
title: ImproveOSM Detection
geometry_types: