yeah, I agree. Having a single organization promoting dozens of competing, unused standards seems like an obvious failure

Of course, there's plenty of commercial products that market themselves on the back of "implements over XX OGC standards", so the system is actually working as designed...

anyway, this all is inspired by seeing tipg specifically mention that they "chose to avoid implementing the second part of the specification to prevent the introduction of CRS-based GeoJSON"

overall, features is great! part 2... less so.

github.com/developments...

standards promote interoperability, which is why we're telling your users to not share their downloaded data with anyone unless they tell them it's broken

we also will not give you any guidance on how to tell people it's broken

not to mention this means 30 characters of every request get taken up by the static URL

and also not to mention that, if a CRS specifies y/x axis order, the standard says to write your geojson with this incorrect order and explicitly does NOT say how to tell users about the bad formatting

they mandate CRS identifiers be specified as "http://www.opengis.net/def/crs/{authority}/{version}/{code}"

why this couldn't just be authority:code is absolutely beyond me, particularly when opengis is seriously incomplete with only EPSG CRS included

this has to be too clever for bluesky right

We keep delaying until we're more confident our jobs are stable 🤷🏼‍♂️

senior author only read the methods when you're ready to submit, and they have some "useful" suggestions

Amendment to the NDAA. Still seems like a crazy thing to not be a stand-alone bill, except that we don't really do those anymore
www.congress.gov/amendment/11...

...I'm going to look this up in a minute, but amendment to what? Seems like a wild tag-on

@ridebluebikes.bsky.social if y'all are taking feature requests....

The Alhambra is unreal. Can't recommend enough.

Maine has a lot of gall talking about traffic when route 1 and Wiscasset exist

my recent focus has been on a lot of point time series data -- I _think_ someone told me zarr handles this use case well enough, but honestly I've only seriously played with parquet so far

my most charitable opinion is that I also don't love that basically all software engineering currently requires using bespoke tooling and renting clock time from 1 of 3 corps

but that does mean that everyone everywhere needs tools for dealing with those corp's tech... not just the hyperscalers

this sent me down a rabbit hole and apparently table sugar is only 50% glucose

but now I'm really curious what the shape of the response function here is