Provide an option property to provide custom circumferences in address.nearbyGPSCoordinate

[Shinigami92]

Clear and concise description of the problem

Currently address.nearbyGPSCoordinate is hardly based on earth, but we can change that simply by provide the possibility to provide a custom circumference given by the user.

faker/src/modules/address/index.ts

Lines 544 to 545 in 7327e6e

	// TODO @Shinigami92 2022-04-26: Provide an option property to provide custom circumferences.
	const kmPerDegree = 40_000 / 360; // in km/°

Suggested solution

nearbyGPSCoordinate(
  coordinate?: [latitude: number, longitude: number],
  options: {
    radius: number = 10,
    isMetric: boolean = false
    circumference: number = 40_000
  }
)

Alternative

No response

Additional context

No response

[xDivisionByZerox]

Is this really needed? I mean GPS Coordinates should be based on Earth's geometric data, shouldn't they?

[Shinigami92]

Maybe the function should even not include GPS just nearbyCoordinate, as it has nothing todo with GPS 🤷

[xDivisionByZerox]

That sounds more reasonable

[github-actions]

Thank you for your feature proposal.

We marked it as "waiting for user interest" for now to gather some feedback from our community:

• If you would like to see this feature be implemented, please react to the description with an up-vote (:+1:).
• If you have a suggestion or want to point out some special cases that need to be considered, please leave a comment, so we are aware about them.

We would also like to hear about other community members' use cases for the feature to give us a better understanding of their potential implicit or explicit requirements.

We will start the implementation based on:

• the number of votes (:+1:) and comments
• the relevance for the ecosystem
• availability of alternatives and workarounds
• and the complexity of the requested feature

We do this because:

• There are plenty of languages/countries out there and we would like to ensure that every method can cover all or almost all of them.
• Every feature we add to faker has "costs" associated to it:
  • initial costs: design, implementation, reviews, documentation
  • running costs: awareness of the feature itself, more complex module structure, increased bundle size, more work during refactors

---

View more issues which are waiting for user interest