Postholer - Hiking & GIS

The masses label us lonely, because they need continued validation, from everyone.

It never ends.

What others have said.

This is a city planning issue and a long-standing pursuit of property taxes. These lands need to be vacated and were *never* suited to development.

Throwing more money at denial is not even remotely the answer.

Nope, it's the real deal. Andrew documented the entire shot on youtube. Pretty amazing. He's got tons of photo like this, moon, space station, sun, etc.

Here's the 11/13 23:00 3 day NBM QPF forecast compared to actual precip. Red means NBM over-stated (in inches):

#Kate thank you very much! :)

Un mot, AdBlockPlus :)

Anyone notice a massive increase of bad internet traffic coming from South America over the last few months?

Here's looking at you #Brazil:

www.femafhz.com/map/-17.9518...

#gis #osint

Reason #387 why killing Israeli's is a bad idea.

Roll your own without hosting any DEM data or 3rd party dependencies, using GDAL and Sentinel data on AWS. Add the following to your server side API:

#maps #gis

That was Carl Sagan's speculation in the book 'Contact'. They're already communicating with us, we're just too dumb to figure it out.

Here's an interactive map with the same data. Double-click anywhere to get the annual precipitation for an exact location:

www.femafhz.com/map/48.62379...

GDAL CLI version 3.12.0 is out!

#gdal #gis #MtHood

Negotiate === concede

Nothing is more traditional than python?

Python spatial and all its package baggage are built on top of GDAL. Cut out the middleman and use 'gdal ....' to create/edit ALL your raster/vector data directly.

(Looking at you, too, ESRI)

Comparison of NBM QPF (precipitation) forecast model vs actual QPF amounts, for 2 events, Oct 24-27 and Nov 04-06 2025 along the California north coast. Consistency is an issue. @nws.noaa.gov #weather #california

"the dog catching the car"

National Risk Index, Riverine Flooding - Expected Annual Loss Rate - National Percentile shown. Choose category by state, county or census tract #polygons.

www.femafhz.com/map/35.13787...

#30DayMapChallenge

a century of glaciers melting 🧪🌐

Using PostGIS ST_LineInterpolatePoints to evenly get points from line features (roads) and ST_ClusterDBScan to get (mostly) non-overlapping points for road shields on interactive map.

Using only st_clusterdbscan for non-overlaping GNIS place names.

#30DayMapChallenge #points #postgis #leafletjs

AMD, Department of Energy announce $1 billion AI supercomputer partnership New supercomputer clusters are headed to Tennessee.

Sorry, no boom, just bits:

www.theverge.com/news/807483/...

AMD, Department of Energy announce $1 billion AI supercomputer partnership New supercomputer clusters are headed to Tennessee.

Sorry, no boom, just bits:

www.theverge.com/news/807483/...

Seems like the guy from AWS last week found new employment.

Geosynchronous-LEO. Cool! ;)

Here's a National Risk Index map for those disasters, except interactive, at state, county, census tract level for 24 different categories and 20+ metrics, percentile, expected annual loss, etc ,etc. 2022 data.

Riverine Flooding shown:
www.femafhz.com/map/36.98500...

Fully interactive map of #Melissa, with the most up-to-date NHC data:

www.femafhz.com/map/19.43551...

Here's the same result using only #GDAL, cutting out the python nastiness:

Simplify:
gdal vector simplify --input=states.gpkg --tolerance=.5 --output=simple.gpkg

Clean coverage:
gdal vector clean-coverage --input=simple.gpkg --snapping-distance=.7 --output=clleaned.gpkg

#Melissa Cat 2-4, Sun 8am to Tues 8am, with Jamaica on the right hand side of the storm, 50km away. Brutal.

www.femafhz.com/map/17.66233...

kdp.amazon.com

On demand printing, no limit on # of copies. Print or eBook. Guidelines exist that can make it daunting. Not a small task. I've been using KDP for 10+ years:

www.postholer.com/maps/Pacific...

Not true. How much data will you fetch from an internet web-server?

The network and the client's ability to process is the limitation, NOT the FGB/COG format. How is shoving 50MB of vector data into an app/browser over the internet useful?

Parquet tooling is a problem, not a solution.

Why bother with Sedona/spark/duckdb/arrow overhead, if you're doing bbox range requests?

People need to understand, for bbox spatial queries, web server range requests and the proper file format, FGB/COG, are ideal.

Need a non-spatial attribute query? Great! Use the overhead you're suggesting.