-
Notifications
You must be signed in to change notification settings - Fork 122
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
ProjectionExtension v2 (proj:epsg -> proj:code) #1287
Conversation
Just checking in on this, is there a date by which the change to support proj:code instead of proj:epsg is expected to take effect? |
Not at this time ... always looking for folks to help out to help move things along! |
@jsignell I noticed that to fix summaries, I am going to have to edit https://github.com/stac-utils/pystac/blob/main/pystac/static/fields-normalized.json - which is easy enough! but it's not formatted at all as a file, so I wanted to check: is it a build artifact of some other Also, whats the best way to run tests with changes to this file? override to a local path or push my local copy to the CDN somehow? |
|
Right I saw that, and it does make sense, but if I need to change it, do I
just Change it like I would than any other file in the repo?
…On Tue, Dec 31, 2024 at 5:05 AM Pete Gadomski ***@***.***> wrote:
or is it just kinda new / should be edited directly if I need to make
changes?
fields-normalized.json is pulled from
***@***.***/stac-fields via this script
<https://github.com/stac-utils/pystac/blob/main/scripts/pull-static>.
—
Reply to this email directly, view it on GitHub
<#1287 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACOH4J2YA47IQCDZZMXISDD2IKCBVAVCNFSM6AAAAABQR6WDL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRWGM4TGMJXGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I don't quite understand the question. Any modifications to |
Sorry I didn’t get to follow up - After I walked away from my computer, I was wondering if that was what you meant. That answers my question, I’ll probably start with a PR to that repo then! Thanks!
|
Hi @KeynesYouDigIt! Thanks for trying to pick this back up. I had opened a PR on stac-fields (stac-utils/stac-fields#27) back when I was working on this, and it looks like that morphed into stac-utils/stac-fields@ebd9c99 is there something more that you need? Or maybe it's just a matter of updating a dependency. |
Hi @jsignell !
Shoulda seen that, thanks for the help! Will let you know how it goes, hoping to wrap it up soon. |
@jsignell So I have commits on this branch that should cover the step
https://github.com/KeynesYouDigIt/pystac/tree/refs/heads/proj-v2 Let me know if I should PR to your branch or directly to this one, I have no preference. As far as the next step, I'm hunting around for exactly what this means...
Could you point me to where this is done and what this means? Does this refer to some of the URI constants in Also we might add some more unit tests, but what do you think? |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1287 +/- ##
==========================================
- Coverage 91.32% 91.23% -0.09%
==========================================
Files 53 53
Lines 7293 7335 +42
Branches 885 894 +9
==========================================
+ Hits 6660 6692 +32
- Misses 452 457 +5
- Partials 181 186 +5 ☔ View full report in Codecov by Sentry. |
Ok! @KeynesYouDigIt thanks so much for pushing this forward! I pulled your commits into this branch and did a few tidy ups. It looks like things are passing now, but as you mentioned more unit tests/docs would be super useful! |
epsg: int | None, | ||
*, | ||
epsg: int | None = None, | ||
code: str | None = None, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gadomski if we want strictly no API changes we could take away the no positional args constraint, but I think we'd want to add it in pystac v2 to make the behavior very explicit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I think that's fine, might break a few folks but it's an easy fix on their part.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oof, thanks for doing this — PySTAC extensions, huh 😓? Just one or two comments, otherwise looks good.
epsg: int | None, | ||
*, | ||
epsg: int | None = None, | ||
code: str | None = None, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I think that's fine, might break a few folks but it's an easy fix on their part.
Great work everybody! CC: @nick-j-roberts |
Related Issue(s):
Description:
The intention of this PR is to still support using epsg and just store it in
proj:code
.Note
This PR removes epsg as a positional argument to ProjectionExtension.apply. It also removes all positional arguments to it should raise nice errors for that scenario.
Another option would be to allow positional arguments and automatically deduce whether they should be interpreted as
epsg
orcode
based on type. I suspect that usingepsg
as a positional argument inapply
is rare, so I strongly prefer the approach in this PR.TO DO:
PR Checklist:
pre-commit
hooks pass locallyscripts/test
)