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

Constraint minimum should indicate more types. #345

Open
tredoe opened this Issue Dec 20, 2016 · 1 comment

Comments

Projects
None yet
3 participants
@tredoe

tredoe commented Dec 20, 2016

The key minimum says:

Supported field types are integer, number, date, time and datetime.

But it also should be added: gyear and gyearmonth, shouldn't it?

@pwalsh pwalsh added the Table Schema label Feb 5, 2017

@pwalsh pwalsh added this to the v1.1 milestone Feb 5, 2017

@Stephen-Gates

This comment has been minimized.

Show comment
Hide comment
@Stephen-Gates

Stephen-Gates Jun 13, 2017

Contributor

Please also consider min/max for the lat,lon values in a geopoint type as discussed at https://discuss.okfn.org/t/how-to-constrain-geopoint-values/5574

Contributor

Stephen-Gates commented Jun 13, 2017

Please also consider min/max for the lat,lon values in a geopoint type as discussed at https://discuss.okfn.org/t/how-to-constrain-geopoint-values/5574

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment