Because raster data is typically pretty large (gigabytes to terabytes), the Woolpert team recommends using a public cloud storage option to stage your data for STREAM:RASTER to ingest. For example, we often have customers upload data to a Google Cloud Storage (GCS) bucket or Amazon S3 bucket first.
There are some web and desktop applications for transferring files to cloud storage buckets, but for robustness we recommend utilities like gsutil rsync to perform bulk uploads from your on-premises data store to the cloud for ingestion.
If you want to use this option Woolpert will set up a Google Cloud Storage bucket and give you access to upload data.
Woolpert can also accept a hard drive of imagery. Please contact your Customer Engineer or follow along the steps in this article: How do I set up and use STREAM:RASTER?
File size and file count
Pixel dimensions of individual image files must not exceed 30,000 x 30,000 pixels.
There is no limit on input band count, but only 3-band images are supported as output. For images with 4 or more bands: the first 3 bands will be included by default, or an alternate 3-band-mapping may be specified (e.g. colorized infrared).
Maximum file count for each dataset is 20,000 image files (accompanying metadata files such as world files or auxiliary XML files do not count toward this limit).
Images to be published as a single layer must all have the same resolution, and "y" resolution values should be negative. There must not be any rotation factor in the geotransform.
Images to be published as a single layer must all be in the same coordinate reference system (CRS). If not defined in image metadata, CRS information must be provided to Woolpert prior to ingestion. CRS definitions must be supported by the PROJ library and can be specified as EPSG code, well-known text (either OGC or Esri dialects), or PROJ string.
Image types and formats
Any 8-bit image format denoted as "Built-in by default" in GDAL's raster driver list is supported as input: https://gdal.org/drivers/raster/index.html
Storing images in a lossless compression format (e.g. GeoTIFF with deflate compression) may improve upload and/or processing speed.
Time between upload and availability to view
The short answer: about five business days, with processing throughput anywhere in the 150GiB to 300GiB per hour range.
The longer answer should help you understand why we're so focused on the quality of the final product.
- Compatible. After uploading your imagery, Woolpert staff will review it to confirm basic details about the dataset(s), including size, format, coordinate system, and resolution. We confirm that your imagery is compatible with STREAM:RASTER.
- Optimize. For a first-time customer we typically find some optional tweaks that can improve the final tile image quality or processing speed. So when we're asking 'how long until I see my final tiles?' we like to estimate about five business days just to make sure we have time for the prep work to ensure the best possible quality product.
- Assurance. Upon completing this review, your imagery will be queued for processing. After processing, imagery will again be reviewed by Woolpert staff for quality assurance and reprocessed if necessary. And then you get to look at it and tell us if you're happy with it.
Article is closed for comments.