Is your feature request related to a problem? Please describe.
Suggestion: GPS coordinate fetch as "input type" (variable)
This should happen automatically, so you shouldn't need to confirm or anything, just that it will include the GPS coordinates in the request.
Describe the solution you'd like
A new option for "Variable Type":
GPS Coordinate.
Input options should be "Wait for fix before execution" which will make it forcefully wait until it gets a valid fix before it submits the HTTP shortcut.
And if "Wait for fix" is checked, a box for "timeout in seconds" should become enabled, so you can decide to submit "what it have" (which could be inaccurate coordinates or no coordinates at all).
Format of variable should be:
xx.xxxxxxxx,yy.yyyyyyyy,z
where x is latitutde, y is longitude, and z is a integer which is 0 for no fix (coordinates will then be 00.00000000), 1 for partial fix (inaccurate) and 2 for full/complete fix.
Is your feature request related to a problem? Please describe. Suggestion: GPS coordinate fetch as "input type" (variable) This should happen automatically, so you shouldn't need to confirm or anything, just that it will include the GPS coordinates in the request.
Describe the solution you'd like A new option for "Variable Type": GPS Coordinate. Input options should be "Wait for fix before execution" which will make it forcefully wait until it gets a valid fix before it submits the HTTP shortcut. And if "Wait for fix" is checked, a box for "timeout in seconds" should become enabled, so you can decide to submit "what it have" (which could be inaccurate coordinates or no coordinates at all).
Format of variable should be: xx.xxxxxxxx,yy.yyyyyyyy,z
where x is latitutde, y is longitude, and z is a integer which is 0 for no fix (coordinates will then be 00.00000000), 1 for partial fix (inaccurate) and 2 for full/complete fix.