-
Notifications
You must be signed in to change notification settings - Fork 1.3k
"Search this area" to launch a nearby search around that location #591
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
Comments
We would be glad if we can take this issue. |
I consider this enhancement as a good one. However, its scope needs to be defined (and discussed) better before implementation.
After adding #252 (This can be discussed under #252 )
|
I agree, the scope of this is very vague at the moment. |
To answer your questions:
In fact even implementing this enhancement in and of itself could potentially increase the risk of vandalism via direct uploads IMO, since someone would not even need to be in a location (or to spoof his location) in order to upload a picture for that Nearby item. When P18 edits are implemented, the consequences of this could be even more severe, as the Wikidata items will actually be edited and removed from Nearby. That being said, maybe I'm being a bit too catastrophic, lol. |
I was thinking for my DSLR camera uploads. Since I never took photos with my android device, I am never able to upload a nearby place while I am there. But I share your vandalism concern. |
Edit: Yeah, I suppose it's possible that some users may want to take all their photos and then upload them to the various Nearby items later. So I can see the benefits in allowing that. Just not sure if it's worth the tradeoff? Edit 2: A possible solution: We check the geotagged location of the image and allow the direct upload to go through if the location is roughly close to the location of the Nearby item? Thoughts on this? |
I want to second that. I upload most of my pictures on the train back, or when I am waiting for a friend for instance.
|
We'd like to focus on 1. and maybe 2. because we're limited in scope and time due to the fact we're implementing this feature in the context of a course at our university. So these two subissues and the correspondent tests totally fullfill the limited scope and time of our course |
Do you think it's possible to implement 1. and 2. isolated and irrespective of 3. ? |
@thealexguy Yes feel free to implement only 1 and 2 :-) |
@thealexguy Sure, please feel free. :) |
Just one more question: |
There is no default developer login unfortunately.
|
I've pulled the latest version and used my normal login username and password. I registered again and now it works :) |
@thealexguy Happy to hear that. :) You can always check what build variant you are using (if you are using Android Studio, it should be on the left side of the screen). The build variants that include the term "beta" (e.g. betaDebug) will upload images to the beta server (instead of the real Commons server) and AFAIK that requires a separate login/registration from the actual Commons one. |
Everything of the following is open for discussion :) We discussed and have some questions so far:
We also like to (and have to due to the course rules) propose a solution approach: Function "add custom location via long press on map":1. Add Marker to MapView and show NearbyPlaces as markers (in the
|
In addition to the tasks above we want (and have) to write one (or more) test cases that captures the intended behavior of the feature. Well as you can read it here, Android doesn’t contain any actual code when running unit tests. “This is to make sure your unit tests only test your code and do not depend on any particular behaviour of the Android platform”. A possible way would be to mock some classes and methods but this wouldn’t make much sense because the feature is per se an interaction of Android classes (View) and the Mapbox library (MapView and MapboxMap). So, do you have any suggestions how we could write a test case for this feature? |
Hi @oe-bayram and @thealexguy - apologies for the slow response, we have been pretty busy recently, 2 of our devs were travelling last weekend and we are gearing up for a release this week. Do you two have any strict deadlines for your project? We will try to answer you within the week if possible. (Edited to fix my wonky temporal perception) |
Hi @misaochan - the goal of our project is more learning the way how to contribute to an opensource software than perfectly implementing a feature. So we have a deadline but it does not have to be strictly adhered to. Of Course a fast reply would be nice. Our project leader focuses more on tests, so we would be glad if you reply to this topic as well. So we could implement them as well. |
Hi @thealexguy , trying to go through your questions now, let me know if I miss anything.
I haven't had time to take a close look at the Mapbox documentation yet, but unless there is a good reason to do otherwise, I would use our own implementation, as there is a possibility that we may not continue to use Mapbox in the future.
Yes, that should be OK.
The proposed approach sounds good to me. What do you think @nicolas-raoul @neslihanturan @maskaravivek ?
I believe this would make sense for the map, but not the list?
Does looking at NearbyAdapterFactoryTest.java help? Unfortunately, I am not entirely sure how to answer this question, hopefully someone else can. :) |
Sounds good! Manual tests are probably enough, I would say, as it is primarily a UI feature. Good luck :-) |
Feature DescriptionId: #591 Functionality:This Feature is an addition to the current feature of showing nearby Places around the current location of the user. Now it’s possible to add a custom location anywhere on the map via a long press. After a few seconds of loading the nearby places around the custom location are shown on the map. API:Basically we catch a long press event on the MapFragment and call the new static method Refactoring and new methods:We refactored |
Dear Team, |
@oe-bayram You could fork the repo and push changes to your branch, and submit a PR then. :) |
Due to the last version update our implementation for this feature isn't compatible anymore. Well the current version has some location issues in the nearby activity (#983). And this is being fixed with this merge. Anyway I have tried to implement the feature with this merge and after a bit change in the nearby activity it works again. But now after a long click, the last position is shown just for a half second and then the long clicked position is shown with its nearby places (with a short white screen inbetween). Our questions: When will this be merged and what could be the reason for this short display of the last shown position? The implementation is on this forked repository. |
Hi @oe-bayram , sorry, we have been quite busy with solving the issues blocking our current release. Testing and merging PRs should hopefully resume next week after we clear the blockers, and hopefully we can try to look into the problems you are experiencing then as well, if still needed. |
When I go nearby-hunting, I only take pictures and walk/cycle. |
I am even more old-fashion @nicolas-raoul , writing down places to a paper since I took photos with DSLR, not phone. So I also think this feature is quite needed. |
I agree. Sorry we didn't follow up on this, @oe-bayram . :/ Are you guys still interested in working on this? |
I think we probably want to bump this up a bit, possibly include it in our next grant (WMCZ or PG). After using our direct uploads quite a bit, I agree completely with @nicolas-raoul that this feature is needed. Some thoughts:
|
"Search this area" is better indeed, and it is found in apps like AirBNB Yes, totally, making "adding a no-GPS picture via the nearby map at a remote location" a feature that can be "unlocked" (see #85 (comment)) is a great idea. Until "reputation" is implemented, though, I think we should not worry too much about vandals, who have much more accessible targets. |
Good point. Yeah, I think we can just use a warning until we implement that. :) |
Had a conversation with User:Jim Henderson at https://commons.wikimedia.org/wiki/Commons_talk:Mobile_app#Wish_list , and a concern of his (that I agree with) is that the map frequently auto-zooms out to display an unusable dense cluster of pins, which requires the user to keep zooming back in, especially if they are switching between apps. When we implement this feature, we should ensure that we save the state of the map (the area that the user chose to search) when onPause or onStop. We should only zoom out to the default view onDestroy, IMO. |
"the map frequently auto-zooms out to display an unusable dense cluster of pins" <- very true. |
I figured I would include it in this issue because the zoom conditions will inherently have to change in the development of this feature - and this feature is due to start being developed within the next 1-2 weeks. Do you think it still warrants a separate issue? |
This problem happens as soon as the Nearby screen appears, before even zooming or moving the map, right? |
@nicolas-raoul Good point. I will create an issue. |
I often plan my itinerary and decide where to go, before actually being there.
On the Nearby map, it would be great if I could long-press a location to launch a nearby search around there.
The text was updated successfully, but these errors were encountered: