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

Make animated visualizations for the target area #108 #138

Open
wants to merge 16 commits into
base: develop
Choose a base branch
from

Conversation

pierrealixt
Copy link

@pierrealixt pierrealixt commented Apr 30, 2018

Implementation for #108 - added support for creating animations of an area.

osmanimate

@timlinux
Copy link
Contributor

Cool thanks @pierrealixt . Can you take care of the failing tests (see https://travis-ci.org/kartoza/osm-reporter/jobs/373057299#L933) - it looks like you need to add BeautifulSoup to the requirements file.

Also, it is nice if you can make little screen animations using https://www.cockos.com/licecap/ or similar and attach to the PR so that the reviewer can easily see what the changeset does without needing to run the code themselves.

For your PR can you include a minimal description that refers back to the ticket e.g. "Implementation for #108 - added support for creating animations of an area."

For the code there are some compliance issues to our standards. Can you start by running pep8 and flake8 against the code base and making sure you have fixed any issues they identify. Then I will do a code walk through with you on wed, outlining any other style related issues I see.

Awesome stuff man!

@pierrealixt
Copy link
Author

The reason why checks have failed has something to do with the executables I use: snap, render, encode.
It seems I must compile them on the Travis machine.

@timlinux
Copy link
Contributor

timlinux commented May 2, 2018

RUN apt-get -y install osm2pgsql wget unzip
RUN wget -O osm-snap.zip "https://github.com/ericfischer/osm-snap/archive/master.zip" && unzip osm-snap.zip && cd osm-snap-master && make && mv snap /usr/local/bin

Copy link
Contributor

@timlinux timlinux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like you are committing the binaries for snap, render and encode now. Is that intended or are you going to rather build them on the fly in docker? Either is ok for me.

class Frame:

"""
Frame is an object representing a frame of the final GIF
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Terminate with full stop and then add newline before extended description

Frame is an object representing a frame of the final GIF.

@@ -5,3 +5,7 @@ pep8
nosexcover
nose
selenium
bs4
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should not needed to repeat these here - the first line of this file already imports everything from requirements.txt

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK but it doesnt. The first line is commented so it doesn't install what's in requirements.txt.

Am i right?

Copy link
Author

@pierrealixt pierrealixt May 4, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I uncommented the first line in requirements-dev.txt.
Then I built an image from Dockerfile.dev with the command:
docker build -f Dockerfile.dev -t "pat-osm-reporter" .

And it crashed as expected: maximum recursion depth exceeded.
Because we ADD HOST/requirements-dev.txt as CONTAINER/requirements.txt
and RUN the pip install command which will install from requirements.txt => maximum recursion depth! KABOOM.

Does it make sense?

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

Successfully merging this pull request may close these issues.

2 participants