Spatial Join with GeometryOps is killing my Julia session

Specific Domains Geo
1

I’m trying to perform a spatial join in Julia between two files that aren’t that large. One is the California PLSS sections shapefile, which is publicly available here and is 164627 x 17 after some cleaning. The other I cannot share publicly, but it’s a biodiversity database that is 99316 x 42.
I perform the spatial join as mentioned in this tutorial as:

spatial_join = innerjoin((plss, biodiversity), by_pred(:geometry, GeometryOps.touches, :geometry))

And then REPL dies and I don’t get any error message. This happens both in VS Code and directly in the REPL. Any idea what’s going on? Could this be an OOM problem?

I also tried using GeoStats.jl, but I run into issues with the projection when trying to open the shapefiles.

My goal in to have a script that performs an analysis with these two files without opening them in ArcGIS. I managed to do it in R, but I’d like to do the same in Julia, but this part has been the bottleneck. I’ll appreciate any help.

2

Hi @alejandromerchan,

Please feel free to start a separate thread and we can try to help. Adding projections is usually easy. There is only one type of projection not covered yet that we are planning to add soon.

3

I don’t mind having the conversation here. The error I’m getting for both my files after running
plss = GeoIO.load("./PLSS/Statewide_CA_PLSS_NAD83AlbersCA_20240718.shp")

is

ERROR: ArgumentError: EPSG/ESRI code for the ESRI ID "NAD_1983_California_Teale_Albers" not found in dictionary. Please check https://github.com/JuliaEarth/CoordRefSystems.jl/blob/main/src/strings.jl If you know the EPSG/ESRI code of a given ESRI WKT string, please submit a pull request.

I checked the dictionary and there an "NAD_1983_Contiguous_USA_Albers" => EPSG{5070},, which I believe should work, but I’m guessing that you have to provide the exact name.

I’d like to make this work, but I also wonder if there’s a way to use the GeoDataFrame that I already have for the GeoTables.geojoin operation.

4

Whenever you encounter an error like this, go to epsg.io and copy/paste the ID:

There are two results as you can see:

image
image369×247 17.5 KB

If you click on them, and scroll down, you will see that you can choose to export the ESRI WKT. In this first result, the string is

"NAD_1983_California_Teale_Albers_FtUS"

image
image1033×427 49.9 KB

In the second result, the string is

"NAD_1983_California_Teale_Albers_Ft_Intl"

image
image1037×456 48.7 KB

So none of the two results match the string in your file. Let’s try the official EPSG database at Geodetic Database. If we search for “California Albers”, we get the following result:

https://epsg.org/crs_3310/NAD83-California-Albers.html

If that is the CRS of your data, then you have the EPSG code 3310.

After you confirm which of these is your CRS, we can help with next steps.

5

I can confirm that your CRS is NAD83 / California Albers - EPSG:3310

If you export the ESRI WKT you will see the same string stored in your file.

So the next step to get things loaded correctly is to submit a PR to CoordRefSystems.jl adding the pair "NAD_1983_California_Teale_Albers" => EPSG{3310} to the dictionary.

1 Like
6

Besed on the .proj file from one of my files, the last one has the right parameters, except the units are meters.

PROJCS[“NAD_1983_California_Teale_Albers”,
GEOGCS[“GCS_North_American_1983”,
DATUM[“D_North_American_1983”,
SPHEROID[“GRS_1980”,6378137.0,298.257222101]],
PRIMEM[“Greenwich”,0.0],
UNIT[“Degree”,0.0174532925199433]],
PROJECTION[“Albers”],
PARAMETER[“False_Easting”,0.0],
PARAMETER[“False_Northing”,-4000000.0],
PARAMETER[“Central_Meridian”,-120.0],
PARAMETER[“Standard_Parallel_1”,34.0],
PARAMETER[“Standard_Parallel_2”,40.5],
PARAMETER[“Latitude_Of_Origin”,0.0],
UNIT[“Meter”,1.0]]

7

Added the entry to the dictionary here:

1 Like
8

The units of the EPSG:3310 are meters:

image
image1216×743 49 KB

1 Like
9

The last ingredient to make things work is to map the newly added EPSG{3310} to an actual CRS type. This is what I did here:

I will merge the PR and release a patch so that you can load your files.

You should be able to update your environment after the version is merged:

Please let us know if something else is not working. Preferably in a separate thread.

10

Thanks a lot. I’ll let you know how it goes.

1 Like