Feature: Support more formats for latitude and longitude

[rushmorem]

Is your feature request related to a problem?

Currently these only support floats. We may want to support more formats like:-

40° 26′ 46″ N 79° 58′ 56″ W
N 40° 26′ 46″ W 79° 58′ 56″
40° 26.767' N 79° 58.933' W
40° 26′ 46″ 79° 58′ 56″, 40° 26′ 46″, 79° 58′ 56″, ...
N 40° 26.767' W 79° 58.933'
40° 26.767' 79° 58.933', 40° 26.767', 79° 58.933', ...
N 40.446° W 79.982°
40.446° N 79.982° W
40.446° 79.982°, 40.446,79.982, etc.

Describe the solution

From Tobie's comment:

We would need to write it in the parser (as opposed to defer to the that crate though, as that will be more performant. Similar to how we are parsing datetimes/durations...

Alternative methods

Using the linked crate latlon. See Tobie's comment above on this.

SurrealDB version

surreal 1.0.0-beta.7 for linux on x86_64

Contact Details

No response

Is there an existing issue for this?

• I have searched the existing issues

Code of Conduct

• I agree to follow this project's Code of Conduct

[Hirdey-1999]

I can help with the issue but can you please expand with the issue

[Adithya2907]

I would like to contribute to the project, and I feel that this issue would be a great place to start. Can I work on this problem, and how do I get started with it?

[koobitor]

Hi Guy,

That i understand right now surrealdb is not support string containing a pair of coordinates input should parse to Point with longitude as X and latitude as Y (natural map orientation) will enable to query.

Ref issue on #91 able to query with multipolygon right now.

This issue need to write parser form latlon string to coordinates format.

Can see more example on this

Best regards,
Koobitor

[Adithya2907]

Thank you for pointing me to the necessary files @koobitor. I'll get started with implementing the parser so that more formats for latitudes and longitudes are accepted.

[Adithya2907]

@tobiemh, @rushmorem I've gone through the codebase, and have a good understanding of the database engine now. I would like to get started with creating the parser to support more formats as mentioned before.
For this, do I create a new file, similar to datetime.rs and duration.rs, or do I define it inside the geometry.rs file itself?

[drdozer]

Hi - i saw this issue and thought it may be bite-sized. I've got surrealdb to compile. Is there a partial solution for this already implemented that I can help with or should I start from scratch?

[clarkmcc]

Hi @rushmorem, I've added support for parsing two of the example formats you specified (decimal degrees, or degree decimals). It would be great if I could get an intermediate review to make sure I'm on the right track before I add support for the remaining formats.

[clarkmcc]

I've added support for DD and DMS formats. Should be ready for review!

[rushmorem]

/cc @tobiemh