Somewhat recently OSM enforced changes to their tile access policy. This is fair enough, this is a free service provided to the benefit of everyone, yet hosting tiles is not free. However, for tools which aren’t compliant, this results in tiles being completely blocked, making interactive maps significantly less useful: This example happens when you use nbconvert to export a jupyter notebook to HTML when it contains a folium map - in this case produced with geopandas.

This is my self reference of handy git config settings to apply for whatever computer I’m setting up. Make git push just push a corresponding branch for new branches, instead of giving me something to copy past to do that git config --global push.autoSetupRemote true The one place I don’t use this is for open source repos where there’s a fork workflow and I’m a maintainer on GitHub. Here I’m often using the github cli gh pr checkout #pr_id and I’m paranoid about accidentally pushing unintended things to other peoples forks (this is probably fine, but I don’t know for sure)

Useful things in python’s platform module Recently I was helping a colleague try and debug a failing installation of GeoPandas. Or to be more precise, installing Pyogrio, the default IO engine was failing. Now once upon a time this was regularly a pain point due to the lack of widely available windows wheels but today that’s a mostly solved problem. User error seemed a more likely scenario. Pretty quickly I was able to work out that the issue came pypi trying to install via source, and the absence of a C compiler and the required flags to build GDAL was the error being surfaced.

Periodically I find myself switching back and forth between different and editors and workflows to try and be the most productive, depending on what kind of work I’m doing. Usually when in python, that involves some variation of writing python libraries / modules and exploratory development in jupyter notebooks of some kind. The goal is to try and minimise the friction encountered working between different sources. These are the combinations I’ve tried over the last couple of years:

To SSH into instances on AWS (or generally do anything where the internet needs to talk to the instance) one needs to set up inbound rules within a security group attached to an instance. For SSH, generally I only want to whitelist a single IP address - my own. Today I learnt that AWS can automatically set your IP: By selecting “My IP” from the “Source” dropdown. At first I was a bit worried this was a little bit too clever and might start updating records whenever I log into AWS - but fortunately not - it’s just to populate the IP on this screen.