Skip to content
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

CRS.srs attribute is not documented #253

Closed
jorisvandenbossche opened this issue Apr 8, 2019 · 6 comments
Closed

CRS.srs attribute is not documented #253

jorisvandenbossche opened this issue Apr 8, 2019 · 6 comments
Labels
documentation Docs need updating

Comments

@jorisvandenbossche
Copy link
Contributor

The srs attribute is not documented on the API page: https://pyproj4.github.io/pyproj/html/api/crs.html

From looking at the code, it seems this attribute is keeping the original "source" string how the CRS was created (which is then used in eg the repr) ?

@snowman2
Copy link
Member

snowman2 commented Apr 8, 2019

You are correct that it is the original "source" string for how the CRS was created. It might be good to add it to the documentation.

@jorisvandenbossche
Copy link
Contributor Author

To take a step back: does this need to be public? (internally it is also only used for the repr and pickling, as far as I can see)
And in that case, is srs a good name?

@snowman2
Copy link
Member

snowman2 commented Apr 8, 2019

srs is also used in the Transformer class for transformations. It does not have to be public, but it is useful for users to compare what they input to what was used to create their projection. The name was chosen to be consistent with the existing Proj.srs.

@jorisvandenbossche
Copy link
Contributor Author

The name was chosen to be consistent with the existing Proj.srs.

Ah, that's a good reason (if starting fresh, I would rather go with something more descriptive such as user_input, as I find srs a bit confusing)

@jorisvandenbossche
Copy link
Contributor Author

But with a good documentation entry, it maybe shouldn't be that confusing. Because as I see, the transformer is actually using this as the actual CRS definition to create the proj pipeline?

@snowman2
Copy link
Member

snowman2 commented Apr 8, 2019

I agree with you on the name. But, since it is there, for backwards compatibility, I think a documentation entry would be the way to go.

the transformer is actually using this as the actual CRS definition to create the proj pipeline?

Yes, it has been the most stable method for creating the proj pipeline.

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

No branches or pull requests

2 participants