Last note -- there'll often be a max number of features that are returned. If the data are longer than that you'll need to loop or use a refined query to bring it down.

Long story short: yes, "`.../0/query?where=1%3D1&f=pgeojson`" will usually work.

However the moment you think it will work out of the box is inevitably the moment that it won't. Clicking through and looking for the things above will usually get you over the line.

Click the layer, then "query", sorry.

Like: github.com/osmlab/edito...

Which grabs the stuff here:
vginmaps.vdem.virginia.gov/arcgis/rest/...

For tiles/maps there are a ton of awesome examples of how to build the URL in the OpenStreetMap iD editor layer index:

github.com/osmlab/edito...

This is more or less what I do when faced with a featureserver/map server. Look for the Query operation, set where=1=1 and format you want, then copy the URL and drop all of the empty API arguments. I'm sure there's a better way, but it works.

You may even be able to directly add it via mapgl::add_fill_layer(source=list(url= "{URL}")) but I'd need to check.

It's a feature server, can't you just pump the URL in directly?

services9.arcgis.com/j1CY4yzWfwpt...

k' should be at least the ridiculous 1e9*1e9, or error/warn, but it's 124 (the default of 5 per term, minus 1).

s/o to the @oceantracking.bsky.social Slack channel for the fun expedition to find this out.

Remarkable to see @dannyavula.bsky.social to go to the mat for raises for city execs making at least 2x RVA's AMI (and often much more), to allow those high-level employees to live outside the city, to maintain one of VA's highest property-tax rates...then fight a $20/hr min wage for city janitors.

Thank you for working to move the needle.

Just going to act like they didn't spend 4 years having every piece of legislation they passed vetoed.