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

Add Location Widget (a.k.a GPS picker) to FHIR Core #880

Closed
f-odhiambo opened this issue Dec 16, 2021 · 1 comment · Fixed by #3046
Closed

Add Location Widget (a.k.a GPS picker) to FHIR Core #880

f-odhiambo opened this issue Dec 16, 2021 · 1 comment · Fixed by #3046

Comments

@f-odhiambo
Copy link
Contributor

f-odhiambo commented Dec 16, 2021

What's the difference between a location widget and a Geo-widget?
From a tech perspective, they are the same thing. They pick location GPS data but from a UI perspective, they are different. Geo Widget will use the map to pick the location data. Done is FHIR Core #1536

Location widget can have 2 variants

  1. Show a drop-down or location tree. This helps you select the locations already saved on the app. It mostly visualizes the location hierarchy on a form.
  2. This is an input field on a form that will pick the GPS coordinates and fill in LAT & LONG input fields in the form.|

Point 2 can be a simple button that gets the (Lat, Long) when clicked or be what Ona Data did here

Opened this ticket to track the SDK issue - google/android-fhir#800

@f-odhiambo f-odhiambo changed the title Add location widget Add Location Widget 2 (a.k.a GPS picker) to FHIR Core Nov 24, 2022
@pld pld removed the Foundation label Jun 14, 2023
@dubdabasoduba dubdabasoduba changed the title Add Location Widget 2 (a.k.a GPS picker) to FHIR Core Add Location Widget (a.k.a GPS picker) to FHIR Core Nov 6, 2023
@ageryck
Copy link
Contributor

ageryck commented Feb 7, 2024

This is fixed by this #3046

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

Successfully merging a pull request may close this issue.

3 participants