Skip to content

Projections, Extents, and Layout Definitions doc - #1608

Merged
lossyrob merged 1 commit into
locationtech:masterfrom
fosskers:docs/extents-etc
Sep 23, 2016
Merged

lossyrob merged 1 commit into
locationtech:masterfrom
fosskers:docs/extents-etc

Conversation

@fosskers

@fosskers fosskers commented Aug 4, 2016

Copy link
Copy Markdown
Contributor

The other day, on gitter:

Me: Alright, I'm digging into the relationship between projections, layout definitions, and extents.

@echeipesh : That sounds like a title of an excellent doc page I wish we had.

@fosskers

fosskers commented Aug 4, 2016

Copy link
Copy Markdown
Contributor Author

Not confident of the line:

"min" and "max" here are CRS specific, as the location of the point (0,0) varies between different CRS.

@lossyrob

lossyrob commented Aug 4, 2016

Copy link
Copy Markdown
Member

Would be useful to comment on the diff line you're referring to.

represented by two coordinate pairs that are its "min" and "max" corners in
some Coorindate Reference System. "min" and "max" here are CRS
specific, as the location of the point `(0,0)` varies between different CRS.
An Extent can also be referred to as a *Bounding Box*.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The whole extent is CRS specific; anything relating to the Extent will have to be in that CRS, and users of the extent should know the CRS of the extent if they are trying to combine it with other things, either by knowing implicitly that all the geometries they are working with are in the same CRS, or explicitly by holding onto CRS instances, and reprojecting where necessary.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, that's mentioned in the next paragraph.

@lossyrob
lossyrob merged commit 06d1306 into locationtech:master Sep 23, 2016
@lossyrob lossyrob added this to the 1.0 milestone Oct 18, 2016
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