pip3 install pipenv
pipenv shell
| import matplotlib.pyplot as plt | |
| import rasterio | |
| from rasterio.windows import Window | |
| import time | |
| import zarr | |
| def convert(raster_filepath, chunk_mbs=1): | |
| """ | |
| Converts raster file to chunked and compressed zarr array. Tested |
| from __future__ import print_function | |
| import requests | |
| import json | |
| import cv2 | |
| addr = 'http://localhost:5000' | |
| test_url = addr + '/api/test' | |
| # prepare headers for http request | |
| content_type = 'image/jpeg' |
| { | |
| "CoolProp": "https://pypi.python.org/packages/17/71/0bfbaed4d1eeb0fd339827e203e8abfbb1b29c82e65bd25a87473fa275a0/CoolProp-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl", | |
| "Cython": "https://pypi.python.org/packages/7d/f1/ef21dc8cfc1deb5efc6d5260bcfe5892d0482972ab851ec577ad40bba67c/Cython-0.24.1-cp27-cp27mu-manylinux1_x86_64.whl", | |
| "Pillow": "https://pypi.python.org/packages/f5/cc/6ed6df9eb1cbe0153e0897a62b6e72560faef13fa4891c143a965374ac4a/Pillow-3.4.1-cp27-cp27mu-manylinux1_x86_64.whl", | |
| "PyLBFGS": "https://pypi.python.org/packages/82/3a/1f6eacc68ad1125efbdcd5dca004cf6ef3bbd3cafc28bb98e2d6b68a2bb0/PyLBFGS-0.2.0.3-cp27-cp27mu-manylinux1_x86_64.whl", | |
| "Pygame": "https://pypi.python.org/packages/4c/91/531fa68e07c4a94a657177494688ef40c5a371a46e5ecb40c2175832d7ff/pygame-1.9.2b8-cp27-cp27mu-manylinux1_x86_64.whl", | |
| "RelStorage": "https://pypi.python.org/packages/3a/a2/a4741cf61a9b0f0eb0f7cf343822602afa13911a43934fee2838f2ee4309/RelStorage-2.0.0b8-cp27-cp27mu-manylinux1_x86_64.whl", | |
| "Shapely": "https://pypi.py |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j