Table of Contents |
---|
Our ultimate goal is to use AWS RDS for both input and output of mosaic data set creation. Ideally, input will be a staging RDS and output will be a production RDS.
...
Code Block | ||
---|---|---|
| ||
<AddRaster> <dataset_id>power</dataset_id> <raster_type>Table / Raster Catalog</raster_type> <Sources> <data_path>Z:\home\arcgis\data\CERES.csv</data_path> </Sources> <filter>*</filter> </AddRaster> |
Use the .sde file to specify mosaic destination (e.g., test_mosaic) using CLI. It will ignore Geodatabase in MDCS.xml file.
Code Block | ||
---|---|---|
| ||
PowerShell>%py% MDCS.py -i:MDCS_Solar.xml -m:Z:\home\arcgis\etc\aws_rds_geodb_conn.sde\test_mosaic
|
Use the .sde file to specify table destination.
Code Block | ||
---|---|---|
| ||
<AddRasters>
<AddRaster>
<dataset_id>power</dataset_id>
<raster_type>Table / Raster Catalog</raster_type>
<Sources>
<data_path>Z:\home\arcgis\etc\aws_rds_geodb_conn.sde\test_csv</data_path>
</Sources>
<filter>*</filter>
</AddRaster>
</AddRasters>
|
Info |
---|
Raster proxies can refer to AWS RDS [1]. From Abhijit, In MDCS to add raster to mosaic in SDE ( remote database) you can pass the path as below C:\Image_Mgmt_Workflows\NASA\Parameter\sde_conn.sde\testmosaic Where “C:\Image_Mgmt_Workflows\NASA\Parameter\sde_conn.sde” is the connection file for sde |
Content by Label | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...