GPS Coordinates (Decimal Degrees — High Precision) Regex for Go

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching gps coordinates (decimal degrees — high precision), ported and verified for Go. Identity and credential patterns need both correctness and safety, since they're frequent targets for adversarial input. The snippet below is ready to drop into your Go project — whether you're validating in a Gin handler, a gRPC service, or a command-line tool.

Go Implementation

// GPS Coordinates (Decimal Degrees — High Precision)
// ReDoS-safe | RegexVault — Identity & PII > Location PII

package validation

import "regexp"

var gpsCoordinatesDecimalDegreesHighPrecisionRe = regexp.MustCompile(`^(-?(?:90(?:\.0{1,6})?|(?:[0-8][0-9]|[0-9])(?:\.[0-9]{1,8})?)),\s?(-?(?:180(?:\.0{1,6})?|(?:1[0-7][0-9]|[0-9]{1,2})(?:\.[0-9]{1,8})?))$`)

func ValidateGpsCoordinatesDecimalDegreesHighPrecision(s string) bool {
    return gpsCoordinatesDecimalDegreesHighPrecisionRe.MatchString(s)
}

// Example
// fmt.Println(ValidateGpsCoordinatesDecimalDegreesHighPrecision("1.3521,103.8198")) // true

Test Cases

When to use this pattern

This pattern is drawn from the Identity & PII > Location PII category and carries a ReDoS-safe certification. That matters for Go developers because Go's RE2 engine is inherently safe from catastrophic backtracking, but this pattern has been additionally verified for correctness. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

Technical Notes

High-precision GPS (>4 decimal places) can identify a specific building or room. 4 decimal places ≈ 11m accuracy. 6 decimal places ≈ 0.1m. GPS coordinates of a home address or frequent location are personal data under GDPR.