[null,null,["最終更新日 2025-07-25 UTC。"],[[["\u003cp\u003eUpload GeoTIFF or TFRecord raster datasets to Earth Engine using the Asset Manager or CLI.\u003c/p\u003e\n"],["\u003cp\u003eImage assets up to 10 GB can be uploaded via the Code Editor; larger files require the command-line option.\u003c/p\u003e\n"],["\u003cp\u003eTFRecord uploads need an associated mixer file, especially for importing image predictions.\u003c/p\u003e\n"],["\u003cp\u003eEdit asset metadata, including the crucial \u003ccode\u003esystem:time_start\u003c/code\u003e property for date filtering, within the Asset Manager.\u003c/p\u003e\n"],["\u003cp\u003eAdvanced options allow customization of pyramiding policy for image resolution and masking modes for data handling.\u003c/p\u003e\n"]]],["Users can upload image datasets in GeoTIFF or TFRecord format using the Asset Manager or CLI. GeoTIFF files up to 10 GB can be uploaded through the Code Editor by selecting \"Image upload,\" specifying an asset ID, and clicking \"UPLOAD.\" TFRecord uploads require an associated mixer file, with predictions in the same order as exported images. Users can edit asset metadata, set properties, choose a pyramiding policy, and define masking modes. For large images, they can upload multiple tiles with constraints on bands, bit depth, projection, and resolution.\n"],null,["# Importing Raster Data\n\nYou can use the [Asset Manager](/earth-engine/guides/asset_manager) or\n[command line interface (CLI)](/earth-engine/guides/command_line#upload) to upload image or other\ngeoreferenced raster datasets in GeoTIFF or TFRecord format. (See\n[Importing Vector Data](/earth-engine/guides/table_upload) for details on importing vectors using the\nCode Editor.)\n\nUploading image assets\n----------------------\n\n### GeoTIFF\n\nIn the Code Editor, you can upload [GeoTIFF](https://github.com/OSGeo/libgeotiff) image files up to 10\nGB in size to your Earth Engine user folder. (For larger files, use the [command-line upload](https://developers.google.com/earth-engine/command_line#upload) option.)\n\nTo upload a GeoTIFF using the Code Editor,\nselect the Assets tab in the upper left corner,\nclick the button, then select **Image\nupload** . Earth Engine presents an upload dialog which should look similar to\nFigure 1. Click the **SELECT** button and navigate to a GeoTIFF on your local\nfile system.\n\nGive the image an appropriate asset ID (which doesn't already exist) in your\nuser folder. If you'd like to upload the image into an existing folder or collection,\nprefix the asset ID with the folder or collection ID, for example\n`projects/myproject/folder-or-collection-id/new-asset`.\n\nClick **UPLOAD** to start the upload.\nFigure 1. The asset manager image upload dialog\n\nOnce you have started the upload, an \"Asset ingestion\" task appears on the Tasks tab\nat the right side of the Code Editor. Hovering over the task in the task manager shows a\n**?** icon which you can use to check the upload status. To cancel an upload,\nclick the spinning icon next to the\ntask. Once the ingestion is complete, the asset will appear in your user folder with\na image icon.\n\n### GeoTIFF Compression\n\nGeoTIFF files can be compressed with DEFLATE, JPEG-XL/JXL, LERC, LERC_DEFLATE, LERC_ZSTD,\nLZMA, LZW, WEBP, or ZSTD.\n\nRecommendations for the best upload experience for large files:\n\n- **Best choice:** ZSTD offers a good balance of speed and compression.\n- **Avoid:** LZMA can be very slow despite good compression.\n- **Uncompressed files:** Will result in larger files and longer upload times.\n- **Lossy compression (e.g., JPEG):** May alter pixel values. Use lossless compression (e.g., DEFLATE, LZMA, LZW, ZSTD) rather than lossy, unless you understand the potential impact on your data.\n\n### TFRecord\n\nTo upload an image from a TFRecord file, you must have the associated mixer file that\nwas generated when you exported imagery on which you performed inference. See\n[the export page](/earth-engine/guides/exporting#mixer) for details on the mixer file. More\nspecifically, to import predictions (as an image) made on exported imagery,\n\n1. Export imagery into one or more TFRecord files.\n2. Perform inference on the imagery (i.e. `model.predict()`).\n3. Write the output of `model.predict()` into a TFRecord file. The predictions should be in the *same order* as the image exports on which you performed inference. Order can be enforced by a sort of the filenames produced by the export. See [the large file\n exports section](/earth-engine/guides/exporting#large-file-exports) for details.\n4. Upload the TFRecord file(s) and associated mixer to Earth Engine.\n\n### Properties editing\n\nEdit asset metadata by specifying one or more metadata properties. In the\n**Properties** menu, click **Add property** to\ndefine a property name and value (Figure 2). The value can be a string or a number.\nEnter strings without quotes. To format a number as a string, enter a single quote\n(`'`) before the number.\n\nBy default, a `system:time_start`\nproperty is added with no value. This property is used by Earth Engine when applying\n`ImageCollection` date filters. Enter either a date in the format shown\nin Figure 2, or a number representing milliseconds since January 1, 1970. (See\n[the glossary](/earth-engine/glossary) for more information on timestamps in Earth Engine).\nThe Asset Manager interprets a number entered as the value for a property named\n`system:time_start` or `system:time_end` as milliseconds and\nformats it as a date.\n\nClick the\ndelete\nicon to remove a property.\n\n### Advanced options\n\nIn the **Advanced** menu, choose the pyramiding policy and the masking mode\nfor your data.\n\nThe [pyramiding\npolicy](https://en.wikipedia.org/wiki/Pyramid_(image_processing)) specifies how Earth Engine generates lower resolution versions of the\nimage. Learn more about how Earth Engine handles multiple resolutions in the\n[scale doc](/earth-engine/guides/scale). Choose a 'Mean', 'Min', or 'Max' pyramiding policy to\ncompute lower resolution levels of the image pyramid as the mean, minimum or maximum\nof each 2x2 group of higher resolution pixels. This is a suitable option for\ncontinuous-valued images. For categorical (e.g. land cover) or QA data, choose a\n'Sample' (the upper left pixel) or 'Mode' (most frequently occurring value, or sample\nif there is no mode) pyramiding policy.\n\nThe masking mode indicates how the uploaded image is\n[masked](/earth-engine/guides/getstarted#masking) (if at all). To specify a no-data value,\nselect 'No-data value' and enter the value. Pixels with this value will be masked in the\nuploaded image. This value is applied to every band of the image independently. To use\nthe last band of your image as a mask for the other image bands, select 'Use last band\nas alpha band'. The\n[alpha band](https://en.wikipedia.org/wiki/Alpha_compositing) should be an\nunsigned 8-bit band where 0 is masked (completely transparent) data and 255 is\ncompletely opaque.\n\n### Tiled uploads\n\nTo upload a single image as multiple tiles, where each tile is stored in a different\nsource file, click **Add another file** to add additional files to the\nupload. Earth Engine will combine the tiles to create a single image in your user\nfolder.\n\nThere are a few constraints on the types of files that can be uploaded into an image\nasset. In particular:\n\n1. The images must have the same number of bands, bit depth, projection, resolution and fill values.\n2. The offset from one file to the next must be an integer multiple of the pixel size.\n3. Gaps between tiles will be filled with masked pixels in the final image, so the tiles should ideally be adjacent and not sparsely spread out. Images with gaps taking up \\\u003e99% of the image area won't be ingested."]]