Clarify geographic vs non-geographic bbox values #145
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates the language about bbox to align with GeoJSON for geographic coordinates and give min/max examples for non-geographic coordinates.
Fixes #112.
(One thing to note - the GeoJSON spec is a bit misleading in saying that the bbox has values for "all axes of the most southwesterly point followed by all axes of the more northeasterly point." What it means is that the value for$i_0$ is the most westerly, the value for $i_1$ is the most southerly, the value for $i_n$ is the most easterly, and the value for $i_{n+1}$ is the most northerly. The values for all other items are the minima followed by the maxima. The way the spec reads, it sounds like the third item of a bbox for geometries with a z would be the z value for the most southwesterly point. Instead it should be the minimum z value for all coordinates. I'll bring this up on the GeoJSON list and submit an errata report if others agree.)