-
Notifications
You must be signed in to change notification settings - Fork 2
Create 1.0.0.schema.json #42
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
base: main
Are you sure you want to change the base?
Conversation
There's a general GeoJSON schema file here. We might want to take a look and compare. |
I'm not sure about requiring north/south/east/west elements. For typical rectangle-based index maps, these values are redundant with the information found in the geometry. Looking at the GBL code, I don't think GBL actually requires any elements except the geometry. However, basic functionality would require "label" (although GBL will handle null). |
Thats a good point about the point features. And if GBL can handle null in the label field, then I think we can move forward with no required elements. Reminding myself this means we need to explicitly allow null for these elements. |
At Geo4LibCamp we thought it would be useful to make the JSON Schema file a bit more restrictive about foreign member elements. Some fields like |
Addresses #41
Adds a JSON Schema file for Specification 1.0.0 which will help GeoBlacklight development better integrate OpenIndexMaps.
I had ChatGPT do a lot of the drafting, but it seems to validate fine. And despite saying that we have no required elements, I've included label, north, south, east, and west. Open to suggestions about this.