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

Installation document precisions #366

Open
geolives-contact opened this issue Oct 12, 2020 · 0 comments
Open

Installation document precisions #366

geolives-contact opened this issue Oct 12, 2020 · 0 comments

Comments

@geolives-contact
Copy link

geolives-contact commented Oct 12, 2020

We tried to make an install of your solution into our server and we got some errors we want to pinpoint here :

  • It was needed to make an upgrade to SQLAlchemy. The version in the installation notes does not support postgres.
    pip3 install SQLAlchemy --upgrade

  • Template database must be set in UTF-8 encoding.

  • Issue with the function st_asbinary(bytea) on new postgis versions, because the function is not unique. The parameters can both be geography or geometry. We removed the geography function to solve the issue temporarily.
    ALTER EXTENSION postgis DROP function st_asbinary(geography);
    DROP function st_asbinary(geography);

Now our main question is : how much size the disk must be to import planet OSM data and make all additional schemes based on imports ?

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

1 participant