At the Micropub Pop-up Session 2020, it was decided to table this issue as there was no clear interest one way or the other.

Trying to elaborate on the point of this. @swentel added this so Indigenous could submit a checkin as a form-encoded post.

• GEO URIs Scheme(https://tools.ietf.org/rfc/rfc5870) - technically extra parameters require registration but unrecognized parameters can be ignored.
• Android(https://developers.google.com/maps/documentation/urls/android-intents) adds z as a parameter for zoom and q as a parameter for query.
  geo:37.786971,-122.399677,50;u=35;h=card;name=Home;url=https://example.com

In my WordPress code that consumes it, I convert this into an object using the following logic.

1. Convert latitude, longitude, and altitude(if present as the 3rd parameter of the coordinates.) into mf2 parameters.
2. Convert u into an accuracy parameter as mf2 has no such concept.
3. If there is an h parameter, assume this is an h parameter, same as Micropub.
4. Convert all other parameters to properties and create a mf2 json object.
5. If no h property, if it only has the coordinates, assume h-geo. Otherwise,, assume h-card.