You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ?
The text was updated successfully, but these errors were encountered:
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 ?
The text was updated successfully, but these errors were encountered: