Tobias Megies

Rebased and force-pushed (previous PR tip was 0fdd130a7bde8a57b1439fe71fc6176e0a311998). Also adding this change to initial migrations.

Maybe whatever consortium/construct is hosting openstreetmap could be asked?

> The consortium/construct is just me. Yeah, that's what I guessed already. I was on about the OSM construct and if it might be worth a thought to let them...

As a side note, I noticed that the main opentopomap.org has very much improved in stability since last August. Since then, downtimes have been very few. Thanks @der-stefan!

> > which apparently proabably never can be in pyodide) > > This is not quite true. The `quickstart` requests API should not be too hard to shim with synclink...

@hoodmane i can add all the run requirements again, i had them in the meta.yaml before, and IIRC they were in there when I built the wheel. I accidently deleted...

@hoodmane compare https://github.com/conda-forge/obspy-feedstock/blob/main/recipe/meta.yaml ```yaml requirements: run: - python - setuptools - numpy - scipy - matplotlib - lxml - sqlalchemy #- requests - decorator # see https://github.com/obspy/obspy/issues/2984#issuecomment-1063161646 #- libffi

Yeah that looks good to me @d-chambers :+1:

Nope don't think its in the code yet, also, all issues in 1.2.1 can be punted to 1.2.2. But to be honest, I would focus on 2.0.0, put mostly everything...

My feeling is, it's OK to have the current libmseed for the next releases 1.2.0 (py2+3) and 2.0.0 (Py3 only - same functionality as 1.2.0). We can put libmseed 3.0...