{"_id":"5955268495aa76002de6cbe2","project":"55faeacad0e22017005b8265","version":{"_id":"55faeacad0e22017005b8268","project":"55faeacad0e22017005b8265","__v":35,"createdAt":"2015-09-17T16:31:06.800Z","releaseDate":"2015-09-17T16:31:06.800Z","categories":["55faeacbd0e22017005b8269","55faf550764f50210095078e","55faf5b5626c341700fd9e96","55faf8a7825d5f19001fa386","560052f91503430d007cc88f","560054f73aa0520d00da0b1a","56005aaf6932a00d00ba7c62","56005c273aa0520d00da0b3f","5601ae7681a9670d006d164d","5601ae926811d00d00ceb487","5601aeb064866b1900f4768d","5601aee850ee460d0002224c","5601afa02499c119000faf19","5601afd381a9670d006d1652","561d4c78281aec0d00eb27b6","561d588d8ca8b90d00210219","563a5f934cc3621900ac278c","5665c5763889610d0008a29e","566710a36819320d000c2e93","56ddf6df8a5ae10e008e3926","56e1c96b2506700e00de6e83","56e1ccc4e416450e00b9e48c","56e1ccdfe63f910e00e59870","56e1cd10bc46be0e002af26a","56e1cd21e416450e00b9e48e","56e3139a51857d0e008e77be","573b4f62ef164e2900a2b881","57c9d1335fd8ca0e006308ed","57e2bd9d1e7b7220000d7fa5","57f2b992ac30911900c7c2b6","58adb5c275df0f1b001ed59b","58c81b5c6dc7140f003c3c46","595412446ed4d9001b3e7b37","59e76ce41938310028037295","5a009de510890d001c2aabfe"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"v1","version_clean":"1.0.0","version":"1"},"category":{"_id":"595412446ed4d9001b3e7b37","project":"55faeacad0e22017005b8265","version":"55faeacad0e22017005b8268","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2017-06-28T20:32:04.415Z","from_sync":false,"order":2,"slug":"gbdx-data-sets-in-progress","title":"Data Sets on GBDX"},"user":"55fae9d4825d5f19001fa379","__v":0,"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-06-29T16:10:44.461Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":4,"body":"# Table of Contents\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Section\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"[Overview](#section-overview)\",\n    \"0-1\": \"Overview of the MDA RADARSAT-2 extra-fine data set\",\n    \"1-0\": \"[Accessing MDA RADARSAT-2 Data](#section-accessing-mda-radarsat-2-data)\",\n    \"1-1\": \"An access key is required to get location information for MDA data. This section describes how this works\",\n    \"2-0\": \"[MDA Acqusitions and Products](#section-mda-acquisitions-and-products)\",\n    \"2-1\": \"This section describes acquisitions and products\",\n    \"3-0\": \"[Types](#section-types)\",\n    \"3-1\": \"This section describes the \\\"types\\\" used to identify MDA Acquisitions and Products\",\n    \"4-0\": \"[Search](#section-search)\",\n    \"4-1\": \"This section describes how to search for MDA Acquisitions and Products, and provides examples of a search and response\",\n    \"5-0\": \"[MDA Product Properties](#section-product-properties)\",\n    \"5-1\": \"This section defines the properties of an MDA product\",\n    \"6-0\": \"[MDA Acquisition Properties](#section-acquisition-properties)\",\n    \"6-1\": \"This section defines the properties of an MDA Acquisition\",\n    \"7-0\": \"[Order MDA Products](#section-order-mda-products)\",\n    \"7-1\": \"This section describes how to order MDA products that are not already available in the GBDX product catalog\",\n    \"8-0\": \"[Find the S3 bucket location for an MDA Product](#section-find-the-s3-bucket-location-for-an-mda-product)\",\n    \"8-1\": \"The S3 bucket location is encrypted, and is only available to customers who purchase the MDA package. Learn more.\",\n    \"9-0\": \"[Run an MDA Task](#section-run-an-mda-task)\",\n    \"9-1\": \"This section identifies algorithms that can run with MDA data on GBDX\"\n  },\n  \"cols\": 2,\n  \"rows\": 10\n}\n[/block]\n# Overview\nThe MacDonald, Dettwiler and Associates Ltd. (MDA) RADARSAT-2 satellite provides high-resolution, operationally focused synthetic aperture radar (SAR) data regardless of cloud cover or light conditions. With unique feature classification capabilities, this dataset allows users to observe features and changes in the environment that would go undetected using other imaging techniques. RADARSAT-2 images the Earth at spatial resolutions ranging from 1 to 100 metres, providing coverage from 144 to 250,000 km<sup>2</sup> in a single scene. Access to the global archive of Extra-Fine beam mode imagery is provided via GBDX. MDA has integrated a synthetic aperture radar (SAR) change detection tool into GBDX that will enable amplitude change detection to be performed on RADARSAT-2 imagery.\n\n**Uses**\nUsers will be able to extract location intelligence at scale, and create reliably collected change detection value-added products on the platform. Unlocked capabilities include automated port monitoring, object detection, and broad area change monitoring.\n\n**Spectral Bands**: Extra Fine Beam Mode\n**Date Range**: March 2013 to present\n**Products available through GBDX**: RADARSAT-2 Extra-fine beam mode dataset (SGF Format)\n**GBDX MDA Package:** The GBDX MDA package can be added to an existing GBDX contract, or purchased as a stand-alone product.  For more information on this offering, contact [**gbdx-support:::at:::digitalglobe.com** ](mailto:gbdx-support@digitalglobe.com).\n\nLearn more about use cases for [RADARSAT-2 content on GBDX](https://platform.digitalglobe.com/radarsat-2-content-gbdx/).\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/8b0856f-Hong_Kong_Adjusted_Image.jpg\",\n        \"Hong Kong Adjusted Image.jpg\",\n        2400,\n        2400,\n        \"#161516\"\n      ],\n      \"caption\": \"Hong Kong in Extra Fine, XF0W2\"\n    }\n  ]\n}\n[/block]\nDisclaimer: RADARSAT-2 Data and Products © MacDonald, Dettwiler and Associates Ltd. (2017). All Rights Reserved. RADARSAT is an official mark of the Canadian Space Agency.\n\nNote: In the GBDX Catalog, the \"types\" field does not accept special characters. In this case, we use \"RADARSAT2\" In all other cases, \"RADARSAT-2\" is used. \n\n# Accessing MDA RADARSAT-2 Data\nThe MDA RADARSAT-2 dataset on GBDX can be searched without an MDA contract. To run analytics using RADARSAT-2 data as inputs, an MDA package is required as part of the user's contract.  Once the MDA package contract has been signed, the access key and instructions will be sent to the account administrator. Additional users account users should contact their account administrator for access.\n[block:callout]\n{\n  \"type\": \"danger\",\n  \"title\": \"Your access key must not be published or hardcoded.\"\n}\n[/block]\n# MDA Acquisitions and Products\n\nIt's important to understand the difference between an MDA Acquisition and an MDA Product.\n\nAn MDA Acquisition is a capture from MDA's RADARSAT-2 satellite. An acquisition is the raw data from the capture. It's not an image yet. GBDX catalogs the acquisition data. \n\nAn MDA Product is a product made from an acquisition. If a product is cataloged on GBDX, the image is available. Only products can be used as input data for a task on the GBDX platform. \n\nNot every acquisition has a product in the catalog. However, products can be ordered for any acqusition cataloged on GBDX. See [Order MDA Products](#section-order-mda-products) for information on how to order products that are not currently available.\n\n# Types\n\nRecords are associated with one or more \"types\". Search by the most specific type that matches your criteria. For example, if you want all acquisitions and products available on GBDX from MDA's RADARSAT-2 platform , search by the type RADARSAT2. For MDA products, search by the type \"MDAProduct\". For acquisitions, search by \"MDAAcquisition\".\n\n## Product Types\nThese are the \"types\" associated with an MDA product record. \n\nType | Definition\n--- | ---\nGBDXCatalogRecord | The parent type for all GBDX catalog records\nRADARSAT2 | This type indicates all records acquired from the RADARSAT-2 sensor platform\nSGFProduct | This type indicates the SAR Georeferenced Fine product (also known as Path Image)\nMDAProduct | This type indicates all product records from MDA data sources\n\n## Acquisition Types\nThese are the \"types\" associated with an MDA acqusition record.\n\nType | Definition\n--- | ---\nGBDXCatalogRecord | The parent type for all GBDX catalog records\nAcquisition | The parent type for all acquisitions\nMDAAcquisition  | The type indicates all acquisition records from the RADARSAT-2 sensor platform\nRADARSAT2 | This type indicates all records acquired from the RADARSAT-2 sensor platform\n\n\n# Search \n\nUsing the GBDX Catalog API, search by \"types\" to find MDA  products and acquisitions.  To narrow the search results set, include area of interest, date range, or both. Search results can be further filtered by the properties of a a product or acquisition. \n\n## Catalog V2 API Request\n\nSend a ```POST``` request to ```https://geobigdata.io/catalog/v2/search``` with a request body. \n\nFor gbdxtools, see  <a href=\"http://gbdxtools.readthedocs.io/en/latest/catalog_search.html#catalog-search-overview\">Catalog Search Overview</a>\n\nTo use the Postman client to send a request directly to the API endpoint, see [Postman Instructions & Collections](doc:postman-instructions-collections) . The search examples below can be used as body text in the request.\n\n## Search Example 1: MDA Acquisition Search\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"   {  \\n    \\\"searchAreaWkt\\\": \\\"POLYGON ((-122.41189956665039 37.59415685597818, -122.41189956665039 37.64460175855099, -122.34529495239259 37.64460175855099, -122.34529495239259 37.59415685597818, -122.41189956665039 37.59415685597818))\\\",\\n     \\\"startDate\\\":\\\"2015-03-01T00:00:00.000Z\\\",\\n    \\\"endDate\\\":\\\"2016-03-01T23:59:59.999Z\\\",\\n    \\\"types\\\":[\\\"MDAAcquisition\\\"]\\n  }\\n\",\n      \"language\": \"json\"\n    }\n  ]\n}\n[/block]\n## Example MDA Acquisition Response\n\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"{\\n    \\\"identifier\\\": \\\"252032_001\\\",\\n    \\\"type\\\": [\\n        \\\"GBDXCatalogRecord\\\",\\n        \\\"Acquisition\\\",\\n        \\\"MDAAcquisition\\\",\\n        \\\"RADARSAT2\\\"\\n    ],\\n    \\\"properties\\\": {\\n        \\\"beamMode\\\": \\\"Extra Fine\\\",\\n        \\\"imgRelOrNo_dbl\\\": 35.622371326,\\n        \\\"archiveFac\\\": \\\"PASS\\\",\\n        \\\"vendor\\\": \\\"MacDonald, Dettwiler and Associates Ltd.\\\",\\n        \\\"timestamp\\\": \\\"2013-04-05T13:57:08.997Z\\\",\\n        \\\"beams\\\": \\\"XF0W2\\\",\\n        \\\"polarizations\\\": [\\n            \\\"HH\\\"\\n        ],\\n        \\\"archiveId\\\": \\\"233751\\\",\\n        \\\"footprintWkt\\\": \\\"MULTIPOLYGON(((-132.73335 -39.86666, -131.44159 -40.18248, -131.89179 -41.24695, -133.20203 -40.92627, -132.73335 -39.86666)))\\\",\\n        \\\"imageId\\\": \\\"252032\\\",\\n        \\\"sceneNo\\\": 1,\\n        \\\"sensorPlatformName\\\": \\\"RADARSAT-2\\\",\\n        \\\"incidenceAngleNearRange\\\": 31.87,\\n        \\\"passDirection\\\": \\\"Descending\\\",\\n        \\\"lookDirection\\\": \\\"Right\\\",\\n        \\\"catalogID\\\": \\\"252032\\\",\\n        \\\"platformName\\\": \\\"RADARSAT-2\\\",\\n        \\\"imgCycle\\\": 80\\n    }\\n}\",\n      \"language\": \"json\"\n    }\n  ]\n}\n[/block]\nSee the [Acquisition Properties](#section-acquisition-properties) table below for relevant acquisition fields and their descriptions. \n\n## Search Example 2:  MDA Product Search\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"   {  \\n    \\\"searchAreaWkt\\\": \\\"POLYGON ((-122.41189956665039 37.59415685597818, -122.41189956665039 37.64460175855099, -122.34529495239259 37.64460175855099, -122.34529495239259 37.59415685597818, -122.41189956665039 37.59415685597818))\\\",\\n     \\\"startDate\\\":\\\"2015-03-01T00:00:00.000Z\\\",\\n    \\\"endDate\\\":\\\"2016-03-01T23:59:59.999Z\\\",\\n    \\\"types\\\":[\\\"MDAProduct\\\"]\\n  }\",\n      \"language\": \"json\"\n    }\n  ]\n}\n[/block]\n## Example MDA Product Response\nThis example response shows the search statistics for the example search above, and the properties of a single product record. \n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"{\\n    \\\"stats\\\": {\\n        \\\"recordsReturned\\\": 25,\\n        \\\"totalRecords\\\": 25,\\n        \\\"typeCounts\\\": {\\n            \\\"GBDXCatalogRecord\\\": 25,\\n            \\\"RADARSAT2\\\": 25,\\n            \\\"SGFProduct\\\": 25,\\n            \\\"MDAProduct\\\": 25\\n        }\\n    },\\n    \\\"results\\\": [\\n        {\\n            \\\"identifier\\\": \\\"PDS_05963840\\\",\\n            \\\"type\\\": [\\n                \\\"GBDXCatalogRecord\\\",\\n                \\\"RADARSAT2\\\",\\n                \\\"SGFProduct\\\",\\n                \\\"MDAProduct\\\"\\n            ],\\n            \\\"properties\\\": {\\n                \\\"beamMode\\\": \\\"Extra Fine\\\",\\n                \\\"lutApplied\\\": \\\"Point Target\\\",\\n                \\\"processingTime\\\": \\\"2017-06-24T00:31:08.000000Z\\\",\\n                \\\"metadataFiles\\\": [\\n                    \\\"product.xml\\\"\\n                ],\\n                \\\"productID\\\": \\\"PDS_05963840\\\",\\n                \\\"timestamp\\\": \\\"2015-09-26T14:08:14.514Z\\\",\\n                \\\"catalogID\\\": \\\"424074\\\",\\n                \\\"imageFiles\\\": [\\n                    \\\"imagery_HH.tif\\\"\\n                ],\\n                \\\"passDirection\\\": \\\"Descending\\\",\\n                \\\"platformName\\\": \\\"RADARSAT-2\\\",\\n                \\\"polarizations\\\": [\\n                    \\\"HH\\\"\\n                ],\\n                \\\"vendor\\\": \\\"MacDonald, Dettwiler and Associates Ltd.\\\",\\n                \\\"lutFiles\\\": [\\n                    \\\"lutBeta.xml\\\",\\n                    \\\"lutSigma.xml\\\",\\n                    \\\"lutGamma.xml\\\"\\n                ],\\n                \\\"beams\\\": \\\"XF0W3\\\",\\n                \\\"bucketPrefix\\\": \\\"736300023a79da72b1238dc79ca0f6b5760800e999507099847468bcf8fce69bab312b9b5cf8bdc175ae6e8899cbf32bf421622611dd3c8a7a42905550780fef7b6cbf89e9b213843a5e896a730b71c04c96f248d188ef22eeae877db28bb64482b45f10ab5c9b5c61d624db55524796ea7e05f1d086f9693b5137aadad68bcb57f76e68a986b9cb2c1b79d5e83dc2b962cffd62fe686f1a0976a6635ae61fa5174b922bfc0f3615f39ee836c64dd16000957499da4f900ac7\\\",\\n                \\\"incidenceAngleFarRange_dbl\\\": 44.2717361,\\n                \\\"bucketName\\\": \\\"73630002b4532e22395755e58af20ea1e8172cc2071ee78c8937f4fcb1fda4591c1227dee7134c567d30b5439a068e37a8e49d8f86bafbfb43f945be559f1941dfe2206dd58c6ed3bce8a13c97ab3ec11d77f16de5949befa2cd25\\\",\\n                \\\"productLevel\\\": \\\"SGF\\\",\\n                \\\"incidenceAngleNearRange_dbl\\\": 38.1088181,\\n                \\\"footprintWkt\\\": \\\"MULTIPOLYGON(((-122.759388785 37.3960461199, -122.523402952 38.5092696551, -121.167566795 38.3247654766, -121.424551057 37.2106634407, -122.759388785 37.3960461199)))\\\",\\n                \\\"processingFacility\\\": \\\"GSS\\\",\\n                \\\"softwareVersion\\\": \\\"CAPPS SAR 1.3\\\",\\n                \\\"sensorPlatformName\\\": \\\"RADARSAT-2\\\",\\n                \\\"lookDirection\\\": \\\"Right\\\"\\n            }\\n        }\\n      \",\n      \"language\": \"json\"\n    }\n  ]\n}\n[/block]\n## Search Example 3:  search for RADARSAT-2 records (products and acquisitions)\n\nThis search returns MDA acquisitions and products.\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"  {  \\n    \\\"searchAreaWkt\\\": \\\"POLYGON ((-122.41189956665039 37.59415685597818, -122.41189956665039 37.64460175855099, -122.34529495239259 37.64460175855099, -122.34529495239259 37.59415685597818, -122.41189956665039 37.59415685597818))\\\",\\n     \\\"startDate\\\":\\\"2015-03-01T00:00:00.000Z\\\",\\n    \\\"endDate\\\":\\\"2016-03-01T23:59:59.999Z\\\",\\n    \\\"types\\\":[\\\"RADARSAT2\\\"]\\n  }\",\n      \"language\": \"json\"\n    }\n  ]\n}\n[/block]\n## Example statistics for a RADARSAT-2 search\n\nThese are the statistics for the search example above. Both MDA acquisitions and MDA products are returned in the result set. Each record will display the properties of its type. \n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"{\\n    \\\"stats\\\": {\\n        \\\"recordsReturned\\\": 34,\\n        \\\"totalRecords\\\": 34,\\n        \\\"typeCounts\\\": {\\n            \\\"MDAProduct\\\": 25,\\n            \\\"RADARSAT2\\\": 34,\\n            \\\"GBDXCatalogRecord\\\": 34,\\n            \\\"MDAAcquisition\\\": 9,\\n            \\\"SGFProduct\\\": 25,\\n            \\\"Acquisition\\\": 9\\n        }\\n    }\",\n      \"language\": \"json\"\n    }\n  ]\n}\n[/block]\n## Identifying Same Geometry Stacks\n\nMDA change detection algorithms require the identification of same geometry stacks before processing. See [Identifying Same Geometry Stacks](https://gbdxdocs.digitalglobe.com/v1/docs/mda-sar-amplitude-change-detection-end-to-end-workflow#section--a-name-identifying-same-gometry-stacks-a-identifying-same-geometry-stacks) for instructions. \n\n# Product Properties\n\nThese are the properties returned in an MDA Product search. Most of these properties can be used as filters to reduce search results. .\n\nProperty | Description | Values\n--- | --- | ---\nbeamMode |  Extra Fine (XF) beam mode data is available on GBDX |Extra Fine\nbeams | Beam Mnemonic describing beam mode and beam position. Extra Fine (XF) beam mode data is available on GBDX. |   Example: \"XF0W3\"        \nbucketName | The S3 prefix and S3 bucket name are encrypted. The GBDX decryption process is required to find the S3 location. | N/A \nbucketPrefix | The S3 prefix and S3 bucket name are encrypted. The GBDX decryption process is required to find the S3 location. | N/A\ncatalogID | This is the catalog ID assigned to the acquisition in the GBDX catalog. The imageID and catalogID are always the same for MDA data  | Ex: \"424074\"\nfootprintWKT | The well known text (wkt) POLYGON is used for searchAreaWkt searches. Other geometry types are not supported.  | See example \nImageFiles | The name of the image file or files for this product | Example:   imagery_HH.tif\nincidenceAngleFarRange_dbl | Incidence angle at far range at mid-azimuth position of the image.   | Example: 44.2646599  (units = deg)\nincidenceAngleNearRange_dbl Angle [degrees] between the vertical at swath center and the line from that point to the satellite when the satellite is broadside to the point.| Example: 38.3(units =deg) \nlookDirection | Spacecraft Orientation | \"left\" or \"right\"\nlutApplied | Output scaling LUT applied| string: for example, \"point target\"\nprocessingTime | Date/time at which processing was performed | Example format: \"2017-05-03T17:45:48.000000Z\"\nlutFiles | the xml files the lut metadata is derived from |     \"lutBeta.xml\", \"lutSigma.xml\", \"lutGamma.xml\"       \nmetadataFiles | meta data file that contains product information | product.xml\npassDirection | Direction of satellite pass defined at the start of the archive segment | Ascending or Descending\nplatformName | The name of the sensor platform that acquired the data | RADARSAT-2\npolarizations |Polarizations used to produce this product. The first letter is transmit polarization and the second letter is receive polarization | Polarization identifiers are “HH” “VV” “HV” “VH”\nproductID | The ID for the MDA product record |  Example: PDS_05778000\nproductLevel | The MDA product level for the record. | GBDX catalogs productLevel SGF\nprocessingFacility | Name of the processing facility which generated the product | GSS\nsoftwareVersion |Version of software used to process the data | CAPPS SAR 1.3\nsensorPlatformName | The name of the sensor platform that acquired the data | RADARSAT-2\ntimestamp | Date/time stamp of first raw data line used during the processing | Example: \"2013-04-10T04:27:31.823Z\"\nvendor | The vendor is the provider of the product data | MacDonald, Dettwiler and Associates Ltd.\n\n# Acquisition Properties\n\nProperty | Description | Values\n--- | --- | ---\narchiveFac | Archive Facility | \"PASS\", \"GATN\" or foreign archive\narchiveID | Identifier assigned by the archive facility | string; example: Identifier\nbeamMode | MDA's archive of Extra Fine beam mode data is available on GBDX |Extra Fine\nbeams | Beam Mnemonic describing beam mode and beam position. Extra Fine (XF) beam mode data is available on GBDX |  Example: \"XF0W3\"\ncatalogID | This is the catalog ID assigned to the acquisition in the GBDX catalog. The imageID and catalogID are always the same for MDA data | Example: 287688\nfootprintWKT | The well known text (wkt) POLYGON is used for searchAreaWkt searches. Other geometry types are not supported.  | \"MULTIPOLYGON(((-122.759388785 37.3960461199, -122.523402952 38.5092696551, -121.167566795 38.3247654766, -121.424551057 37.2106634407, -122.759388785 37.3960461199)))\"\nidentifier | This is the unique ID in the GBDX catalog for this record | The naming convention is <catalogID>_<sceneNo>. Example: 409017_001. \nimageID |This is MDA's identifier for this acquisition. imageID and catalogID are always the same for MDA data | Example: 287688\nimgCycle | Orbit cycle in which the image acquisition starts (343 orbits per 24-day cycle for RADARSAT-2) | Integer; Example: 146\nincidenceAngleNearRange | Angle [degrees] between the vertical at swath center and the line from that point to the satellite when the satellite is broadside to the point.   | Example: 38.3 (units =deg)\nlookDirection | Satellite orientation | \"left\" or \"right\"\npassDirection | Direction of satellite pass defined at the start of the archive segment | Ascending or Descending\nplatformName | The name of the sensor platform that acquired the data | RADARSAT-2\npolarizations |Polarizations used to produce this product. The first letter in the value is the transmit polarization. The second letter is the receive polarization. | Polarization identifiers are “HH” “VV” “HV” “VH”. See \"Polarizations\" below for polarization definitions.\nsceneNo | Scene number within segment, starting at 1 and incrementing by 1 for each scene. There can be multiple records with the same imageID, but each record will have a difference scene number. | Example: 1\nsensorPlatformName | The name of the sensor platform that acquired the image data. This field is identical to \"platformName\". | RADARSAT-2\ntimeStamp | Framed product segment start date/time in UTC: “yyyy-mm-ddThh:mm:ss.uuu” | Example:  \"2017-08-21T22:22:34.727Z\"\nvendor | The vendor is the provider of the data | MacDonald, Dettwiler and Associates Ltd.\n\n## Polarization Identifiers\n\nIdentifier | Description\n--- | ---\nHH | Horizontal polarization on transmit, Horizontal polarization on receive\nHV | Horizontal polarization on transmit, Vertical polarization on receive\nVH | Vertical polarization on transmit, Horizontal polarization on receive\nVV | Vertical polarization on transmit, Vertical polarization on receive\n\n\n\n\n\n\n##Acquisition Strip Example\n\nThis example shows the scenes that are part of an acquisition. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/620c531-acquisition_view.jpg\",\n        \"acquisition_view.jpg\",\n        1056,\n        816,\n        \"#e10505\"\n      ],\n      \"caption\": \"This example shows an acquisition with multiple scenes. The catalog ID is the same for each scene within the strip.\"\n    }\n  ]\n}\n[/block]\n# Order MDA Products\n\nWhen identifying a set of MDA data to use, we recommend searching for products in your Area of Interest. If the product data set for your AOI is not acceptable, GBDX MDA subscribers can place an order for additional products. \n\nTo order products, search for MDA acquisitions in your Area of Interest. Once you have identified the catalog IDs you want to order, send the following information to [**gbdx-support@digitalglobe.com** ](mailto:gbdx-support@digitalglobe.com) for each acquisition:\n\n* imageID\n* Date Range\n* The WKT for the Area of Interest\n\nExample:\n\n**imageID**\n52957\n\n**Date Range**\n\"startDate\": \"2014-06-01T12:00:00.000Z\",\n\"endDate\": \"2014-06-06T12:00:00.000Z\"\n\n\nAOI\n\"MULTIPOLYGON(((-122.759388785 37.3960461199, -122.523402952 38.5092696551, -121.167566795 38.3247654766, -121.424551057 37.2106634407, -122.759388785 37.3960461199)))\"\n\n# Find the S3 bucket location for an MDA Product\n\nFor MDA products, the AWS bucket name and bucket prefix are encrypted. You'll use your account's access key and decryption script to find the S3 url path to the product's location. If you need the access key, see your account administrator. \n\n# Run an MDA Task\nOnly RADARSAT-2 data can be used as input data for an MDA task. \n\nTo learn more about MDA's SAR Amplitude Change Detection Task, see [MDA® SAR Amplitude Change Detection End-to-End Workflow](doc:mda-sar-amplitude-change-detection-end-to-end-workflow)","excerpt":"","slug":"mda-radarsat-2","type":"basic","title":"MDA RADARSAT-2"}
# Table of Contents [block:parameters] { "data": { "h-0": "Section", "h-1": "Description", "0-0": "[Overview](#section-overview)", "0-1": "Overview of the MDA RADARSAT-2 extra-fine data set", "1-0": "[Accessing MDA RADARSAT-2 Data](#section-accessing-mda-radarsat-2-data)", "1-1": "An access key is required to get location information for MDA data. This section describes how this works", "2-0": "[MDA Acqusitions and Products](#section-mda-acquisitions-and-products)", "2-1": "This section describes acquisitions and products", "3-0": "[Types](#section-types)", "3-1": "This section describes the \"types\" used to identify MDA Acquisitions and Products", "4-0": "[Search](#section-search)", "4-1": "This section describes how to search for MDA Acquisitions and Products, and provides examples of a search and response", "5-0": "[MDA Product Properties](#section-product-properties)", "5-1": "This section defines the properties of an MDA product", "6-0": "[MDA Acquisition Properties](#section-acquisition-properties)", "6-1": "This section defines the properties of an MDA Acquisition", "7-0": "[Order MDA Products](#section-order-mda-products)", "7-1": "This section describes how to order MDA products that are not already available in the GBDX product catalog", "8-0": "[Find the S3 bucket location for an MDA Product](#section-find-the-s3-bucket-location-for-an-mda-product)", "8-1": "The S3 bucket location is encrypted, and is only available to customers who purchase the MDA package. Learn more.", "9-0": "[Run an MDA Task](#section-run-an-mda-task)", "9-1": "This section identifies algorithms that can run with MDA data on GBDX" }, "cols": 2, "rows": 10 } [/block] # Overview The MacDonald, Dettwiler and Associates Ltd. (MDA) RADARSAT-2 satellite provides high-resolution, operationally focused synthetic aperture radar (SAR) data regardless of cloud cover or light conditions. With unique feature classification capabilities, this dataset allows users to observe features and changes in the environment that would go undetected using other imaging techniques. RADARSAT-2 images the Earth at spatial resolutions ranging from 1 to 100 metres, providing coverage from 144 to 250,000 km<sup>2</sup> in a single scene. Access to the global archive of Extra-Fine beam mode imagery is provided via GBDX. MDA has integrated a synthetic aperture radar (SAR) change detection tool into GBDX that will enable amplitude change detection to be performed on RADARSAT-2 imagery. **Uses** Users will be able to extract location intelligence at scale, and create reliably collected change detection value-added products on the platform. Unlocked capabilities include automated port monitoring, object detection, and broad area change monitoring. **Spectral Bands**: Extra Fine Beam Mode **Date Range**: March 2013 to present **Products available through GBDX**: RADARSAT-2 Extra-fine beam mode dataset (SGF Format) **GBDX MDA Package:** The GBDX MDA package can be added to an existing GBDX contract, or purchased as a stand-alone product. For more information on this offering, contact [**gbdx-support@digitalglobe.com** ](mailto:gbdx-support@digitalglobe.com). Learn more about use cases for [RADARSAT-2 content on GBDX](https://platform.digitalglobe.com/radarsat-2-content-gbdx/). [block:image] { "images": [ { "image": [ "https://files.readme.io/8b0856f-Hong_Kong_Adjusted_Image.jpg", "Hong Kong Adjusted Image.jpg", 2400, 2400, "#161516" ], "caption": "Hong Kong in Extra Fine, XF0W2" } ] } [/block] Disclaimer: RADARSAT-2 Data and Products © MacDonald, Dettwiler and Associates Ltd. (2017). All Rights Reserved. RADARSAT is an official mark of the Canadian Space Agency. Note: In the GBDX Catalog, the "types" field does not accept special characters. In this case, we use "RADARSAT2" In all other cases, "RADARSAT-2" is used. # Accessing MDA RADARSAT-2 Data The MDA RADARSAT-2 dataset on GBDX can be searched without an MDA contract. To run analytics using RADARSAT-2 data as inputs, an MDA package is required as part of the user's contract. Once the MDA package contract has been signed, the access key and instructions will be sent to the account administrator. Additional users account users should contact their account administrator for access. [block:callout] { "type": "danger", "title": "Your access key must not be published or hardcoded." } [/block] # MDA Acquisitions and Products It's important to understand the difference between an MDA Acquisition and an MDA Product. An MDA Acquisition is a capture from MDA's RADARSAT-2 satellite. An acquisition is the raw data from the capture. It's not an image yet. GBDX catalogs the acquisition data. An MDA Product is a product made from an acquisition. If a product is cataloged on GBDX, the image is available. Only products can be used as input data for a task on the GBDX platform. Not every acquisition has a product in the catalog. However, products can be ordered for any acqusition cataloged on GBDX. See [Order MDA Products](#section-order-mda-products) for information on how to order products that are not currently available. # Types Records are associated with one or more "types". Search by the most specific type that matches your criteria. For example, if you want all acquisitions and products available on GBDX from MDA's RADARSAT-2 platform , search by the type RADARSAT2. For MDA products, search by the type "MDAProduct". For acquisitions, search by "MDAAcquisition". ## Product Types These are the "types" associated with an MDA product record. Type | Definition --- | --- GBDXCatalogRecord | The parent type for all GBDX catalog records RADARSAT2 | This type indicates all records acquired from the RADARSAT-2 sensor platform SGFProduct | This type indicates the SAR Georeferenced Fine product (also known as Path Image) MDAProduct | This type indicates all product records from MDA data sources ## Acquisition Types These are the "types" associated with an MDA acqusition record. Type | Definition --- | --- GBDXCatalogRecord | The parent type for all GBDX catalog records Acquisition | The parent type for all acquisitions MDAAcquisition | The type indicates all acquisition records from the RADARSAT-2 sensor platform RADARSAT2 | This type indicates all records acquired from the RADARSAT-2 sensor platform # Search Using the GBDX Catalog API, search by "types" to find MDA products and acquisitions. To narrow the search results set, include area of interest, date range, or both. Search results can be further filtered by the properties of a a product or acquisition. ## Catalog V2 API Request Send a ```POST``` request to ```https://geobigdata.io/catalog/v2/search``` with a request body. For gbdxtools, see <a href="http://gbdxtools.readthedocs.io/en/latest/catalog_search.html#catalog-search-overview">Catalog Search Overview</a> To use the Postman client to send a request directly to the API endpoint, see [Postman Instructions & Collections](doc:postman-instructions-collections) . The search examples below can be used as body text in the request. ## Search Example 1: MDA Acquisition Search [block:code] { "codes": [ { "code": " { \n \"searchAreaWkt\": \"POLYGON ((-122.41189956665039 37.59415685597818, -122.41189956665039 37.64460175855099, -122.34529495239259 37.64460175855099, -122.34529495239259 37.59415685597818, -122.41189956665039 37.59415685597818))\",\n \"startDate\":\"2015-03-01T00:00:00.000Z\",\n \"endDate\":\"2016-03-01T23:59:59.999Z\",\n \"types\":[\"MDAAcquisition\"]\n }\n", "language": "json" } ] } [/block] ## Example MDA Acquisition Response [block:code] { "codes": [ { "code": "{\n \"identifier\": \"252032_001\",\n \"type\": [\n \"GBDXCatalogRecord\",\n \"Acquisition\",\n \"MDAAcquisition\",\n \"RADARSAT2\"\n ],\n \"properties\": {\n \"beamMode\": \"Extra Fine\",\n \"imgRelOrNo_dbl\": 35.622371326,\n \"archiveFac\": \"PASS\",\n \"vendor\": \"MacDonald, Dettwiler and Associates Ltd.\",\n \"timestamp\": \"2013-04-05T13:57:08.997Z\",\n \"beams\": \"XF0W2\",\n \"polarizations\": [\n \"HH\"\n ],\n \"archiveId\": \"233751\",\n \"footprintWkt\": \"MULTIPOLYGON(((-132.73335 -39.86666, -131.44159 -40.18248, -131.89179 -41.24695, -133.20203 -40.92627, -132.73335 -39.86666)))\",\n \"imageId\": \"252032\",\n \"sceneNo\": 1,\n \"sensorPlatformName\": \"RADARSAT-2\",\n \"incidenceAngleNearRange\": 31.87,\n \"passDirection\": \"Descending\",\n \"lookDirection\": \"Right\",\n \"catalogID\": \"252032\",\n \"platformName\": \"RADARSAT-2\",\n \"imgCycle\": 80\n }\n}", "language": "json" } ] } [/block] See the [Acquisition Properties](#section-acquisition-properties) table below for relevant acquisition fields and their descriptions. ## Search Example 2: MDA Product Search [block:code] { "codes": [ { "code": " { \n \"searchAreaWkt\": \"POLYGON ((-122.41189956665039 37.59415685597818, -122.41189956665039 37.64460175855099, -122.34529495239259 37.64460175855099, -122.34529495239259 37.59415685597818, -122.41189956665039 37.59415685597818))\",\n \"startDate\":\"2015-03-01T00:00:00.000Z\",\n \"endDate\":\"2016-03-01T23:59:59.999Z\",\n \"types\":[\"MDAProduct\"]\n }", "language": "json" } ] } [/block] ## Example MDA Product Response This example response shows the search statistics for the example search above, and the properties of a single product record. [block:code] { "codes": [ { "code": "{\n \"stats\": {\n \"recordsReturned\": 25,\n \"totalRecords\": 25,\n \"typeCounts\": {\n \"GBDXCatalogRecord\": 25,\n \"RADARSAT2\": 25,\n \"SGFProduct\": 25,\n \"MDAProduct\": 25\n }\n },\n \"results\": [\n {\n \"identifier\": \"PDS_05963840\",\n \"type\": [\n \"GBDXCatalogRecord\",\n \"RADARSAT2\",\n \"SGFProduct\",\n \"MDAProduct\"\n ],\n \"properties\": {\n \"beamMode\": \"Extra Fine\",\n \"lutApplied\": \"Point Target\",\n \"processingTime\": \"2017-06-24T00:31:08.000000Z\",\n \"metadataFiles\": [\n \"product.xml\"\n ],\n \"productID\": \"PDS_05963840\",\n \"timestamp\": \"2015-09-26T14:08:14.514Z\",\n \"catalogID\": \"424074\",\n \"imageFiles\": [\n \"imagery_HH.tif\"\n ],\n \"passDirection\": \"Descending\",\n \"platformName\": \"RADARSAT-2\",\n \"polarizations\": [\n \"HH\"\n ],\n \"vendor\": \"MacDonald, Dettwiler and Associates Ltd.\",\n \"lutFiles\": [\n \"lutBeta.xml\",\n \"lutSigma.xml\",\n \"lutGamma.xml\"\n ],\n \"beams\": \"XF0W3\",\n \"bucketPrefix\": \"736300023a79da72b1238dc79ca0f6b5760800e999507099847468bcf8fce69bab312b9b5cf8bdc175ae6e8899cbf32bf421622611dd3c8a7a42905550780fef7b6cbf89e9b213843a5e896a730b71c04c96f248d188ef22eeae877db28bb64482b45f10ab5c9b5c61d624db55524796ea7e05f1d086f9693b5137aadad68bcb57f76e68a986b9cb2c1b79d5e83dc2b962cffd62fe686f1a0976a6635ae61fa5174b922bfc0f3615f39ee836c64dd16000957499da4f900ac7\",\n \"incidenceAngleFarRange_dbl\": 44.2717361,\n \"bucketName\": \"73630002b4532e22395755e58af20ea1e8172cc2071ee78c8937f4fcb1fda4591c1227dee7134c567d30b5439a068e37a8e49d8f86bafbfb43f945be559f1941dfe2206dd58c6ed3bce8a13c97ab3ec11d77f16de5949befa2cd25\",\n \"productLevel\": \"SGF\",\n \"incidenceAngleNearRange_dbl\": 38.1088181,\n \"footprintWkt\": \"MULTIPOLYGON(((-122.759388785 37.3960461199, -122.523402952 38.5092696551, -121.167566795 38.3247654766, -121.424551057 37.2106634407, -122.759388785 37.3960461199)))\",\n \"processingFacility\": \"GSS\",\n \"softwareVersion\": \"CAPPS SAR 1.3\",\n \"sensorPlatformName\": \"RADARSAT-2\",\n \"lookDirection\": \"Right\"\n }\n }\n ", "language": "json" } ] } [/block] ## Search Example 3: search for RADARSAT-2 records (products and acquisitions) This search returns MDA acquisitions and products. [block:code] { "codes": [ { "code": " { \n \"searchAreaWkt\": \"POLYGON ((-122.41189956665039 37.59415685597818, -122.41189956665039 37.64460175855099, -122.34529495239259 37.64460175855099, -122.34529495239259 37.59415685597818, -122.41189956665039 37.59415685597818))\",\n \"startDate\":\"2015-03-01T00:00:00.000Z\",\n \"endDate\":\"2016-03-01T23:59:59.999Z\",\n \"types\":[\"RADARSAT2\"]\n }", "language": "json" } ] } [/block] ## Example statistics for a RADARSAT-2 search These are the statistics for the search example above. Both MDA acquisitions and MDA products are returned in the result set. Each record will display the properties of its type. [block:code] { "codes": [ { "code": "{\n \"stats\": {\n \"recordsReturned\": 34,\n \"totalRecords\": 34,\n \"typeCounts\": {\n \"MDAProduct\": 25,\n \"RADARSAT2\": 34,\n \"GBDXCatalogRecord\": 34,\n \"MDAAcquisition\": 9,\n \"SGFProduct\": 25,\n \"Acquisition\": 9\n }\n }", "language": "json" } ] } [/block] ## Identifying Same Geometry Stacks MDA change detection algorithms require the identification of same geometry stacks before processing. See [Identifying Same Geometry Stacks](https://gbdxdocs.digitalglobe.com/v1/docs/mda-sar-amplitude-change-detection-end-to-end-workflow#section--a-name-identifying-same-gometry-stacks-a-identifying-same-geometry-stacks) for instructions. # Product Properties These are the properties returned in an MDA Product search. Most of these properties can be used as filters to reduce search results. . Property | Description | Values --- | --- | --- beamMode | Extra Fine (XF) beam mode data is available on GBDX |Extra Fine beams | Beam Mnemonic describing beam mode and beam position. Extra Fine (XF) beam mode data is available on GBDX. | Example: "XF0W3" bucketName | The S3 prefix and S3 bucket name are encrypted. The GBDX decryption process is required to find the S3 location. | N/A bucketPrefix | The S3 prefix and S3 bucket name are encrypted. The GBDX decryption process is required to find the S3 location. | N/A catalogID | This is the catalog ID assigned to the acquisition in the GBDX catalog. The imageID and catalogID are always the same for MDA data | Ex: "424074" footprintWKT | The well known text (wkt) POLYGON is used for searchAreaWkt searches. Other geometry types are not supported. | See example ImageFiles | The name of the image file or files for this product | Example: imagery_HH.tif incidenceAngleFarRange_dbl | Incidence angle at far range at mid-azimuth position of the image. | Example: 44.2646599 (units = deg) incidenceAngleNearRange_dbl Angle [degrees] between the vertical at swath center and the line from that point to the satellite when the satellite is broadside to the point.| Example: 38.3(units =deg) lookDirection | Spacecraft Orientation | "left" or "right" lutApplied | Output scaling LUT applied| string: for example, "point target" processingTime | Date/time at which processing was performed | Example format: "2017-05-03T17:45:48.000000Z" lutFiles | the xml files the lut metadata is derived from | "lutBeta.xml", "lutSigma.xml", "lutGamma.xml" metadataFiles | meta data file that contains product information | product.xml passDirection | Direction of satellite pass defined at the start of the archive segment | Ascending or Descending platformName | The name of the sensor platform that acquired the data | RADARSAT-2 polarizations |Polarizations used to produce this product. The first letter is transmit polarization and the second letter is receive polarization | Polarization identifiers are “HH” “VV” “HV” “VH” productID | The ID for the MDA product record | Example: PDS_05778000 productLevel | The MDA product level for the record. | GBDX catalogs productLevel SGF processingFacility | Name of the processing facility which generated the product | GSS softwareVersion |Version of software used to process the data | CAPPS SAR 1.3 sensorPlatformName | The name of the sensor platform that acquired the data | RADARSAT-2 timestamp | Date/time stamp of first raw data line used during the processing | Example: "2013-04-10T04:27:31.823Z" vendor | The vendor is the provider of the product data | MacDonald, Dettwiler and Associates Ltd. # Acquisition Properties Property | Description | Values --- | --- | --- archiveFac | Archive Facility | "PASS", "GATN" or foreign archive archiveID | Identifier assigned by the archive facility | string; example: Identifier beamMode | MDA's archive of Extra Fine beam mode data is available on GBDX |Extra Fine beams | Beam Mnemonic describing beam mode and beam position. Extra Fine (XF) beam mode data is available on GBDX | Example: "XF0W3" catalogID | This is the catalog ID assigned to the acquisition in the GBDX catalog. The imageID and catalogID are always the same for MDA data | Example: 287688 footprintWKT | The well known text (wkt) POLYGON is used for searchAreaWkt searches. Other geometry types are not supported. | "MULTIPOLYGON(((-122.759388785 37.3960461199, -122.523402952 38.5092696551, -121.167566795 38.3247654766, -121.424551057 37.2106634407, -122.759388785 37.3960461199)))" identifier | This is the unique ID in the GBDX catalog for this record | The naming convention is <catalogID>_<sceneNo>. Example: 409017_001. imageID |This is MDA's identifier for this acquisition. imageID and catalogID are always the same for MDA data | Example: 287688 imgCycle | Orbit cycle in which the image acquisition starts (343 orbits per 24-day cycle for RADARSAT-2) | Integer; Example: 146 incidenceAngleNearRange | Angle [degrees] between the vertical at swath center and the line from that point to the satellite when the satellite is broadside to the point. | Example: 38.3 (units =deg) lookDirection | Satellite orientation | "left" or "right" passDirection | Direction of satellite pass defined at the start of the archive segment | Ascending or Descending platformName | The name of the sensor platform that acquired the data | RADARSAT-2 polarizations |Polarizations used to produce this product. The first letter in the value is the transmit polarization. The second letter is the receive polarization. | Polarization identifiers are “HH” “VV” “HV” “VH”. See "Polarizations" below for polarization definitions. sceneNo | Scene number within segment, starting at 1 and incrementing by 1 for each scene. There can be multiple records with the same imageID, but each record will have a difference scene number. | Example: 1 sensorPlatformName | The name of the sensor platform that acquired the image data. This field is identical to "platformName". | RADARSAT-2 timeStamp | Framed product segment start date/time in UTC: “yyyy-mm-ddThh:mm:ss.uuu” | Example: "2017-08-21T22:22:34.727Z" vendor | The vendor is the provider of the data | MacDonald, Dettwiler and Associates Ltd. ## Polarization Identifiers Identifier | Description --- | --- HH | Horizontal polarization on transmit, Horizontal polarization on receive HV | Horizontal polarization on transmit, Vertical polarization on receive VH | Vertical polarization on transmit, Horizontal polarization on receive VV | Vertical polarization on transmit, Vertical polarization on receive ##Acquisition Strip Example This example shows the scenes that are part of an acquisition. [block:image] { "images": [ { "image": [ "https://files.readme.io/620c531-acquisition_view.jpg", "acquisition_view.jpg", 1056, 816, "#e10505" ], "caption": "This example shows an acquisition with multiple scenes. The catalog ID is the same for each scene within the strip." } ] } [/block] # Order MDA Products When identifying a set of MDA data to use, we recommend searching for products in your Area of Interest. If the product data set for your AOI is not acceptable, GBDX MDA subscribers can place an order for additional products. To order products, search for MDA acquisitions in your Area of Interest. Once you have identified the catalog IDs you want to order, send the following information to [**gbdx-support@digitalglobe.com** ](mailto:gbdx-support@digitalglobe.com) for each acquisition: * imageID * Date Range * The WKT for the Area of Interest Example: **imageID** 52957 **Date Range** "startDate": "2014-06-01T12:00:00.000Z", "endDate": "2014-06-06T12:00:00.000Z" AOI "MULTIPOLYGON(((-122.759388785 37.3960461199, -122.523402952 38.5092696551, -121.167566795 38.3247654766, -121.424551057 37.2106634407, -122.759388785 37.3960461199)))" # Find the S3 bucket location for an MDA Product For MDA products, the AWS bucket name and bucket prefix are encrypted. You'll use your account's access key and decryption script to find the S3 url path to the product's location. If you need the access key, see your account administrator. # Run an MDA Task Only RADARSAT-2 data can be used as input data for an MDA task. To learn more about MDA's SAR Amplitude Change Detection Task, see [MDA® SAR Amplitude Change Detection End-to-End Workflow](doc:mda-sar-amplitude-change-detection-end-to-end-workflow)