They are migrating the api to a new domain and browning out the old one to get folks to switch over and figure out if there are any issues. There is also another infrastructure change going on as well.

Normally those would be posted on https://www.weather.gov/notification/ but that’s having hiccups, but the email list for announcements still works.

A few of the recent announcements: - https://www.weather.gov/media/notification/pdf_2023_24/scn24... - https://www.weather.gov/media/notification/pdf_2023_24/scn24... - https://www.weather.gov/media/notification/pdf_2023_24/scn24...

For as much improvement as there has been with what can be distributed via PyPI, there are still some domains that have gnarlier dependencies than wheels happily handle alone, and you either need to reach for the system package manager (and loose the ability to really control the dependency environment from that mismatch), or take advantage of the Conda ecosystem.

My org does a lot of work combining machine learning with oceanographic and climate modeling, which are both domains that have deep dependency chains that don't always mesh well, especially as our researchers mix in R and other languages as the same time, and the Conda ecosystem helps us a ton with that, but there are issues that `conda` and `mamba` don't help us out with.

Pixi takes a swing at some of what the Conda ecosystem hasn't been great at (at least without a lot of manual custom ceremony) that Cargo, Poetry, Pipenv, PDM, and other dependency and workflow management tools have demonstrated can be done such as lock files, cross platform dependency management, task running, and defining multiple related environments.

What's really cool when you have a mix of projects, Pixi can work almost entirely PyPI native out of a `pyproject.toml`, other than installing Python from Conda-Forge, so you can mix and match environments but stay with the same tool. https://prefix.dev/blog/using_python_projects_with_pixi docs: https://pixi.sh/latest/advanced/pyproject_toml/

Have you tried https://pixi.sh/ ? It brings Cargo/NPM/Poetry like commands and lock files to the Conda ecosystem, and now can manage and lock PyPI dependencies alongside by using uv under the hood.

I haven't been using anything CUDA, but the scientific geospatial stack is often a similar mess to install, and it's been handling it really well.

My local power company worked with a bunch of businesses in my town to install these rather than upgrade the dead end line for a few peak periods.

I gotthe habit of using 4” barrier webbing tape with gaffers on either side to make wire chases. That way there was nothing stuck to the cables and if another cable needed to run the same route, one side could be lifted, the cable slid in, and then reapplied.

I remember reading that paper when I was trying to figure out why we were having issues with a wireless link down in the Patagonia fjords.

Unfortunately we didn't have the hardware or enough control over the link (it took negotiating access with armed forces to work on either end) to try to implement any of their ideas.

Gaia GPS is fantastic. You can mix and match layers, and specify what bounds you want to download for a trip.

Right now I've got 3 GB stored locally, some of that for the usual locations that I wander out of connectivity, and some for a trip next week.

Garmin (formerly Delorme) Earthmate despite their other issues is great for state or province wide vector maps. Not as great for fine navigation and tracking (as it's designed to be paired with and control an InReach), but good for point of interest exploration.

I love Gaia on my iPhone and iPad, but I’ve had real problems with map layers not displaying lately. MapBox Streets and Gaia Streets are both hosed and I can’t figure out why.

I tracked a 20 day trip down the Grand Canyon on my VivoSmart.

I think it has the storage for a few months worth of continuous tracking before it needs to sync to free space.

Gulf of Maine Research Institute | Web Application Developer | Portland, ME | Full Time

If you like science or the ocean, know technology, and want to use tech to push science forwards, we’re looking for a Web Application Developer at Gulf of Maine Research Institute as part of the Ocean Data Products team.

GMRI is right on the waterfront in Portland Maine, where we work at the intersection of people and the ocean.

For a little detail of what the ODP team does, here’s a little of what I’ve been working on recently:

- Testing knowledge graph ontologies for a NSF project that is trying to push the domains of scientific modeling forwards - Developing a citizen science platform designed to support classrooms and projects that need a coverage to prove presence vs absence - Geeked out with USGS about low cost sensor platforms at the ESIP conference - Evolving the user focused components of NERACOOS’s interface to the buoys in the Gulf of Maine and beyond to make it more approachable to regular mariners (fishermen, sailors, surfers) than just scientists. - Prototyping transitioning our primary data service (ERDDAP) for NERACOOS to run on Kubernetes.

Or in the tech stack flavor: AWS, Digital Ocean, Kubernetes, Python, JavaScript, ERDDAP, THREDDS, Django, PostGIS, some flavor of graph database to be decided soon...

If that sounds like your kind of jam, here are some details: https://www.gmri.org/about-us/join-our-team/jobs/web-applica... You can reach out to me akerney at our website if you've got any questions.

It’s correct, the wilderness boundary line for Baxter follows the road. They didn’t just use the park extent.

Nope, the [park tote] road at 46.011344, -69.061875 is within the "remote radius" at peakbagger by about 450-500m. It's still in the top-50, but it's a tad lower on the list.