generate the JSON file, you can easily change the export format (XML or CSV, for example) or the storage backend (FTP or Amazon S3, for example). You can also write an item pipeline to store the items in a which allows you to generate feeds with the scraped items, using multiple serialization formats and storage backends. 84 Chapter 3. Basic concepts Scrapy Documentation, Release 2.4.1 3.8.1 Serialization multiple storage backend types which are defined by the URI scheme. The storages backends supported out of the box are: • Local filesystem • FTP • S3 (requires botocore) • Google Cloud Storage (GCS)

generate the JSON file, you can easily change the export format (XML or CSV, for example) or the storage backend (FTP or Amazon S3, for example). You can also write an item pipeline to store the items in a which allows you to generate feeds with the scraped items, using multiple serialization formats and storage backends. 3.8.1 Serialization formats For serializing the scraped data, the feed exports use the multiple storage backend types which are defined by the URI scheme. The storages backends supported out of the box are: • Local filesystem • FTP • S3 (requires boto3) • Google Cloud Storage (GCS) (requires

generate the JSON file, you can easily change the export format (XML or CSV, for example) or the storage backend (FTP or Amazon S3, for example). You can also write an item pipeline to store the items in a which allows you to generate feeds with the scraped items, using multiple serialization formats and storage backends. 3.8.1 Serialization formats For serializing the scraped data, the feed exports use the multiple storage backend types which are defined by the URI scheme. The storages backends supported out of the box are: • Local filesystem • FTP • S3 (requires botocore) • Google Cloud Storage (GCS)

generate the JSON file, you can easily change the export format (XML or CSV, for example) or the storage backend (FTP or Amazon S3, for example). You can also write an item pipeline to store the items in a which allows you to generate feeds with the scraped items, using multiple serialization formats and storage backends. 3.8.1 Serialization formats For serializing the scraped data, the feed exports use the multiple storage backend types which are defined by the URI scheme. The storages backends supported out of the box are: • Local filesystem • FTP • S3 (requires botocore) • Google Cloud Storage (GCS)

generate the JSON file, you can easily change the export format (XML or CSV, for example) or the storage backend (FTP or Amazon S3, for example). You can also write an item pipeline to store the items in a which allows you to generate a feed with the scraped items, using multiple serialization formats and storage backends. 3.8.1 Serialization formats For serializing the scraped data, the feed exports use the store the feed using a URI (through the FEED_URI setting). The feed exports supports multiple storage backend types which are defined by the URI scheme. The storages backends supported out of the box are:

generate the JSON file, you can easily change the export format (XML or CSV, for example) or the storage backend (FTP or Amazon S3, for example). You can also write an item pipeline to store the items in a which allows you to generate feeds with the scraped items, using multiple serialization formats and storage backends. 3.8.1 Serialization formats For serializing the scraped data, the feed exports use the multiple storage backend types which are defined by the URI scheme. The storages backends supported out of the box are: • Local filesystem • FTP • S3 (requires botocore) • Google Cloud Storage (GCS)

generate the JSON file, you can easily change the export format (XML or CSV, for example) or the storage backend (FTP or Amazon S3, for example). You can also write an item pipeline to store the items in a which allows you to generate feeds with the scraped items, using multiple serialization formats and storage backends. 3.8.1 Serialization formats For serializing the scraped data, the feed exports use the multiple storage backend types which are defined by the URI scheme. The storages backends supported out of the box are: • Local filesystem • FTP • S3 (requires botocore) • Google Cloud Storage (GCS)

generate the JSON file, you can easily change the export format (XML or CSV, for example) or the storage backend (FTP or Amazon S3, for example). You can also write an item pipeline to store the items in a which allows you to generate feeds with the scraped items, using multiple serialization formats and storage backends. 3.8.1 Serialization formats For serializing the scraped data, the feed exports use the multiple storage backend types which are defined by the URI scheme. The storages backends supported out of the box are: • Local filesystem • FTP • S3 (requires botocore) • Google Cloud Storage (GCS)

generate the JSON file, you can easily change the export format (XML or CSV, for example) or the storage backend (FTP or Amazon S3, for example). You can also write an item pipeline to store the items in a which allows you to generate feeds with the scraped items, using multiple serialization formats and storage backends. This page provides detailed documentation for all feed export features. If you are looking multiple storage backend types which are defined by the URI scheme. The storages backends supported out of the box are: • Local filesystem • FTP • S3 (requires boto3) • Google Cloud Storage (GCS) (requires

generate the JSON file, you can easily change the export format (XML or CSV, for example) or the storage backend (FTP or Amazon S3, for example). You can also write an item pipeline to store the items in a which allows you to generate feeds with the scraped items, using multiple serialization formats and storage backends. This page provides detailed documentation for all feed export features. If you are looking multiple storage backend types which are defined by the URI scheme. The storages backends supported out of the box are: • Local filesystem • FTP • S3 (requires boto3) • Google Cloud Storage (GCS) (requires