sparlab / bikemaps Goto Github PK

End of life for Python 2.7 is scheduled for January 2020. Are there plans to upgrade the site to Python 3 before then? The site will still run on 2.7 after EOL, but it will become increasingly vulnerable from a security standpoint. This might be a not-so-painless update to a lot of the backend code so was just wondering if it's on the radar.

If needed, I might be interested in helping with this in my spare time to brush up on my Django skills. Let me know.

Hope you're all doing well!

If someone reports two consecutive reports, they have to un-click and re-cklick the "I have read and understand the terms and conditions" check box to activate the submit button.

It would be great if you added some information about dependencies to this:

• What version of postgres are you using?
• What version of python?

Also would be great if you included the commands to create the database (because, for example, I've never created a case sensitive database name):

CREATE DATABASE "bikeDB";
\connect bikeDB;
CREATE EXTENSION postgis;
CREATE EXTENSION postgis_topology;
CREATE EXTENSION fuzzystrmatch;
CREATE EXTENSION postgis_tiger_geocoder;

Do something about your hard linked path to your email password

I get an error: You're using the staticfiles app without having set the STATIC_ROOT setting to a filesystem path. Is this my fault?

Right now, the map on the visibility page uses the extent of the world when the page loads. This means that a very large amount of data gets requested and slows things down.

We can explore a couple of options for improving performance and the user experience:

1. Use geolocation to identify the users position and set the extent at a certain level (experiment to see what appears reasonable).
2. If navigating from the main map page, use the center point of the map from the main page as the center point of the map on this vis page and zoom to an appropriate scale.