Selection of basemap output formats, TMS input, mobile UI

[spwoodcock]

Note: this requires osm-fieldwork v0.3.7 or v0.4.0

I quickly made the PR as I had been working on osm-fieldwork basemapper.py and had it fresh in my head (avoid context switching).

Fixes #839 and fixes #586

• Selection of mbtiles, osmand (sqlite) and pmtiles formats for basemap generation.
• Use custom TMS URL for input.
• Fixed mobile UI for tile generation modal.

@varun2948 I didn't spend too long on the UI part. I didn't want to duplicate work you may be doing already. But I just made it work on mobile as well as desktop 👍

[varun2948]

@spwoodcock sounds good to me will have a look onto this branch aswell thanks for the feature on both side frontend backend .

[varun2948]

@spwoodcock i am having this issue on this branch on my local server any idea ?

from osm_fieldwork.basemapper import create_basemap_file fmtm_api | ImportError: cannot import name 'create_basemap_file' from 'osm_fieldwork.basemapper' (/home/appuser/.local/lib/python3.10/site-packages/osm_fieldwork/basemapper.py)

[spwoodcock]

This needs a new release of osm-fieldwork.

You can bind mount a local version - see the dev backend docs 👍

[varun2948]

@spwoodcock now using development version of osm-fieldwork, I am getting error like this
File "/opt/app/central/central_routes.py", line 33, in <module> from ..projects import project_crud, project_schemas File "/opt/app/projects/project_crud.py", line 41, in <module> from osm_fieldwork.basemapper import create_basemap_file File "/home/appuser/.local/lib/python3.10/site-packages/osm_fieldwork/basemapper.py", line 34, in <module> from pmtiles.tile import ( ModuleNotFoundError: No module named 'pmtiles'

[spwoodcock]

You need to rebuild the backend image using this branch.

It has the pmtiles dependency added.

[varun2948]

added output_format on migration and then onto api and onto the UI table for generate basemap.

[spwoodcock]

Nice 🤩

The migration looks good 👍

I was determining the format using the file extension - I'll have to check the download endpoint - we can probably use this new field instead. (I understand the new field is required to display the format without downloading the file).

Just fyi, I don't really envision the pmtiles format will be requested by a user, as it's an online only format (although they could, so we can give the option.

The idea of pmtiles was to:

• Generate the entire project area in pmtiles when the project is created.
• A user requests an area to download in mbtiles or sqlite format.
• The backend grabs the tiles from S3 based pmtiles via RANGE request, and packages the tiles in the requested format (so they can view their area offline).

[varun2948]

Yeah
My initial thought about the output_format was to extract it from the path and use that but then just did it with another field as it seemed reasonable as it already had a column for source.

Hmm about the PMtiles it was just requested by Rob so i guess we went ahead and did it for PMTiles too but i understand what you're trying to say.