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

Hook up geoservice client in gedbrowser #96

Closed
dickschoeller opened this issue Jan 8, 2017 · 0 comments
Closed

Hook up geoservice client in gedbrowser #96

dickschoeller opened this issue Jan 8, 2017 · 0 comments
Assignees
Milestone

Comments

@dickschoeller
Copy link
Owner

  1. Gather places from person
  2. Request geocode for each place
  3. Log the result (info first, debug later)
  4. Display in textual form on page
@dickschoeller dickschoeller added this to the version-1.1 milestone Jan 8, 2017
dickschoeller added a commit that referenced this issue Jan 14, 2017
* Create a standalone application that is a geoservice client
* Rearrange stuff so that the backup data types are now what is presented in the service
* Rename types to be more reasonable for current usage
dickschoeller added a commit that referenced this issue Jan 14, 2017
…nt-in-gedbrowser

Issue #96 - hook up geoservice client in gedbrowser
dickschoeller added a commit that referenced this issue Jan 14, 2017
* Fix the naming of a test class
dickschoeller added a commit that referenced this issue Jan 15, 2017
All of the geo information is now in GeoJSON forms. The internal geometry
description is now a Point (location) and 2 Features (bounds and viewport).

The next step will be to make it be completely a Feature Collection. That
will require turning the Point into a Feature with the Point and the
location type (as a property).
dickschoeller added a commit that referenced this issue Jan 17, 2017
All of the response data is now in the GeoJSON. However, I can't
deserialize the Google data types if they are in a Feature.properties.
So, I have that data redundantly in the response. For current semantics
it's in the wrapper.

Next steps is to make componentize the client. Use the application just
to test the component. Eventually use that component in GedBrowser.
dickschoeller added a commit that referenced this issue Jan 17, 2017
…nt-in-gedbrowser

Issue #96 - Backed off a little on the GeoJSON
dickschoeller added a commit that referenced this issue Jan 17, 2017
* This makes the client a consumable object
* The geoservice client application is more robust for testing
* I am holding back the actual use of the client in the gebrowser
dickschoeller added a commit that referenced this issue Jan 17, 2017
…nt-in-gedbrowser

Issue #96 - the geoservice can now be used by gedbrowser behaviors
dickschoeller added a commit that referenced this issue Jan 18, 2017
* Clean up some warnings in tests
* Make gedbrowser call geoservice for persons
* Don't do family places yet. That can be a new issue.
* Don't connect to the UI yet. That already is an issue.
dickschoeller added a commit that referenced this issue Jan 18, 2017
…nt-in-gedbrowser

Issue #96 hook up geoservice client in gedbrowser
@dickschoeller dickschoeller self-assigned this Jan 20, 2017
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

1 participant