Ian Dees

Starting on 2m terrain model, looks like there are 5,679 images to grab: ``` curl -s https://raw.githubusercontent.com/iandees/uk-lidar/master/catalog.csv \ | grep LIDAR-DTM-2M-ENGLAND-EA-MD-YY \ | wc -l ``` #### Mirroring data ```...

At this point I tried opening one of these files to verify that the transcode process will be able to handle it. It turns out each of the .zip files...

Over the weekend I added a few scripts to [my uk-lidar repo](https://github.com/iandees/uk-lidar/tree/master/dem_composite) to assist with this. I processed the .zip's of .asc's into .tif's and started merging them into larger...

I completed the process to convert, merge, and upload the 2m LIDAR-based data from the UK and documented it here: https://github.com/iandees/uk-lidar/blob/master/dem_composite/README.md #### Transcode files ``` aws s3 ls s3://elevation-sources-prod/uk_lidar/ --recursive...

I finished transcoding and loading footprints to get this:  The data looked great, but there was a large chunk of data missing in the lower right. I re-downloaded and...

> There's also LIDAR data for Wales and Scotland's is due any time now. Shall I create new issues for them? Yes! The more data the better.

I've been poking at it for a while and haven't found a nice way to do it.

I've spent a couple hours trying to find the CRS for this data and haven't found anything that seems to work. Based on the "DATUM" attribute on an entry like...

Did a bunch of pre-processing (similar to the UK data) documented in this new repo: https://github.com/iandees/mx-lidar #### Transcode files ``` aws s3 ls s3://elevation-sources-prod/mx_lidar/ --recursive | \ grep .tif$ |...

The transcoding finished and we ended up with 2,516 footprints in the database. This doesn't come close to covering Mexico, though:  [This regex filter](https://github.com/iandees/mx-lidar/blob/master/list_urls.py#L23) in the URL listing step...