Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic computations from GrandLyonOpenData #30

Open
clementcolin opened this issue Jun 10, 2021 · 1 comment
Open

Automatic computations from GrandLyonOpenData #30

clementcolin opened this issue Jun 10, 2021 · 1 comment
Assignees

Comments

@clementcolin
Copy link
Contributor

There is a need to propose a docker that allows to automatically fill a 3DCityDB with borough name to fetch in OpenData GrandLyon.

It should be very similar to the Chemistry Valley

@EricBoix EricBoix changed the title Automatique computations from GrandLyonOpenData Automatic computations from GrandLyonOpenData Jun 10, 2021
@EricBoix
Copy link
Contributor

EricBoix commented Jun 10, 2021

Some remarks

The chemistry valley data processing container that you point is alas unfinished work...

Under the hood, there is a computational pipeline that as indicated by the Dockefile uses a python+docker based pipeline to realize the computations.
As poorly documented for the static case (i.e. the non temporal version) the pipeline is a simplification of the diagram standing at the head of that PythonCallingDocker page and boils down to the Chemistry Valley (entrypoint.sh) pipeline.

If what you need is a loaded up 3dCityDB database, it should suffice to consider the first part of that pipeline, and stop at line 8 of that script.

Related info

Note that the manual way of things (that should be avoided because it is not reproducible), for the Chemistry Valley (that is the upstream information that led to the chemistry valley data processing container) is documented in the associated DEMO.
This manual instruction set indirectly documents the importance of the demo_configuration.py configuration file which explains this Dockerfile line.

Possible hints

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants