This article explains the GPS Location block that can be added as a block to design an app.
Click on the block and start editing on the panel that appears on the right side.
This is what appears as the name of the GPS block to the end-user.
This is the text that goes below the GPS block to help the user.
Tick this option if you want the user to compulsorily input the GPS location.
Click on the Advanced tab in the right panel to view more configuration options for the GPS block.
By default, this option is turned on. If kept on, the GPS Location will be auto-filled when the user loads the Clappia App. This captures fixed GPS location of the user at the time of submission.
By default, GPS location editing is not allowed to be changed by the user. If you want the users to modify their current location, enable this option. This captures dynamic GPS location of the user, i.e., the GPS Location block takes the location that the user sets.
Note: If your app is accessed through a public link (Link Sharing mode), users will not be able to move the map pin unless you give your own Google Maps API key. Once the key is provided and "Allow user to manually change location" is enabled, users can move the pin in this mode.
Use this option if you want to see location captured displayed on a map.
By default, the GPS Location block captures and displays the user's coordinates (latitude and longitude). If you want to see the actual address of the captured location (such as street or locality name), enable the "Fetch address from configured location" option.
The variable with #address in the name can be used to display the actual address in your app.
To display the address in the app, use a Calculations & Logic block. In the formula section, type @ followed by the GPS block's field name and select the variable ending with #address.
Note: The address variable will only be available if the ‘Fetch Address from Configured Location’ option is enabled. If the option is disabled and the address variable is used in the ‘Calculations & logic’ block, the value will remain blank.
Each GPS Location block automatically creates two variables:
To display the actual address, always use the #address variable. If the 'fetch address from configured location' option is not enabled and you try to use @gps_location#address, it will return a blank value.
Type @ followed by the field name of the GPS Location block to find the field's variables.
The regular variable without #address will always return GPS coordinates (latitude and longitude).
To display the address captured through the GPS Location block:
This will allow you to display the actual address in App Home once a submission is made. If the #address variable is not available, double-check that the "Fetch address from configured location" option is enabled in the GPS location block.
In Link Sharing mode (public access without login), address fetching will not work by default. To use the #address variable in this mode, you must provide your own Google Maps API key.
To enter your API key:
To get your own Google Maps API Key, you will need to:
Note: Google may charge for use of these services based on their pricing policies.
Once the API key is configured and "Fetch address from configured location" is enabled in the GPS block, address data will be available even in Link Sharing mode.
In login-based access (Clappia mobile app or website), you do not need to provide an API key. Enabling "Fetch address from configured location" is sufficient to retrieve the address. However, you may still enter your own key under Third Party Integrations if desired.
Use this option to allow users to submit only when they are at one of the designated locations. You can specify a list of designated locations and a radius to define the Geofencing boundary.
A list of locations defined in the form of "Latitude,Longitude" separated by a new line. It can also contain other GPS variables from the app.
The maximum aerial distance where the user can be present from one the designated locations.
Use this option to show or hide the field under specific conditions. It accepts the standard Clappia formulae, similar to conditional sections or in the 'Calculations & Logic' block.
This option appears once a condition is set in the Display this field if option. Enable this setting if you want the field's value to be retained even when the field is hidden. This is useful for preserving user input in cases where the field may temporarily disappear based on conditions.
Example: If the field is hidden based on user selection but you still need to keep the entered value for future reference or calculations, enable this option to ensure the data is retained.
This option is enabled by default. When active, end users can edit the GPS location after creating a submission. Disable this option if you want the initial location to remain unchangeable once submitted.
Desktop View: Set the width of the GPS Location block in the desktop view. Options are 100%, 75%, 50%, or 25%.
Mobile View: Set the width of the GPS Location block in the mobile view. Options are 100% or 50%.
No, this is a privacy issue for the end-user. That's why we don't provide this feature. Also, continuous GPS polling impacts battery usage heavily.
Yes, you can restrict form submissions to a specific location using the 'Geofencing' feature of the GPS Location Block. It allows you to define geographical boundaries within which the form can be submitted. Find out more about setting up this feature in the Help Guide article on Geofenced Location-Based Submission.
Yes, you will be able to capture GPS locations even without an internet connection. Once the connectivity is back, the data gets synced automatically and you will be able to see the location in your Submissions tab.
L374, 1st Floor, 5th Main Rd, Sector 6, HSR Layout, Bengaluru, Karnataka 560102, India
3500 S DuPont Hwy, Dover,
Kent 19901, Delaware, USA
3500 S DuPont Hwy, Dover,
Kent 19901, Delaware, USA
L374, 1st Floor, 5th Main Rd, Sector 6, HSR Layout, Bengaluru, Karnataka 560102, India