Earth Engine はプライマリ ジオメトリ列の検出を試みます。特に指定しない限り、データ投影は WGS84 と見なされます。ジオメトリの測地線の状態は、指定された投影のデフォルトのエッジ解釈によって決まります（WGS84 では測地線ジオメトリが使用されます）。ただし、これは [詳細設定] メニューでオーバーライドできます。データのジオメトリが x 列と y 列で定義されたポイントの場合は、それぞれの列に「経度」と「緯度」という名前を付けるか、[詳細設定] で x 列と y 列の名前を指定してください。
[null,null,["最終更新日 2025-07-25 UTC。"],[[["\u003cp\u003eUpload Shapefiles or CSV files as table assets to Earth Engine using the Asset Manager or command line interface.\u003c/p\u003e\n"],["\u003cp\u003eEnsure your vector data is in \u003ccode\u003eEPSG:4326\u003c/code\u003e projection before uploading to avoid unintended coordinate transformations.\u003c/p\u003e\n"],["\u003cp\u003eCSV files representing geospatial features must have a geometry column (GeoJSON or WKT) or columns named "longitude" and "latitude" for point locations.\u003c/p\u003e\n"],["\u003cp\u003eLarge geometries with over 1 million vertices will be automatically split by Earth Engine during upload, and you can adjust this limit in Advanced Options.\u003c/p\u003e\n"],["\u003cp\u003eMonitor upload progress and manage tasks in the Task Manager, and access uploaded table assets as \u003ccode\u003eFeatureCollection\u003c/code\u003e objects in your scripts.\u003c/p\u003e\n"]]],["Datasets in Shapefile or CSV format can be uploaded using the Asset Manager or command line interface. When uploading, specify a unique asset ID. Shapefiles require .shp, .dbf, and .shx files; a .prj file is recommended to avoid WGS84 default coordinates. CSV files should include a geometry string or x and y position properties. Geometries with over 1 million vertices will automatically split. Upload progress can be tracked in the Task Manager. Table uploads have a limit of 100 million features and 1,024 properties per feature.\n"],null,["# Importing Table Data\n\nUploading table assets\n----------------------\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 datasets in\nthe Shapefile or CSV format. (See [Importing Raster Data](/earth-engine/guides/image_upload) for details\non importing rasters using the Code Editor or CLI.) Your uploaded assets are initially\nprivate, but can be shared as described in the [Sharing\nAssets Section](/earth-engine/guides/asset_manager#sharing-assets).\n| **Warning:** All vector data in Earth Engine is stored in a spherical coordinate system (specifically, `EPSG:4326`). When data is uploaded, the resultant coordinate transformation may have unintended consequences that include change of geometry type (e.g. from polygon to linestring or point) or incorrect georeferencing. To minimize the possibility of unintended changes, first reproject vector data to `EPSG:4326` before uploading.\n\n### Upload a Shapefile\n\nTo upload a Shapefile from the Code Editor, click the\nbutton, then select\n**Shape files** under the **Table\nUpload** section. An upload dialog similar to\nFigure 1 will be presented. Click the **SELECT** button and navigate to a\nShapefile or Zip archive containing a Shapefile on your local file system. When selecting a\n.shp file, be sure to select the related .dbf, .shx and .prj files. Earth\nEngine will default to WGS84 (longitude, latitude) coordinates if a .prj file is not\nprovided. If you are uploading a Zip archive, make sure it contains only one Shapefile\n(set of .shp, .dbf, .shx, .prj, etc.) and no duplicate filenames. Make sure filenames\ndo not include additional periods or dots. (Filenames will include a single period before\nthe extension.)\n\nGive the table an appropriate asset ID (which doesn't already exist) in your\nuser folder. Click **UPLOAD** to start the upload.\nFigure 1. The Asset Manager Shapefile upload dialog. Note that the .shp, .dbf, and .shx files are required. The other sidecar files are optional. If the .prj file is not provided, WGS84 is assumed.\n\n### Upload a CSV file\n\nTo upload a CSV from the Code Editor, activate the **Assets** tab, then click\nthe button and select\n**CSV file** under the **Table Upload** section. An upload dialog\nsimilar to Figure 2 will be presented. Click the **SELECT** button and navigate\nto a .csv file on your local file system. Give the table a unique, relevant asset ID name.\nClick OK\nto start the upload.\nFigure 2. The Asset Manager CSV file upload dialog.\n\nThe CSV file should contain a row for each feature and as many columns as there are\nproperties or variables for the feature set. If features are geospatial, they must have a\ngeolocation defined by either a geometry string (GeoJSON, WKT) or x and y position properties.\nIf the CSV file is an export from a GIS or geospatial data tool such as GDAL/OGR, a properly\nformatted and named geometry column should already exist.\nAlternatively, two columns for x and y coordinates representing point locations can be\ndefined in a spreadsheet application and exported\nas CSV format along with any other variables.\n\nAdvanced Options\n----------------\n\n\nIn the **Advanced options** section of the upload dialog, view and change\ndefault settings. Performance of Earth Engine can be improved by splitting up geometries\nthat have a large number of vertices. Earth Engine does not allow features with more than 1\nmillion vertices. During table upload, Earth Engine will automatically split geometries that\nhave more than 1 million vertices. You can specify a lower value to improve vector\nrendering performance.\n\nEarth Engine will attempt to detect a primary geometry column and assumes the data\nprojection is WGS84 unless otherwise specified. The geodesic state of the geometries are\ndetermined by the default edge interpretation of the\ngiven projection (e.g. WGS84 uses geodesic geometries), but this can be overridden in the\nAdvanced settings menu. If the geometry of your data are points defined by x and y\ncolumns, be sure to name the respective columns \"longitude\" and \"latitude\" or specify the\nx and y column names under Advanced settings.\n| **Note:** Mixed datatype columns (e.g. numbers and strings) will default to string upon ingestion. This is an important consideration when preparing a table in a spreadsheet application, where it is common to denote missing data as NA, Null, None, --, etc. In the case of missing data, leave the \"cell\" empty.\n\nTracking upload progress\n------------------------\n\n\nAfter starting a table upload, an 'Asset ingestion' task is added to the Task Manager, found\nunder the **Tasks** tab at the right side of the Code Editor. Check the upload\nstatus by clicking on the **?** icon that appears when hovering over the\ntask. To cancel an upload, click on the spinning icon\nnext to the\ntask. Once the ingestion is complete, the task cell will turn blue and the asset will appear\nin your user folder under the **Assets** tab with\na table_chart icon.\n\nTable Upload Limits\n-------------------\n\n\nWhen uploading tables, the maximum number of features in the table is 100 million. The maximum\nnumber of properties on a feature is 1,024. These limits ensure that the resulting asset can\nbe queried efficiently. Additionally, each feature has a maximum number of vertices as\nexplained in the \"Advanced Options\" section above.\n\nLoading a table asset to your script\n------------------------------------\n\nTo create a `FeatureCollection` in your script from a table asset, import it as\ndescribed on the [Managing Assets](/earth-engine/guides/asset_manager#importing-assets-to-your-script)\npage."]]
ボタンをクリックし、[テーブルのアップロード] セクションで [シェープファイル] を選択します。図 1 のようなアップロード ダイアログが表示されます。[SELECT] ボタンをクリックし、ローカル ファイル システムにあるシェープファイルまたはシェープファイルを含む ZIP アーカイブに移動します。.shp ファイルを選択する際は、関連する .dbf、.shx、.prj ファイルも必ず選択してください。.prj ファイルが指定されていない場合、Earth Engine はデフォルトで WGS84（経度、緯度）座標を使用します。ZIP アーカイブをアップロードする場合は、シェープファイル（.shp、.dbf、.shx、.prj などのセット）が 1 つだけ含まれ、ファイル名が重複していないことを確認してください。ファイル名に余分なピリオドやドットが含まれていないことを確認します。（ファイル名の拡張子の前にピリオドが 1 つ付きます）。
をクリックします。取り込みが完了すると、タスクセルが青色に変わり、アセットがユーザー フォルダの [アセット] タブに アイコン付きで表示されます。