osmox

[Hussein-Mahfouz]

Related to #19 and #39. We can either:

• implement logic in this comment
• point the user to osmox and tell them where to place the output file once they've created it

[sgreenbury]

Remaining tasks:

• Update the output format to geoparquet
• Update the output path to interim/osmox and change the downstream scripts to point to this
• Check minimum python version issue with 3.12
• Ensure the output from pyrosm matches the region config name

[sgreenbury]

Adding the deps mentioned for osmium fixes the CI for Python 3.12 (b54cff0)

[Hussein-Mahfouz]

Do these dependencies need to be added to the poetry lock file?

[sgreenbury]

Do these dependencies need to be added to the poetry lock file?

Since they're external system deps to python I don't think we're able to install with poetry though we can add this to a requirements section in the docs and link to the osmium docs

[sgreenbury]

Merging this now with (the output file from pyrosm can be passed directly to osmox (1504c59).

[sgreenbury]

Perhaps we can move these osmox notes to a section in the documentation as part of #63?

[Hussein-Mahfouz]

Does it make sense to add the notes as a subsection under the Installation section of the main README? If that sounds good, do you mind doing it? I think you're better placed to add the notes than I am.

[sgreenbury]

Sounds good, I'll go ahead and add these notes to the docs as part of #63. I think we can have a section on configuration of the pipeline and we can include a subsection on osmox and mention the default config file JSON (config_osmox.json) along with the descriptions here.