Add new quest to determine the maxheight #960

ENT8R · 2018-03-08T19:28:57Z

This PR is a little bit more extensive... It adds a quest for determining the maximum height of e.g. tunnels or covered ways, parking entrances for underground and multi-storey parkings and of course height restrictors. It fixes #399, #421, #447.
Sorry for creating so many PRs in the last time, but I hope this helps to get the issue amount below 100 😄

Here are some things I have questions about:

Can somebody maybe proofread the list of height units per country?
Result: the measurement system is now stored in a new file. All countries and their units were checked while adding them.
If there is no sign, should we tag it as maxheight=default (used about 10K times) or maxheight=no_sign as proposed by the wiki but only used 14 times according to taginfo...
see the source code for more information
Result: There is another menu for selecting the best fitting value
Should the query be improved to add the same functionality as the maxheight map by @mmd-osm does?
Result: don't add additional functionality because this might need some processing
If the unit is metric but the input value is an integer (without values after the comma 😄), should automatically a trailing .0 be added by SC? This is also the current behaviour...
Result: Should not be added and removed

The quest looks like this in countries with the metric system known:

And this is how the quest will look like in countries with the imperial system

This is the current Overpass query: https://overpass-turbo.eu/s/wSP

matkoniecz · 2018-03-08T21:37:09Z

I was just reading code, but

This height looks implausible

(if necessary) should be rather something like

This height looks implausible, are you sure that it is correct?

westnordost · 2018-03-08T21:37:41Z

Wow, this is a complex one. You even took care of those imperial countries, nice.

Sorry for creating so many PRs in the last time, but I hope this helps to get the issue amount below 100 😄

It would be better if you do one thing after another and see it to the end, rather than creating one construction site after another, in my opinion. These days, it feels like I am spending 90% of the time I have for SC on commenting on tickets or reviewing PRs.
On that note, I feel sorry for fritruc that I will not help him nor review his PR (in this state), seeing the amount of code he fabricated, but I just don't have the time for that. Perhaps you could give him a hand and point out the blunders and possible improvements in his code since you know quite a bit of Android development, the SC source code by now and the quality I demand?

Anyway, will review your code now...

goldfndr · 2018-03-08T22:41:25Z

app/src/main/java/de/westnordost/streetcomplete/quests/max_height/AddMaxHeight.java

+			"(" +
+			" node['barrier'='height_restrictor']" +  QUERY_RESTRICTIONS + ";" +
+			" node['amenity'='parking_entrance']['parking'~'^(underground|multi-storey)$']" +  QUERY_RESTRICTIONS + ";" +
+			" way['highway'~'^(" + ROADS + ")$']['tunnel'~'^(yes|building_passage)$']" +  QUERY_RESTRICTIONS + ";" +


Please add avalanche_protector to tunnel types.

goldfndr · 2018-03-08T22:55:15Z

app/src/main/java/de/westnordost/streetcomplete/quests/max_height/AddMaxHeightForm.java

+	{
+		double height = Double.parseDouble(getHeightFromInput());
+		double heightInMeter = isMetric ? height : feetToMeter(height);
+		return heightInMeter > 6;


Low heights might also be implausible, maybe < 2 m?

westnordost · 2018-03-08T21:45:17Z

app/src/main/java/de/westnordost/streetcomplete/quests/max_height/AddMaxHeight.java

+			" way['highway'~'^(" + ROADS + ")$']['tunnel'~'^(yes|building_passage)$']" +  QUERY_RESTRICTIONS + ";" +
+			" way['highway'~'^(" + ROADS + ")$']['covered'='yes']" +  QUERY_RESTRICTIONS + ";" +
+			");" +
+			"out meta geom;";


By the way, Overpass QL does not require ' for simple values like i.e. barrier=height_restrictor. Would improve readability a bit.

westnordost · 2018-03-08T21:58:13Z

app/src/main/java/de/westnordost/streetcomplete/quests/max_height/AddMaxHeight.java

+			/*TODO: maxheight=default or maxheight=no_sign?
+			according to https://taginfo.openstreetmap.org/keys/maxheight#values maxheight=no_sign is only used 14 times,
+			while maxheight=default is used about 10K times*/
+			changes.add("maxheight", "default");


But what is maxheight=default (or no_sign) supposed to mean? What is the information gain here?

I think it would be better to in that case ask the user about an estimate of the height and tag the estimate then. (Choose a tagging where it is clear that this is an estimate)

They’re documented on the Osm wiki ---> https://wiki.openstreetmap.org/wiki/Key:maxheight

What is the information gain here?

I guess that in typical country it is mandatory to sign maxheight if it is below some value (I would expect it to be chosen so normal-sized vehicles can pass). So lack of sign indicates that normal vehicles can pass trough. Also, with this it is always possible to tag something, making this quest possible.

about an estimate of the height and tag the estimate then

At least I am not really able to estimate height with any kind of accuracy that would make worth tagging it.

westnordost · 2018-03-08T21:59:03Z

app/src/main/java/de/westnordost/streetcomplete/quests/max_height/AddMaxHeight.java

+		}
+	}
+
+	@Override public String getCommitMessage() { return "Add maximum height"; }


I think this is usually plural

app/src/main/java/de/westnordost/streetcomplete/quests/max_height/AddMaxHeight.java

+	{
+		boolean isParkingEntrance = "parking_entrance".equals(tags.get("amenity"));
+		boolean isHeightRestrictor = "height_restrictor".equals(tags.get("barrier"));
+		boolean isTunnel = "yes".equals(tags.get("tunnel"));


westnordost · 2018-03-08T22:13:21Z

app/src/main/java/de/westnordost/streetcomplete/quests/max_height/AddMaxHeight.java

+
+	@Override public int getTitle() { return R.string.quest_maxheight_title; }
+	@Override public int getDefaultDisabledMessage() { return 0; }
+	@Nullable @Override public Boolean isApplicableTo(Element element) { return null; }


I think it is. But it would be a long chain of if-checks, I figure. You could use several tagfilters. I.e.... (pseudo code)

TagFilterExpression nodeFilter = parser.parse("nodes with (barrier=height_restrictor or amenity=parking_entrance and parking ~ underground|multi-storey) and !maxheight and !maxheight:physical"); TagFilterExpression wayFilter = parser.parse("ways with highway~(primary|secondary|tertiary|trunk)(_link)?|motorway|service|residential|unclassified|living_street and (covered=yes or tunnel~yes|building_passage) !maxheight and !maxheight:physical"); return nodeFilter.matches(element) || wayFilter.matches(element);

To be honest, with a little extension on the TagFilterExpression class (adding a method that outputs the TagFilterExpression without the full thing (bbox and out geom meta;) as Overpass QL, perhaps these filters could be used as well in the getOverpassQuery method.

westnordost · 2018-03-08T22:43:50Z

app/src/main/java/de/westnordost/streetcomplete/quests/max_height/AddMaxHeightForm.java

+			if (!heightInput.getText().toString().isEmpty())
+			{
+
+				return heightInput.getText().toString().replace(",", ".");


Where does the "," come from?

Ah, I see. If the user enters it with , instead of . (in Germany, e.g.) However, I think, even the German keyboard layout for numbers limits the input to . as a decimal separator.

Right, this is why I added it...

I think, even the German keyboard layout for numbers limits the input to . as a decimal separator.

I don't think so... I even specified the possible input values (the same is done for the housenumber quest too) here:
https://github.com/ENT8R/StreetComplete/blob/59b437425c51bacc9c0fd8c8b9866c86e4f474e2/app/src/main/res/layout/quest_max_height.xml#L22

ENT8R, the line you cited is not there to allow German decimal points but to allow an input like "3,5" (multiple housenumbers).

I do not believe that Android multilingual support is supposed to be that crappy that it leaves it to the app to "understand" the number of the user input.

You should set android:inputType=numberDecimal and probably remove the android:digits="0123456789.,", then everything should be fine.

Alright. Will do that!

westnordost · 2018-03-08T22:46:47Z

app/src/main/java/de/westnordost/streetcomplete/quests/max_height/AddMaxHeightForm.java

+		{
+			if (!feetInput.getText().toString().isEmpty() && !inchInput.getText().toString().isEmpty())
+			{
+				return feetInput.getText().toString() + "." + inchInput.getText().toString();


Not sure why you do this, but I find this dangerous. Ten inch are not one foot, twelve inch are one foot. By introducing the dot, you seem to imply that the inch are the decimal, which they are not.

Yeah, true... I will have to find a better solution...

westnordost · 2018-03-08T22:51:07Z

app/src/main/res/drawable/background_max_height_sign.xml

+    <path
+        android:fillColor="#fff"
+        android:pathData="M17.967,22.201c3.207,-1.6 5.235,-4.876 5.236,-8.461 -0.002,-3.585 -2.029,-6.86 -5.236,-8.461l-4.224,3.698 -4.217,-3.694C6.317,6.881 4.287,10.156 4.283,13.74c0.005,3.585 2.035,6.859 5.244,8.456l4.217,-3.694z"/>
+</vector>


Actually, it would also be possible to use the simple layer-list drawable (see background_maxspeed_sign.xml). The advantage would be that it is also displayed as vector on older Android versions.

Is there some chance to convert it? I don't think so, but I'm not familiar at all with those layer-list drawables...

No. But hmm, don't mind about that. Turns out that those two triangles are not possible with shape drawables alone.

westnordost · 2018-03-08T22:52:57Z

app/src/main/res/values/strings.xml

+    <string name="quest_maxheight_tunnel_title">What is the height limit of this tunnel?</string>
+    <string name="quest_maxheight_answer_noSign">There is no sign</string>
+    <string name="quest_maxheight_answer_noSign_confirmation_title">Are you sure there is no sign?</string>
+    <string name="quest_maxheight_answer_noSign_confirmation">Did you check at both ends? If there is no sign, default limits apply.</string>


This doesn't make sense. What are the "default limits"? Also, it doesn't make sense (IMO) to ask the user to look at "both ends". I think it doesn't matter from which side you enter a tunnel for the height restriction to apply. :-D

westnordost · 2018-03-08T22:56:38Z

res/country_metadata/heightUnit.yml

+# https://en.wikipedia.org/wiki/Metrication#Overview
+# https://en.wikipedia.org/wiki/Imperial_units#Current_use
+default: [m]
+CA: [ft, m]


Canada should be meter only, see https://en.wikipedia.org/wiki/Comparison_of_MUTCD-influenced_traffic_signs
Or, at least, m first, then ft.

goldfndr · 2018-03-08T23:04:07Z

app/src/main/java/de/westnordost/streetcomplete/quests/max_height/AddMaxHeightForm.java

+		{
+			if (!feetInput.getText().toString().isEmpty() && !inchInput.getText().toString().isEmpty())
+			{
+				return feetInput.getText().toString() + "." + inchInput.getText().toString();


Although simplifying inches to a range from 12 to 10 doesn't seem so bad, an 11 inch measurement will give an odd result. (I admittedly didn't check against boundary condition.)

westnordost · 2018-03-08T23:06:29Z

Hmm, not sure why it is not shown (to me), but I also wrote:

Unfortunately, the US is not the only country that uses imperial units. You need to separate the selection of the layout from the selection of which unit to select. I.e. this is how the signs look like in UK apparently.

Traffic sign layout: most countries follow the International Standard, see also the comparison of European road signs. This is the layout I saw in your screenshot. However, I think you should also include the "m" in the form, even if it is not a dropdown menu, because it is an element in all the signs.
Some countries follow the US standard (MUTCD). In the linked page, search for "Height restriction ahead" to see how the sign look there. So, the layout should look like that. If you feel extra-cool, you could make extra forms even on variations, i.e. for Australia.

Meters vs Feet+Inch: So, both layouts need to have both input fields. These input fields can simply be made visible/invisible depending on the country or user's selection where both systems may be used.

westnordost · 2018-03-08T23:09:22Z

Should the query be improved to add the same functionality as the maxheight map by @mmd-osm does?

No, because that would potentially show very long stretches of road which would need to be split up. So, this would introduce possibly wrong data because the height restriction surely is not valid for the whole road/stretch but only for the area below the bridge.

mmd-osm · 2018-03-09T06:29:47Z

westnordost commented 7 hours ago
Should the query be improved to add the same functionality as the maxheight map by @mmd-osm does?
No, because that would potentially show very long stretches of road which would need to be split up. So, this would introduce possibly wrong data because the height restriction surely is not valid for the whole road/stretch but only for the area below the bridge.

BTW: Some queries in maxheight map depend on extensive post processing. Using the query results as-is will not suffice in all cases. This is especially true for queries with intersection checks.

Instead of adding data to the way, also existing nodes could be used for maxheight tags. This could avoid expensive splitting of roads.

westnordost · 2018-03-09T08:29:02Z

The estimate dialog could include the hint to take your own body height as a measure and estimate how many times you'd fit stacked on top of each other. Would that help you? As said, it should be an estimate only and clearly be tagged as such.

…

On 9 March 2018 09:09:36 CET, Mateusz Konieczny ***@***.***> wrote: matkoniecz commented on this pull request. > + + @OverRide public AbstractQuestAnswerFragment createForm() + { + return new AddMaxHeightForm(); + } + + @OverRide public void applyAnswerTo(Bundle answer, StringMapChangesBuilder changes) + { + boolean hasNoSign = answer.getBoolean(AddMaxHeightForm.NO_SIGN); + String maxheight = answer.getString(AddMaxHeightForm.MAX_HEIGHT); + if(hasNoSign) + { + /*TODO: maxheight=default or maxheight=no_sign? + according to https://taginfo.openstreetmap.org/keys/maxheight#values maxheight=no_sign is only used 14 times, + while maxheight=default is used about 10K times*/ + changes.add("maxheight", "default"); > What is the information gain here? I guess that in typical country it is mandatory to sign maxheight if it is below some value (I would expect it to be chosen so normal-sized vehicles can pass). So lack of sign indicates that normal vehicles can pass trough. Also, with this it is always possible to tag something, making this quest possible. > about an estimate of the height and tag the estimate then At least I am not really able to estimate height with any kind of accuracy that would make worth tagging it. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #960 (comment)

-- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

mmd-osm · 2018-03-09T08:33:27Z

ping //cc: @slhh

mmd-osm · 2018-03-09T15:45:08Z

app/src/main/java/de/westnordost/streetcomplete/quests/max_height/AddMaxHeight.java

+
+	/*the query does not exclude elements which are not accessible by the public,
+	because a maxheight sign will very probably be visible at the entrance or beginning*/
+	private static final String QUERY_RESTRICTIONS = "['maxheight'!~'.']['maxheight:physical'!~'.']";


You can use !tag instead of "tag"!~'.' here : e.g. [!maxheight], or [!"maxheight:physical"]

slhh · 2018-03-09T22:21:56Z

If there is no sign, should we tag it as maxheight=default (used about 10K times) or maxheight=no_sign as proposed by the wiki but only used 14 times according to taginfo...

If there is no sign, the user should be asked whether the physical height restricts any normal trafic including hgv. According to the answer we can tag:

No -> maxheight = default
Yes -> maxheight = below_default
Maybe (I can't estimate) -> maxheight = no_indications
I don't remember -> maxheight = no_sign

rugk · 2018-03-10T06:10:21Z

HGV?

mmd-osm · 2018-03-10T06:12:30Z

Hgv : Heavy goods vehicle (LKW in deutsch)

rugk · 2018-03-10T06:14:27Z

Ah, "truck".😌

ENT8R · 2018-03-10T06:19:03Z

I don't remember -> maxheight = no_sign

Why should a surveyor who sees the bridge/tunnel in "real life" should not remember if he is standing right in front of it...?

matkoniecz · 2018-03-10T08:48:29Z

"This height looks implausible" message hides value entered by user, maybe it should be somehow displayed in a message?

matkoniecz · 2018-03-10T08:52:26Z

I would recommend excluding vehicle=private|no ways.

I would recommend excluding also access=private|no ways.

matkoniecz · 2018-03-10T08:53:51Z

If there is no sign, should we tag it as maxheight=default (used about 10K times) or maxheight=no_sign as proposed by the wiki but only used 14 times according to taginfo...

I would use no_sign as it is more clear what is really mapped.

matkoniecz · 2018-03-10T08:54:32Z

should automatically a trailing .0 be added by SC?

I see no justification for that - why it should be done?

ENT8R · 2018-03-10T09:21:04Z

I would recommend excluding vehicle=private|no ways.
I would recommend excluding also access=private|no ways.

I would not, because this decreases the amount of solveable quest significantly. And very often the maxheight sign will be even displayed at the entrance of e.g. a parking

matkoniecz · 2018-03-10T09:33:26Z

I would not, because this decreases the amount of solveable quest significantly

Is it removing unwanted/pointless quests? If yes then I think that significant decrease makes it an even better idea. See cases like https://www.openstreetmap.org/way/518140477#map=19/50.07558/19.93155 or https://www.openstreetmap.org/way/295422615#map=19/50.05658/19.94075

What is the point of mapping maxheight restrictions for places inaccessible to general public? Owners of yard are not going to check maps/routing engines to check whatever they can access their own property.

ENT8R · 2018-03-10T09:37:35Z

Owners of yard are not going to check maps/routing engines to check whatever they can access their own property.

Well, that's true, but maybe there are some underground parkings which are not accessible by the general public but if you rent a parking space you can go in there... So there is not a single user but some more people who might be interested in using that data...

matkoniecz · 2018-03-10T09:41:15Z

So maybe keep

node['amenity'='parking_entrance']['parking'~'^(underground|multi-storey)$']" + QUERY_RESTRICTIONS + ";" +

unchanged and add access filters for

way['highway'~'^(" + ROADS + ")$']['tunnel'~'^(yes|building_passage)$']" + QUERY_RESTRICTIONS + ";" +

?

This should handle both cases.

ENT8R · 2018-03-10T09:45:10Z

Good idea! I will do this.

ENT8R · 2018-03-10T10:22:16Z

"This height looks implausible" message hides value entered by user, maybe it should be somehow displayed in a message?

Don't think that this is necessary... The user will either remember the value he entered some moments ago or can simply press Cancel/I will check...

… make DB actions involving single quests/elements synchronous again to simplify things

…n't limit at level 17.5) (streetcomplete#965)

westnordost · 2018-08-12T12:54:23Z

whoops, did a rebase-merge instead of a normal merge. In case there will be problems when merging back to master, I will fix them.

westnordost · 2018-08-12T14:19:28Z

I tested this a bit, found this issue:

If I change the language of my phone to German, it does not let me input 5,5 m.

westnordost · 2018-08-12T14:22:24Z

Hmm, regarding the Iceland-thing, it is weird. The LayoutInflater has the correct mcc-infused resources and selects the correct layout to inflate. Furthermore, it passes the same context to views it creates. For testing, I created a new view and included it in the layout.

public class TestView extends View
{
	public TestView(Context context)
	{
		super(context);
		setBackgroundResource(R.drawable.background_maxheight_sign);
	}

	public TestView(Context context,
					@Nullable AttributeSet attrs)
	{
		super(context, attrs);
		setBackgroundResource(R.drawable.background_maxheight_sign);
	}

	public TestView(Context context, @Nullable AttributeSet attrs, int defStyleAttr)
	{
		super(context, attrs, defStyleAttr);
		setBackgroundResource(R.drawable.background_maxheight_sign);
	}

	@TargetApi(Build.VERSION_CODES.LOLLIPOP) public TestView(Context context,
															 @Nullable AttributeSet attrs, int defStyleAttr, int defStyleRes)
	{
		super(context, attrs, defStyleAttr, defStyleRes);
		setBackgroundResource(R.drawable.background_maxheight_sign);
	}
}

Result:

So I am still in the dark as to why it does not work for that other view.

westnordost · 2018-08-12T16:13:56Z

Okay I found it. It is not easily solvable, as Google did not anticipate I guess that one would like to work with modified Resources:
For reading the attributes during layout inflation, not directly the context's Resources are used, but the Context's Theme (getTheme). My ContextWrapper implementation in AbstractQuestAnswerFragment only overrides getResources(). While getTheme can also be overridden, the method's return type Resources.Theme is final, so I cannot create something like a ThemeWrapper that instead uses the overridden resources.
This means that resources specified in XML (backgrounds, strings, images, ...) will never be resolved to the current-country resources.

The workaround then is to manually set the resources again programmatically after inflation.

westnordost · 2018-08-12T17:08:53Z

Also, in regards to the earlier problem I noticed: When you write a dot instead of a comma on a non-English locale, the app crashes

Caused by: java.text.ParseException: Unparseable number: "14.5" (at offset 4)
                      at java.text.NumberFormat.parse(NumberFormat.java:557)
                      at de.westnordost.streetcomplete.quests.max_height.AddMaxHeightForm.getHeightFromInput(AddMaxHeightForm.java:192)

Also, a feet has 12 inch. That means, that you should not be allowed to enter 12 inch, but at most 11.

* make signs of height quest look-alike with speed quest and the other way round * adapt wording a little * add maxheight sign source svg

goldfndr · 2018-08-12T20:16:47Z

Although the measure_height_help image is gone from this PR, I have some feedback on it for when it next appears.

The object should have a flat top and bottom, to encourage accuracy.
The person and object should be at the same level.
A flat elevation line should extend from the object to the person, to emphasize that a slope gives less accuracy.

# Conflicts: # app/src/main/res/layout/activity_main.xml

westnordost · 2018-08-15T18:24:54Z

Looks like this was an Android bug until Android O. Since this was only fixed then, we still need to workaround this.

…o always be the "." for EditTexts with inputType "numberDecimal", independent of Locale. See https://issuetracker.google.com/issues/36907764

…t be confused whether he should use the one as displayed on the sign or in his phone's locale

westnordost · 2018-08-15T19:23:15Z

Completed final tests

ENT8R · 2018-08-15T19:35:20Z

Thank you very much for finishing this! 👍 🎉 I was really busy in the last days...

westnordost · 2018-08-15T19:47:40Z

You're welcome! But also, thank you of course for preparing this PR :-)

ENT8R added 3 commits March 8, 2018 18:01

Add new quest to determine the maximum height of some elements

02f38ac

Remove unnecessary import statement

7ff5c4a

Remove now unnecessary drawable files

59b4374

goldfndr reviewed Mar 8, 2018

View reviewed changes

westnordost requested changes Mar 8, 2018

View reviewed changes

goldfndr reviewed Mar 8, 2018

View reviewed changes

mmd-osm reviewed Mar 9, 2018

View reviewed changes

westnordost added 10 commits August 12, 2018 14:52

refactor to clean VisibleQuestListener to have only this one purpose,…

143ef5a

… make DB actions involving single quests/elements synchronous again to simplify things

add quest plop animation on solving

63ba0d0

fix error on downloading oneway quest for areas

ccbc2b7

don't show upload-button in autosync-mode

1f1f650

progress bar on upload button

8ceeec2

also add plop-animation for create-notes.

b29d5ec

show blinking cursor in speed limit input and housenumber input sign

5221612

when exiting quest details, always zoom back to the previous zoom (do…

220ca4c

…n't limit at level 17.5) (streetcomplete#965)

fix tests

5a31fd4

request focus on input field when layout is set

84042c4

* fix sign is not yellow in Nordic countries

cc19ad8

* make signs of height quest look-alike with speed quest and the other way round * adapt wording a little * add maxheight sign source svg

westnordost added 3 commits August 15, 2018 20:14

remove outer (double) black line from signs to reduce noise

e0ef7fc

Merge branch 'master' into maxheight

48c0fcd

# Conflicts: # app/src/main/res/layout/activity_main.xml

remove outer (double) black line from signs to reduce noise

91e87c1

westnordost added 2 commits August 15, 2018 20:55

Workaround for an Android bug that it assumes the decimal separator t…

a9d9f7d

…o always be the "." for EditTexts with inputType "numberDecimal", independent of Locale. See https://issuetracker.google.com/issues/36907764

actually, let's not care about which separator the user uses, he migh…

0eea8c8

…t be confused whether he should use the one as displayed on the sign or in his phone's locale

westnordost merged commit 551f015 into streetcomplete:master Aug 15, 2018

ENT8R deleted the maxheight branch August 15, 2018 19:35

matkoniecz mentioned this pull request Sep 14, 2019

No max height for private parkings #1560

Closed

westnordost mentioned this pull request Jan 31, 2024

There is no default maxheight in Israel #5458

Closed

Add new quest to determine the maxheight #960

Add new quest to determine the maxheight #960

Conversation

ENT8R commented Mar 8, 2018 • edited Loading

matkoniecz commented Mar 8, 2018

westnordost commented Mar 8, 2018

Choose a reason for hiding this comment

goldfndr Mar 8, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mmd-osm Mar 9, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

This comment was marked as resolved.

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ENT8R Mar 10, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

westnordost commented Mar 8, 2018

westnordost commented Mar 8, 2018

mmd-osm commented Mar 9, 2018 • edited Loading

westnordost commented Mar 9, 2018 via email

mmd-osm commented Mar 9, 2018

Choose a reason for hiding this comment

slhh commented Mar 9, 2018

rugk commented Mar 10, 2018

mmd-osm commented Mar 10, 2018

rugk commented Mar 10, 2018

ENT8R commented Mar 10, 2018 • edited Loading

matkoniecz commented Mar 10, 2018

matkoniecz commented Mar 10, 2018 • edited Loading

matkoniecz commented Mar 10, 2018

matkoniecz commented Mar 10, 2018

ENT8R commented Mar 10, 2018

matkoniecz commented Mar 10, 2018

ENT8R commented Mar 10, 2018

matkoniecz commented Mar 10, 2018 • edited Loading

ENT8R commented Mar 10, 2018

ENT8R commented Mar 10, 2018

westnordost commented Aug 12, 2018

westnordost commented Aug 12, 2018

westnordost commented Aug 12, 2018

westnordost commented Aug 12, 2018

westnordost commented Aug 12, 2018 • edited Loading

goldfndr commented Aug 12, 2018

westnordost commented Aug 15, 2018

westnordost commented Aug 15, 2018

ENT8R commented Aug 15, 2018

westnordost commented Aug 15, 2018

ENT8R commented Mar 8, 2018 •

edited

Loading

goldfndr Mar 8, 2018 •

edited

Loading

mmd-osm Mar 9, 2018 •

edited

Loading

ENT8R Mar 10, 2018 •

edited

Loading

mmd-osm commented Mar 9, 2018 •

edited

Loading

ENT8R commented Mar 10, 2018 •

edited

Loading

matkoniecz commented Mar 10, 2018 •

edited

Loading

matkoniecz commented Mar 10, 2018 •

edited

Loading

westnordost commented Aug 12, 2018 •

edited

Loading