Distance constraint add on frontend

[NSUWAL123]

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation
• 🧑‍💻 Refactor
• ✅ Test
• 🤖 Build or CI
• ❓ Other (please specify)

Related Issue

• Related to Addition of distance constraints between user's geolocation and feature selected for mapping #1985

Describe this PR

Validate the distance between user location and entity if the distance constraint is true.
If the distance constant is set to true, the user must enable their device location & must be within the distance constraint set.

Screenshots

1. Geolocation must be enabled if the distance constant set
   

2. Show a message if the user now within the range
   

[spwoodcock]

I updated the logic to be:

// Check if drawn geometry is within set distance constraints from user
const isDistanceConstaintValid = (): boolean => {
const coordTo = entitiesStore.selectedEntityCoordinate?.coordinate;
const coordFrom = entitiesStore.userLocationCoord;

// Geolocation not enabled, warn user
if (!coordFrom) {
	alertStore.setAlert({
		message:
			'This project has a distance constraint set. Please enable device geolocation for optimal functionality',
		variant: 'warning',
	});
	return false;
}

const entityDistance = distance(coordFrom as Coord, coordTo as Coord, { units: 'kilometers' }) * 1000;
if (entityDistance && entityDistance > projectData?.geo_restrict_distance_meters) {
	// Feature is far away from user, warn user
	alertStore.setAlert({
		message: `The feature must be within ${projectData?.geo_restrict_distance_meters} meters of your location`,
		variant: 'warning',
	});
	if (projectData?.geo_restrict_force_error) {
		// Not valid coord, prevent user from continuing
		return false;
	}
	// Valid coord: it's outside of range, but only 'warn' user
	return true;
}

// Valid coord
return true;
};

The goal is to:

• Warn the user if geo_restrict_force_error=False
• Error / stop the user if geo_restrict_force_error=True

Hope this makes sense! Please check it works as intended, then merge 🙏

[NSUWAL123]

So do we want user's to restrict map the feature if their device location is turned off?
If yes then we shall update the toast message and let the user map the feature else we shall only update the toast message to Please enable device geolocation to map this feature.

[spwoodcock]

I didn't test the logic, so perhaps made a mistake.

But you make a good point.
We can't force users to enable geolocation, hence its impossible to actually enforce this constraint.

Anyway, this should happen:

• No geolocation, no force geo constraint: ignore / do not show warning.
• No geolocation, force geo constraint: prompt to enable geolocation.
• Geolocation, no force geo constraint: warning if triggered.
• Geolocation, force geo constraint: error if triggered.

Does that sound right?

[spwoodcock]

I'm really hesitant to block the user from mapping if they don't have location on (where I imagine this is what the Tokha team want @manjitapandey ?).

This would mean if there is a problem with the users geolocation, like they accidentally blocked access and can't work out how to enable access, they can't use FMTM (not ideal if they have been transported to the field and are now stuck and can't do anything)

[manjitapandey]

Yes the conditions above sounds right.

also In such cases, For Tokha projects, field managers and monitoring team will always be available on call to assist mappers in field. For other project this may not be relevant so only warnings and prompt to enable geolocation should work but this case is different.

[spwoodcock]

Thanks!

Let's block the mapping if geolocation is not enabled then @NSUWAL123 👍

[NSUWAL123]

Updated logic to:

• No geolocation, no force geo constraint: ignore / do not show warning
• No geolocation, force geo constraint: prompt to enable geolocation
• Geolocation, no force geo constraint: ignore / do not show warning
• Geolocation, force geo constraint: error if triggered

[spwoodcock]

So sorry to be a pain, but for the third option, do we not still want to show a warning?

Not a blocking error, but something like: 'The selected feature is far from your current location. Are you sure?'

[NSUWAL123]

Sure! It makes sense