Skip to content

Issues: inasafe/safe-geonode

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.

Sign up for GitHub

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

10 Open 3 Closed
10 Open 3 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Timestamp returned by InaSAFE crashes the keyword parser
#13 opened Sep 30, 2013 by vdeparday
Issue with projection that need to be forced declared in GeoServer
#12 opened Sep 30, 2013 by vdeparday
Upgrade to django-leaflet 0.7
#11 opened Sep 30, 2013 by vdeparday
More robust parsing of the HTML table output given by InaSAFE
#10 opened Sep 30, 2013 by vdeparday
Pan center not set properly at first load
#9 opened Sep 30, 2013 by vdeparday
Error when generating raw data for the json output when processing geometries
#8 opened Apr 28, 2013 by vdeparday
Ask the user before overwriting output layer with the same name
#5 opened Apr 27, 2013 by vdeparday
Install requirement on GeoNode causes an error even with GeoNode installed and virtual env activated
#3 opened Apr 27, 2013 by vdeparday
Latest GeoNode 2.0 template conflicting with safe-geonode, leaflet template
#2 opened Apr 27, 2013 by vdeparday
Projection files created by QGIS for WGS84 are detected as incompatible
#1 opened Apr 27, 2013 by vdeparday
ProTip! Type g i on any issue or pull request to go back to the issue listing page.