Skip to content
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

Android application not recording tree addresses for mapped trees #285

Open
hadleystein1 opened this issue Oct 28, 2016 · 10 comments
Open

Comments

@hadleystein1
Copy link

Customer (Leaf Limb Consulting) has been mapping thousands of trees in the field. All trees on their map (https://www.opentreemap.org/durhamtestmap/map/) have been individually over the past few weeks using our Android application. The addresses for certain trees are not populating. Over 150 trees on their map do not contain addresses. Customer did not detect any pattern to when address were populating versus when addresses were not populating. I have attached the most recent export from their map.

In addition to fixing the issue, customer wants to know is there a way for addresses to retroactively populate so all tree records on the map contain address information?

LeafLimbConsulting_10_28.xlsx

@RickMohr
Copy link

RickMohr commented Oct 28, 2016

OTM does not support retroactive geocoding. Currently we'd have to do it for them as a geocoding project.

A cheap OTM enhancement would be for "Quick Edit" to look up the address if it's missing. They'd have to select each of the 150 trees but that would go pretty fast.

@hadleystein1
Copy link
Author

To clarify:

  • The application is supposed to populate the address field?
  • As for finding the addresses of the already-mapped trees without address information that is not possible as the system is currently designed and/or without allocating additional time/resources to those specific records?

@maurizi
Copy link
Contributor

maurizi commented Oct 28, 2016

The application is supposed to populate the address field?

The Android app does not currently do this, but the website does and according to @RickMohr the iOS app does as well. This is wrong. The Android app does attempt to reverse geocode when adding a tree:

newPlot.setAddressFromGeocoder(new Geocoder(getActivity(), Locale.getDefault()));

As for finding the addresses of the already-mapped trees without address information that is not possible as the system is currently designed and/or without allocating additional time/resources to those specific records?

Correct

@hadleystein1
Copy link
Author

hadleystein1 commented Oct 28, 2016

Client said: "We have been using Androids the entire time. Like I said, it only happened on two phones for one day during the three weeks." Is this possible?

@jmorrison1847 does the Texas A&M have an address tool for getting addresses from Lat and Long information?

@jmorrison1847
Copy link

@maurizi
Copy link
Contributor

maurizi commented Oct 28, 2016

I was wrong, the Android app does reverse geocode to fill in the address fields when adding a tree. I don't know why some trees do not have the address information filled in. I would assume it is because reverse geocoding failed to find an address (which usually happens if the point is not near any address).

@jmorrison1847
Copy link

^if that's the case, I'm not sure that there is a clear solution--Google's geocoding API is about as good as it gets.

@RickMohr
Copy link

We use ESRI's geocoder.

@maurizi
Copy link
Contributor

maurizi commented Oct 28, 2016

@RickMohr Android uses the Google geocoder (because it is conveniently built-in)

@RickMohr
Copy link

Before assuming it's a problem with the geocoder I think we should try geocoding the lat/long for a few of the no-address trees.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants