Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support for 'other members' in GeoJson all objects? #4

Open
jsiedentop opened this issue Feb 29, 2024 · 0 comments
Open

Support for 'other members' in GeoJson all objects? #4

jsiedentop opened this issue Feb 29, 2024 · 0 comments
Labels
RFC 7946 complaint

Comments

@jsiedentop
Copy link
Contributor

jsiedentop commented Feb 29, 2024 •
edited
Loading

The specification states that a geojson object may have other members. This is currently only implemented for features by propagating the fields property as Map<String, dynamic>.

3. GeoJSON Object

  • A GeoJSON object represents a Geometry, Feature, or collection of
    Features.
    • A GeoJSON object MAY have other members (see Section 6).

Nothing we need for TurfDart, but to be compliant with the standard we should keep this in mind.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
RFC 7946 complaint
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jsiedentop