diff --git a/apple-touch-icon-120x120.png b/apple-touch-icon-120x120.png index 5a1f39f6c..6d62996bf 100644 Binary files a/apple-touch-icon-120x120.png and b/apple-touch-icon-120x120.png differ diff --git a/apple-touch-icon-152x152.png b/apple-touch-icon-152x152.png index 8184a5362..9abe8f691 100644 Binary files a/apple-touch-icon-152x152.png and b/apple-touch-icon-152x152.png differ diff --git a/apple-touch-icon-180x180.png b/apple-touch-icon-180x180.png index fe57504fb..d493e655a 100644 Binary files a/apple-touch-icon-180x180.png and b/apple-touch-icon-180x180.png differ diff --git a/apple-touch-icon-60x60.png b/apple-touch-icon-60x60.png index e660a9a69..2614f814c 100644 Binary files a/apple-touch-icon-60x60.png and b/apple-touch-icon-60x60.png differ diff --git a/apple-touch-icon-76x76.png b/apple-touch-icon-76x76.png index 2ca4fc8e7..7719dd0ae 100644 Binary files a/apple-touch-icon-76x76.png and b/apple-touch-icon-76x76.png differ diff --git a/apple-touch-icon.png b/apple-touch-icon.png index d4354810f..c08bd1942 100644 Binary files a/apple-touch-icon.png and b/apple-touch-icon.png differ diff --git a/articles/sf1.html b/articles/sf1.html index a2a82de12..a16562ddc 100644 --- a/articles/sf1.html +++ b/articles/sf1.html @@ -374,7 +374,7 @@

sf: objects with simple features## Dimension: XY ## Bounding box: xmin: -84.32385 ymin: 33.88199 xmax: -75.45698 ymax: 36.58965 ## Geodetic CRS: NAD27 -

(Note that users will not use system.file but give a +

(Note that users will not use system.file() but give a filename directly, and that shapefiles consist of more than one file, all with identical basename, which reside in the same directory.) The short report printed gives the file name, the driver @@ -475,7 +475,7 @@

sfc: simple feature geometry li geometries is a list, of class sfc. We can retrieve the geometry list-column in this case by nc$geom or nc[[15]], but the more general way uses -st_geometry:

+st_geometry():

 (nc_geom <- st_geometry(nc))
 ## Geometry set for 100 features 
@@ -574,10 +574,10 @@ 
sfc: simple feature geometry li
 ## [67] str                          summary                     
 ## [69] vec_cast.sfc                 vec_ptype2.sfc              
 ## see '?methods' for accessing help and source code
-

Coordinate reference systems (st_crs and -st_transform) are discussed in the section on coordinate reference systems. st_as_wkb and -st_as_text convert geometry list-columns into -well-known-binary or well-known-text, explained below. st_bbox retrieves the coordinate +

Coordinate reference systems (st_crs() and +st_transform()) are discussed in the section on coordinate reference systems. st_as_wkb() +and st_as_text() convert geometry list-columns into +well-known-binary or well-known-text, explained below. st_bbox() retrieves the coordinate bounding box.

Attributes include:

@@ -812,7 +812,7 @@ 
Reading and writing
 nc <- read_sf(filename)

Writing takes place in the same fashion, using -st_write:

+st_write():

 st_write(nc, "nc.shp")
 ## Writing layer `nc' to data source `nc.shp' using driver `ESRI Shapefile'
@@ -831,9 +831,9 @@ 
Reading and writingDriver-specific options
 

 
The dsn and layer arguments to
-st_read and st_write denote a data source name
-and optionally a layer name. Their exact interpretation as well as the
-options they support vary per driver, the GDAL driver
+st_read() and st_write() denote a data source
+name and optionally a layer name. Their exact interpretation as well as
+the options they support vary per driver, the GDAL driver
 documentation is best consulted for this. For instance, a PostGIS
 table in database postgis might be read by:

 
@@ -841,11 +841,11 @@ 
Driver-specific optionswhere the PG: string indicates this concerns the PostGIS
 driver, followed by database name, and possibly port and user
 credentials. When the layer and driver
-arguments are not specified, st_read tries to guess them
+arguments are not specified, st_read() tries to guess them
 from the datasource, or else simply reads the first layer, giving a
 warning in case there are more.

-
st_read typically reads the coordinate reference system
-as proj4string, but not the EPSG (SRID). GDAL cannot
+
st_read() typically reads the coordinate reference
+system as proj4string, but not the EPSG (SRID). GDAL cannot
 retrieve SRID (EPSG code) from proj4string strings, and,
 when needed, it has to be set by the user. See also the section on coordinate reference systems.

 
st_drivers() returns a data.frame listing
@@ -885,9 +885,9 @@ 
Create, read, update and deletecrud
 (create, read, update, delete) functions to persistent storage.
-st_read (or read_sf) are used for reading.
-st_write (or write_sf) creates, and has the
-following arguments to control update and delete:

+st_read() (or read_sf()) are used for reading.
+st_write() (or write_sf()) creates, and has
+the following arguments to control update and delete: