inasafe/safe-geonode

Issues

• Timestamp returned by InaSAFE crashes the keyword parser

  #13 opened 11 years ago by vdeparday
  0

• Issue with projection that need to be forced declared in GeoServer

  #12 opened 11 years ago by vdeparday
  0

• Upgrade to django-leaflet 0.7

  #11 opened 11 years ago by vdeparday
  0

• More robust parsing of the HTML table output given by InaSAFE

  #10 opened 11 years ago by vdeparday
  0

• Pan center not set properly at first load

  #9 opened 11 years ago by vdeparday
  0

• Error when generating raw data for the json output when processing geometries

  #8 opened 11 years ago by vdeparday
  0

• Keyword that have a colon in their value causes the application to crash

  #7 opened 11 years ago by vdeparday
  1

• Calculated output layer gets the name of the input hazard layer

  #6 opened 11 years ago by vdeparday
  1

• Input hazard layer get silently overwritten by the output/calculated layer

  #4 opened 11 years ago by vdeparday
  1

• Ask the user before overwriting output layer with the same name

  #5 opened 11 years ago by vdeparday
  0

• Install requirement on GeoNode causes an error even with GeoNode installed and virtual env activated

  #3 opened 11 years ago by vdeparday
  0

• Latest GeoNode 2.0 template conflicting with safe-geonode, leaflet template

  #2 opened 11 years ago by vdeparday
  0

• Projection files created by QGIS for WGS84 are detected as incompatible

  #1 opened 11 years ago by vdeparday
  0