aifdr / tsudat2-client Goto Github PK

When I select upload or search layers I get no upload dialog. Just blank.

Can we develop functionality so the user can upload their own elevation data in the elevation dialog box in step 2 instead of having to do it in the genode map - upload section prior to starting the simulation workflow.

The user should not be able to draw a complex polygon. This used to work, but now I can draw one with no error message

I uploaded a geotiff file and set the permissions to private. Then i could not view the layer in the data section of geonode, it just returned a white screen. Then in maps it did not load any layers not even the base layers.

Update - instead of top and bottom banner. Use drawer for bottom banner. Can we somehow fit the logos in the top banner. Even if they are smallish. Need to make them visible to keep people happy :) Nick

The Client should have a Top Banner that looks like the one in the main tsudat site http://tsudat.nci.org.au/ It should probably be much thinner in height.

It should probably include:

• a login button if the user is not currently logged in
• a logout button if the user is currently logged in
• the username displayed if the user is currently logged in (this may require more work, or a call to something like /data/acls to get the username {which may require changes to that endpoint})

The output layers should be set to totally private when loaded from anuga output into GeoNode. The user can then open them up if they so desire.

the abstract for the maps should be the same as the layers (jeff you have this information from when you were here in email). The only difference is that it wont say what layer it is. But it needs all the meta data on the event etc.

In the data search page in Geonode I listed all layers I can see. I then zoomed right into batemans bay so I could only see the town. I then tried to refine by search by this area and it still returned all the same layers. This includes subfaults etc, which are not in this field of view.

When a user selcects an event in the events grid, the associated subfaults should be highlighted on the map.

When user selects a hazard point they should be able to see the hazard curve (png) image for that hazard point (step 1 in UI wiki).

Still some things to be replaced in the output map abstract formatting and content.

Unless the user submits an SLD with their uploaded DEM data, they have no good way to use the default DEM style that is in the DB. Its not assigned as an option in the publishing options unless the GeoServer admin does this for them.

Perhaps a dropdown/multiselect of a set of default styles on the data upload page instead of just SLD upload? Some subset of all styles

When I view the flow depth layer, I get my old wet-dry colour pallete at large scales, then when I zoom in I get the new red-blue colour scale.

The mesh resolution in step 2 is getting passed into the json file as zero. The default is 1 000 000 but in the json file this value is zero.

I exported a layer as a geotiff - then tried to import it back in and it gave me an error saying the layer must be geotiff or shapefile. Shouldnt the exported layer be geotiff?

When panning the map - when I move the centre of the map east across the dateline I lose all the layers in the map. Then when I go back they re appear.

When I zoom right into a community to create at around 1:200k scale the hazard points are very small and hard to see. Can we change the size of the hazard points for different zoom levels so that they get bigger as you zoom in. Cheers

At the moment I cannot select a hazard point. And when I zoom in the subfaults turn to the old blue square style.

Jeff from the UI when you pass the information about the internal polygons, can you change the type one of 'resolution', 'friction' or 'aoi' (case-insensitive).

"interior_regions_list":[
[
3,
"/data/run_tsudat/nickhorspool_20110617T163511/no_project_name/xtest_9/final/polygons/ip0.csv",
null
]
],

The doc. says:

interior_regions_list

This entry in the JSON dictionary will contain a list of iterables of the form:

(type, filename, value)

type is a string defining the type of polygon data and will be one of 'resolution', 'friction' or 'aoi' (case-insensitive).

Can you add a sentence to the map and layer abstracts "The simulation setup was a Trial/Final version"

Jeff, I realised that we need to allow the AOI polygon in step 2 to be able to cross over other polygons. This is because it is not used in anuga for the mesh, just for defining the bounds of the export area so it is ok to have it crossing. are you able to allow this poly to cross over? thanks N

Abstract:
Can you please round the magnitude to 1 Decimal Places, tide to 1DP. The waveheight at the HP is coming up as zero. This should be 2DP. And there is still a fixme for the elevation data layers used.

Layers:
In the info button on the tool bar. Can we round these values to 2DP, at present it gives me about 15 DP.

Create default SLDs for flow depth, flow speed, and waveheight (amplitude)

Set default values in step 2 to the following:
Tide=0.0
Start time=0
End time=3600
Smoothing=0.1
Setup=Trial

Step 1
default mesh friction = 0.01

When a user selects gauges in the simulation setup the run_tsudat code will return pngs graphs of the tsunami wave. Can these figures be included in the project map.

can we have a tool that will automatically create accounts for a list of users (or can you just do it).

In step2 we do not need a internal polygon called area of significance. So you can remove this from the options.

The boundaries of the Project and Internal Polygons should be displayed on the Project Map pages. This would require that a MapLayer source_cfg or layer_cfg be able to store a CQL statement with the layer to limit the records that are returned.

Something that might be useful in upstream geonode. Might be nice to be able to have this at the Layer level such that you could have a "view" of another layer as its own layer in GeoNode. Will post to the GeoNode list about this.

Jeff, can you please check the model setup parameter. I ran a simulation last night (420 Cairns_4IP_friction_2 Project ID: 465 DONE) which ran til completion, however I used a model setup=FINAL but in the abstract it says trial. It also ran v. quickly hinting that it might have used a trial set up. Can you please check this parameter is getting passed through correct, or is it just the abstract is wrong?

When attempting to print a map in Geonode it returns a 500 internal server error. This occurs when clicking the print icon in the print preview window.

When i select google earth button in the map view it shows loading wheel then just turns white. Its says done in the browser.

https://skitch.com/nickhorspool/fd5ft/fullscreen

Still some things to be replaced in the output layer abstract formatting and content.

The google aerial basemap in the layers panel on the left displays the google roadmap not the google aerial imagery.

Step4. When I change between the panels, the polygons I created in step2 are not visible. It would help if these were visible for all steps, so we can keep some context of where the simulation area is. This is important for selecting gauges in step4 which require us to put a gauge inside the simulation area so we really need to see these polygons.

You can remove the selectable option "Output the quantities above as the maximum value over the entire duration of the simulation.". This will now be fixed option.

as per title

When I select a source zone by clicking on one of its subfaults, that individual subfault becomes highlighted. Then when I select an event from the populated menu I can see the subfaults that make up that event. That is working fine.

However if I select a source zone from the drop down source menu then it highlights all of the subfaults. Then when I try and select an event I cannot see which subfaults are highlighted because they all are.

Rollie, can you have another crack at refining the hazard point styling. It is a little hard to tell the difference between the lower colours. Maybe either sizing or colouring or both needs to be changed.

The client should have a footer that includes many of the same links as the footer in the main app. http://tsudat.nci.org.au/

• Powered by GeoNode
• Help
• For Developers
• Disclaimer
• Partner Logos

As with the Top Banner, its probably going to take a TON of screen real estate away from the app if we replicate the exact format of the footer in the main app. Rollie, I'll leave it to you to sort that out.

NOTE: Jeff and i discussed and we will go with a :drawer for logos so not to take up real esate of the client- Nick

Can you please change "depth of water (m)" to "Flow depth of water onland (m)"?

Andreas can you please change the symbol of the hazard points to diamonds. To distinguish them from the subfaults. Rollie had this in his original wireframes. Cheers

can we colour the polygons by type - and make internal polygons that are invalid (ie. overlap boundaries, or are complex) turn red.

Can we have a selected styling similar to the subfaults but for the hazard points. The highlighted colour might be different - maybe bright red?

There is some problem with the Velocity Output Layers showing up all Black. There is data in them, something else amiss.

Step1. The hazard points and subfaults are not yet coloured according to their values. Jeff I know you are planning to do this, but this is just a reminder :)

Jeff, I noticed that the batemans 20m DEM has zero values around the edge (have a look in the UI) which have come in from when it was warped from UTM to WGS84. This is a problem as it will assign zeros to the elevation in anuga. Can you change this so those values are NAN. Or if you cant we might need to clip the reprojected DEM to remove these. Also what will happen when it gets put back into UTM when it gets passed back to ANUGA.

When the user hits "run simulation" in step 4, a pop-up box should appear saying "Confirm that you want to run this simulation Yes/No button. Note that the simulation may take a while, and you will be notified by email when it is finished."

Please add A4 portrait to the print map option.

The 3 default DEM raster styles for stage, depth and velocity are not being properly applied to the output layers from anuga when being loaded into GeoNode.

Bug here somewhere

https://github.com/AIFDR/tsudat2/blob/master/tsudat/tasks.py#L379

The polygons that are defined by the user (simulation polygons, internal polygons etc) need to be exported as vertices but the first vertice should not be repeated at the end of the file.