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.

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

GeoJson types limited to 2 fields #769

Closed
mion00 opened this issue Nov 24, 2015 · 1 comment
Closed

GeoJson types limited to 2 fields #769

mion00 opened this issue Nov 24, 2015 · 1 comment
Labels
stale

Comments

@mion00
Copy link

mion00 commented Nov 24, 2015

Quoting from the GeoJSON specification:

The GeoJSON object may have any number of members (name/value pairs)

Using one of the GeoJson types in Eve schemas I cannot add additional fields besides "types" and "coordinates".
For istance the following GeoJSON is valid according to http://geojsonlint.com/, but is rejected by Eve, having defined the field as type "point"

{
    "type": "Point",
    "coordinates": [
        -105.01621,
        39.57422
    ],
    "customField": "blabla"
}
Martin456 added a commit to Martin456/eve that referenced this issue Mar 26, 2017
@Martin456
Improve GeoJSON validation
5bbc576 
- New config variable to allow custom fields in GeoJSON (Issue pyeve#769)
- Validation if coordinates contain at least two values
- Support for Feature and FeatureCollection structures
@Martin456 Martin456 mentioned this issue Mar 26, 2017
Closed
nicolaiarocci pushed a commit that referenced this issue Apr 6, 2017
@Martin456 @nicolaiarocci
Improve GeoJSON validation
2ebb75c 
- New config variable to allow custom fields in GeoJSON (Issue #769)
- Validation if coordinates contain at least two values
- Support for Feature and FeatureCollection structures
nicolaiarocci pushed a commit that referenced this issue Apr 24, 2017
@Martin456 @nicolaiarocci
Improve GeoJSON validation
b144f7d 
- New config variable to allow custom fields in GeoJSON (Issue #769)
- Validation if coordinates contain at least two values
- Support for Feature and FeatureCollection structures
nicolaiarocci pushed a commit that referenced this issue May 2, 2017
@Martin456 @nicolaiarocci
Improve GeoJSON validation
a368d34 
- New config variable to allow custom fields in GeoJSON (Issue #769)
- Validation if coordinates contain at least two values
- Support for Feature and FeatureCollection structures
nicolaiarocci pushed a commit that referenced this issue May 3, 2017
@Martin456 @nicolaiarocci
Improve GeoJSON validation
71e38e4 
- New config variable to allow custom fields in GeoJSON (Issue #769)
- Validation if coordinates contain at least two values
- Support for Feature and FeatureCollection structures
@stale
Copy link

stale bot commented May 11, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label May 11, 2018
@stale stale bot closed this as completed May 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mion00