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.
It is not clear how to set AWS RDS as output in MDCS xml file.
<Workspace> <WorkspacePath>md</WorkspacePath> <Geodatabase>Amberg</Geodatabase>
The above item is always local based on documentation. Ask Abhijit if a connection file can be used there for output.
It is also not clear how we can replace .csv file in MDCS xml file. Can the table entry be an AWS RDS?
<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.
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.
<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>
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