You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be a great idea to have a cohesive, statewide 1 meter lidar dataset for cartographic and other uses where the overall appearance and ease of use is more important than maintaining the exact values from each project.
I see a couple different steps to create this:
Figure out a tiling index
Figure out how to deal with overlaps between projects- most recent, averaging, distance-weighed average, etc
Figure out resampling of 0.5m lidar tiles
Figure out storage- costs, does it make sense to reference existing data as much as possible, etc
Figure out a processing framework- local, Global Mapper, GCP, etc
The text was updated successfully, but these errors were encountered:
I am behind a new statewide UGRC 1 Meter dataset and that is why I started messing with the national grid to come up with some tiling ideas. I was really surprise with my first test to merge ~1200 tiles in that it took less then 10 minutes to output a ~9gb file from Global Mapper. It is possible the data could be more compressed but it was just a first test run where I expected it to blow up. We should talk more but my idea to create 106-50Km/sq tiles which seems reasonable and I think it cold solve a lot of folk's pain points.
Here is an image of what I am talking about. I created topology on the lidar extents and the few large pink areas denote project overlap where we would choose which dataset would be used and it could also become sort of a metadata to track the lineage of the new 1 meter dataset:
I think it would be a great idea to have a cohesive, statewide 1 meter lidar dataset for cartographic and other uses where the overall appearance and ease of use is more important than maintaining the exact values from each project.
I see a couple different steps to create this:
The text was updated successfully, but these errors were encountered: