Planet to Google Earth Engine Pipeline (Command Line Interface)
No Thumbnail Available
Can’t use the file because of accessibility barriers? Contact us with the title of the item, permanent link, and specifics of your accommodation need.
Date
2017-08-13
Authors
Journal Title
Journal ISSN
Volume Title
Publisher
Zenodo
Permanent Link
Abstract
While moving between assets from Planet Inc and Google Earth Engine it was imperative to create a pipeline that allows for easy transitions between the two service end points and this tool is designed to act as a step by step process chain from Planet Assets to batch upload and modification within the Google Earth Engine environment. The ambition is apart from helping user with batch actions on assets along with interacting and extending capabilities of existing GEE CLI. It is developed case by case basis to include more features in the future as it becomes available or as need arises. Planet assets were used as a potential platform test-bed and the tool now includes manifests to handle additional assets such as Digital Globe, Arctic-DEM and other assets will be added as metadata information becomes available. This release also contains a windows installer which bypasses the need for you to have admin permission, it does however require you to have python in the system path.
Description
Keywords
Google Earth Engine, Remote Sensing, Satellite Imagery, Batch Processing,Planet Labs, Python
Citation
Samapriya Roy. (2017, August 13). samapriya/Planet-GEE-Pipeline-CLI: Planet-GEE-Pipeline-CLI. Zenodo. http://doi.org/10.5281/zenodo.842078
Journal
Link(s) to data and video for this item
Relation
Rights
Apache License,Version 2.0, January 2004 (http://www.apache.org/licenses/LICENSE-2.0). A licensee of Apache Licensed V2 software can: copy, modify and distribute the covered software in source and/or binary forms, exercise patent rights that would normally only extend to the licensor provided that: all copies, modified or unmodified, are accompanied by a copy of the license, all modifications are clearly marked as being the work of the modifier, all notices of copyright, trademark and patent rights are reproduced accurately in distributed copies, the licensee does not use any trademarks that belong to the licensor. Furthermore, the grant of patent rights specifically is withdrawn if: the licensee starts legal action against the licensor(s) over patent infringements within the covered software This rewriting of the BSD licence tries to achieve a few things. Firstly it adds an explicit grant of patent rights where that is needed to operate, modify and distribute the software. Some argue that such a grant is implicit in other open source licences, but the Apache License v2 spells it out, as well as explicitly withdrawing that grant in the circumstance mentioned above. It also contains solid definitions of the concepts it uses, providing more certainty as to its intended meaning. Among these is a definition of Contributor that contains another interesting feature of the licence. A Contributor, as distinct from someone who just modifies the software, also grants a licence to their modification back to the original authors. This mechanism, if taken up, simplifies control of the code. Finally the v2 licence is usable by other projects without the need to replace wording in the licence document itself.
Type
Software