It seems very silly that elevation is a directly key-able data point in the UI during on-boarding or adjustable afterwards while lat & long is not.
-Yeah I know you can move your pin around on the Openstreets map…which is probably fine for users in urban environments or at the very least less inaccurate. But if you live out in the sticks, Openstreets is a just a sea of black or white depending on the UI theme you went with. Consequently, getting your location dialed in accurately by moving the pin around is pretty, well…mehhhh.
-Yeah I know you can add it manually in the config file…but why mess with a yaml file for lat & long but not elevation? I can SEE MY HOUSE in Google maps and get lat & long to like 10 decimal places. It’s easy to find, easy to copy & paste somewhere - it should be just as easy for the end user to enter. Especially for such a baseline piece of info that so much relies on…weather…sun…zone…etc.
That’s my 2 cents.