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

troublesome crs matching, works on some versions of rasterio, but not others #592

Merged
merged 1 commit into from
Dec 27, 2023

Conversation

bw4sz
Copy link
Collaborator

@bw4sz bw4sz commented Dec 27, 2023

This is becoming a bit of a saga. #591 is rasterio version dependent. Comparing on str is much safer.

For example

gdf.crs
<Projected CRS: EPSG:32659>
Name: WGS 84 / UTM zone 59N
Axis Info [cartesian]:
- E[east]: Easting (metre)
- N[north]: Northing (metre)
Area of Use:
- name: Between 168°E and 174°E, northern hemisphere between equator and 84°N, onshore and offshore. Russian Federation; United States (USA) - Alaska.
- bounds: (168.0, 0.0, 174.0, 84.0)
Coordinate Operation:
- name: UTM zone 59N
- method: Transverse Mercator
Datum: World Geodetic System 1984 ensemble
- Ellipsoid: WGS 84
- Prime Meridian: Greenwich

has the same raster crs

raster_crs
CRS.from_epsg(32659)

Locally it works, but not on HPC

gdf.crs == raster_crs
False
gdf.crs.to_string() == raster_crs.to_string()
True

I'm rebasing upstream on my geo_type branch.

Not my finest day of software dev.

@bw4sz bw4sz merged commit ee9ee5d into main Dec 27, 2023
4 of 6 checks passed
@bw4sz bw4sz deleted the crs_to_string branch February 22, 2024 14:07
janjatovic pushed a commit to Treeconomy/DeepForest_new that referenced this pull request Mar 26, 2024
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.

1 participant