update urls

CRAN-SUBMISSION

@@ -1,3 +1,3 @@
-Version: 0.0.7
-Date: 2024-08-29 19:47:20 UTC
-SHA: 95206cc8b77234f8f8f5e6b65d507bf2a7419d1c
+Version: 0.0.9
+Date: 2024-12-16 22:42:15 UTC
+SHA: c640069aa88db8207723af38530d36b5b51e9fc9

README.Rmd

@@ -87,7 +87,7 @@ efi <- open_dataset("s3://anonymous@neon4cast-scores/parquet/aquatics?endpoint_o
 
 `duckdb` can also understand a wide array of spatial data queries for spatial
 vector data, similar to operations found in the popular `sf` package.
-See [the list of supported functions](https://github.com/duckdb/duckdb_spatial#supported-functions) for details.
+See [the list of supported functions](https://github.com/duckdb/duckdb-spatial#supported-functions) for details.
 Most spatial query operations require an geometry column that expresses the 
 simple feature geometry in `duckdb`'s internal geometry format 
 (nearly but not exactly WKB).  
@@ -128,7 +128,7 @@ The `to_sf()` coercion will parse its input into a SQL query that gets
 passed to `duckdb`, and the return object will be collected through
 `sf::st_read`, returning an (in-memory) `sf` object. 
 
-For more details including a complete list of the dozens of spatial operations currently supported and notes on performance and current limitations, see the [duckdb spatial docs](https://github.com/duckdb/duckdb_spatial)
+For more details including a complete list of the dozens of spatial operations currently supported and notes on performance and current limitations, see the [duckdb spatial docs](https://github.com/duckdb/duckdb-spatial)
 
 ### Reading spatial vector files
 

README.md

@@ -108,7 +108,7 @@ efi <- open_dataset("s3://anonymous@neon4cast-scores/parquet/aquatics?endpoint_o
 `duckdb` can also understand a wide array of spatial data queries for
 spatial vector data, similar to operations found in the popular `sf`
 package. See [the list of supported
-functions](https://github.com/duckdb/duckdb_spatial#supported-functions)
+functions](https://github.com/duckdb/duckdb-spatial#supported-functions)
 for details. Most spatial query operations require an geometry column
 that expresses the simple feature geometry in `duckdb`’s internal
 geometry format (nearly but not exactly WKB).
@@ -167,7 +167,7 @@ collected through `sf::st_read`, returning an (in-memory) `sf` object.
 For more details including a complete list of the dozens of spatial
 operations currently supported and notes on performance and current
 limitations, see the [duckdb spatial
-docs](https://github.com/duckdb/duckdb_spatial)
+docs](https://github.com/duckdb/duckdb-spatial)
 
 ### Reading spatial vector files