Skip to content

Conversation

d-v-b
Copy link
Contributor

@d-v-b d-v-b commented Oct 1, 2025

adds a pydantic model for projjson

@d-v-b
Copy link
Contributor Author

d-v-b commented Oct 1, 2025

@emmanuelmathot some comments on the geo proj spec based on the work here:

@d-v-b
Copy link
Contributor Author

d-v-b commented Oct 1, 2025

also:

  • "bbox" is defined relative to the CRS defined by the "code", "projjson", or "proj.wkt2" fields. But all of those fields are optional. If none of those fields are set, how should the "bbox" field be interpreted? Should it be ignored, or is it it an error for "bbox" to be set when a CRS was not declared?

@emmanuelmathot
Copy link
Contributor

  • we can update the examples
  • To me when not specified, null, empty or {} are the same.
  • projjson can be updated to projjson object.
  • At least one of the fields MUST be specified, but it is RECOMMENDED to provide more information so that, for example, GDAL can read your data without issues.

@d-v-b
Copy link
Contributor Author

d-v-b commented Oct 1, 2025

  • At least one of the fields MUST be specified, but it is RECOMMENDED to provide more information so that, for example, GDAL can read your data without issues.

I don't think this language is in the spec right now. For each of the 3 CRS fields, it says:

This field SHOULD be set to null in the following cases:

    The asset data does not have a CRS, such as in the case of non-rectified imagery with Ground Control Points.

@d-v-b
Copy link
Contributor Author

d-v-b commented Oct 1, 2025

should I open a PR to add the requirement that at least one of the 3 fields is set?

@emmanuelmathot
Copy link
Contributor

yes please

@emmanuelmathot
Copy link
Contributor

#44

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants