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.

Sign up for GitHub

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

Jump to bottom

OSM Layer not properly managed #117

Closed
Aleglise opened this issue Aug 2, 2016 · 5 comments
Closed

OSM Layer not properly managed #117

Aleglise opened this issue Aug 2, 2016 · 5 comments
Assignees
@Aleglise
Labels
bug
Milestone
Medium Priority

Comments

@Aleglise
Copy link
Collaborator

Aleglise commented Aug 2, 2016

image
@Aleglise Aleglise added the bug label Aug 2, 2016
@Aleglise Aleglise added this to the Medium Priority milestone Aug 2, 2016
@abyot abyot assigned Aleglise and unassigned abyot Aug 7, 2016
@abyot
Copy link
Collaborator

abyot commented Aug 7, 2016

Oh ya, this is because of the latest changes in Google GIS API policy... This is a common issue we just faced in across DHIS2. The GIS team is currently trying to figure out a problem. They have said we do not have this problem in 2.24. So upgrading could be one solution.

@Aleglise
Copy link
Collaborator Author

Aleglise commented Aug 7, 2016

Regarding the data capture app, upgrading could also be one solution: dhis2/dhis2-android-datacapture#23

@Aleglise Aleglise assigned abyot and unassigned Aleglise Aug 7, 2016
@Aleglise
Copy link
Collaborator Author

Aleglise commented Aug 7, 2016

Can you please assess the risks of a 2.24 upgrade?

@abyot abyot assigned Aleglise and unassigned abyot Aug 7, 2016
@abyot
Copy link
Collaborator

abyot commented Aug 7, 2016

Yes, right now trying to upgrade. I was kind of pushing task, if not critically needed to avoid it all together. But seems we need it more and more. The thing is I just have to synchronize many things :(

@Aleglise
Copy link
Collaborator Author

This DHIS2 version 2.23-SNAPSHOT does not properly manage the new OSM policy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Aleglise Aleglise

Labels
bug
Projects
None yet
Milestone
Medium Priority
Development

No branches or pull requests
2 participants
@abyot @Aleglise