Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / inasafe/safe-geonode issues and pull requests
#13 - Timestamp returned by InaSAFE crashes the keyword parser
Issue -
State: open - Opened by vdeparday almost 11 years ago
#12 - Issue with projection that need to be forced declared in GeoServer
Issue -
State: open - Opened by vdeparday almost 11 years ago
#11 - Upgrade to django-leaflet 0.7
Issue -
State: open - Opened by vdeparday almost 11 years ago
#10 - More robust parsing of the HTML table output given by InaSAFE
Issue -
State: open - Opened by vdeparday almost 11 years ago
#9 - Pan center not set properly at first load
Issue -
State: open - Opened by vdeparday almost 11 years ago
#8 - Error when generating raw data for the json output when processing geometries
Issue -
State: open - Opened by vdeparday about 11 years ago
#7 - Keyword that have a colon in their value causes the application to crash
Issue -
State: closed - Opened by vdeparday about 11 years ago
- 1 comment
#6 - Calculated output layer gets the name of the input hazard layer
Issue -
State: closed - Opened by vdeparday about 11 years ago
- 1 comment
#5 - Ask the user before overwriting output layer with the same name
Issue -
State: open - Opened by vdeparday about 11 years ago
#4 - Input hazard layer get silently overwritten by the output/calculated layer
Issue -
State: closed - Opened by vdeparday about 11 years ago
- 1 comment
#3 - Install requirement on GeoNode causes an error even with GeoNode installed and virtual env activated
Issue -
State: open - Opened by vdeparday about 11 years ago
#2 - Latest GeoNode 2.0 template conflicting with safe-geonode, leaflet template
Issue -
State: open - Opened by vdeparday about 11 years ago
#1 - Projection files created by QGIS for WGS84 are detected as incompatible
Issue -
State: open - Opened by vdeparday about 11 years ago