-
-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changesets refactor #1329
Changesets refactor #1329
Conversation
# Conflicts: # app/build.gradle
|
app/src/main/java/de/westnordost/streetcomplete/data/osm/split/SplitWayUpload.kt
Outdated
Show resolved
Hide resolved
app/src/main/java/de/westnordost/streetcomplete/data/osm/split/SplitWayUpload.kt
Outdated
Show resolved
Hide resolved
app/src/main/java/de/westnordost/streetcomplete/data/osm/split/SplitWayAtPosition.kt
Outdated
Show resolved
Hide resolved
One thing that seems to be missing - on splitting some closed ways one needs to create a multipolygon (on splitting say Maybe it can be assumed that it will not happen in StreetComplete and is not worth implementing but may be worth noting it in comments that it is supposed to not happen. |
Multipolygon? Not sure what you mean. A closed way is just a closed way, if you split it up, you get two unclosed ways. That is the behavior of JOSM. |
Yes, but
is incorrect (water area will disappear), and following is necessary:
|
Probably not a multipolygon but two separated closed ways. But anyway, splitting a way is quite a different operation from splitting an area. The way is just 1-dimensional, so it can be split in a point. The area is 2-dimensional, so the split itself is a line, or a polyline. In OSM, there exists no data structure for an area. I wonder, does JOSM have such a function, splitting a closed way (=area) along a (poly)line? I can imagine use cases in StreetComplete where such a function would be helpful, for example if one wants to split up a building, a farmland or so. I'll keep this in mind, but for now, this won't be part of the implementation. A simple split of a way is already complicated enough, also UI wise. Imagine the user would need to draw a polyline (on a smartphone screen) to split an area with. |
I'll probably be back from my "cave" this weekend, pushing a huge refactor of the whole upload system:
|
OK this sounds like a bug. Will investigate. I also received feedback in the German forum, so probably a beta-Release needs to be postponed (it was initially planned to be this Wednesday).
Yes, they might be. I was hoping that the dialog shown before the split-way screen explains this good enough. Do you or anyone else have a suggestion how to make the wording clearer so that the user is not surprised why he can't answer the question anymore (until next upload)?
Yes, this is the case. @HolgerJeromin Are you interested to test the cases I wrote about above from A-Z(, or some of them)? |
Ok fixed |
# Conflicts: # app/src/main/res/values/strings.xml # app/src/test/java/de/westnordost/streetcomplete/data/osm/download/OsmQuestDownloadTest.java
<string name="quest_generic_answer_differs_along_the_way">"Differs along the way…"</string> | ||
<string name="quest_split_way_description">If it differs along the way, the first step is to split up the way. After that, the quest can be answered for each split part separately.\nNote that the quests for the split parts may appear mach later.\nSplit it now?</string> | ||
<string name="quest_split_way_tutorial">Tap on the way to split it at the point(s) where the answer differs. Try to be as precise as possible, you can zoom in as usual.</string> | ||
<string name="quest_split_way_too_imprecise">"Please zoom in further"</string> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This appears also at the maximum possible zoom.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm. The message appears if you tapped multiple nodes at once with your finger. If the nodes are absurdedly close to each other, then it wouldn't be possible to split up the way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd love to just set the maximum zoom further up. But The default maximum zoom in tangram-es is 20.5 and it cannot be turned up further (and only starting at the new tangram-es version that we do not use).
At zoom 20.5, the diameter of the tap of the finger is about 3 meters in our latitude and about 5 on the equator. So, that is about still 4 zoom levels away from achieving the OSM 7-decimals-precision.
So the best choice here is to instead of requiring to further zoom in at already that high of a zoom level, just choose the node that is closest to the center of the tap position.
Will work on it. Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implemented it. Would you mind testing it again at the position where you discovered it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Co-Authored-By: Mateusz Konieczny <[email protected]>
# Conflicts: # app/src/main/res/values/strings.xml
While testing, I discovered two more problems:
So, the release will be postponed further. |
Is the second error manifesting as |
Yes |
The first dialog is forgotten. Another Toast after splitting "The quest you selected will be available after upload" would have helped me. |
Solution still WIP... |
Tests listed here complete. Further tests done:
|
5 steps: