If in fullscreen mode, pressing the refresh/reload button does refresh but also exits fullscreen mode. It should stay in fullscreen mode.

I know we have some inherent problems with terrain height, but I think there may also be a bug. If you roam with mouse point around the coastline you get some odd numbers. If you go to Tuross Heads, the number get smaller as you go inland and higher as you go out to sea. It's almost like the tile is being read backwards.

A guide to style the share panel in keeping with current content and functionality

Provide a simple API to allow a 3rd party service to work with National Map. Change GeoSpace to work through this API and have no built-in presence in NM. Provide a sample service and documentation.

This work is mostly completed sans documentation. I just wanted to have an issue to work against.

We should set up our POC NM to use Google Analytics before it's announced to track usage before, during and after govhack (to understand how people are using it and also to help plan for the production release)

Images are in the National Map Implementation Plan:
http://wiki.inside.nicta.com.au/display/DLGETD/National+Map+Implementation+Plan

Australian Topography only covers Australia, so we'd like to have something for the rest of the world as well.

Not needed for POC but a nice-to-have

Use a smaller font, replace logos with text links.

I realise this will all go away when we get the new data collection IA in but if that is more than a day away... can we remove the placeholder broadband and nbn data services. A few people are now checking/demoing the NM and I've had a couple of queries re this. It would be best to remove these and add back in if we get access the real data services.

Hi Kevin

Attached is an updated brand for http://nationalmap.research.nicta.com.au/ header with "beta" changed to "0.1"

Identical size and file name (most of it is invisible on this white bg)

We've indicated we will bundle up small local datasets with our share URL so more shared links will work. On the surface it doesn't appear too bad to do, but may have lots of implications, so may get moved to Post-POC.

We'd like to include a compass in the POC. #34 covers the code side, but we also need a compass design. Ideally it would be designed for interaction as well as display, so users could use it to rotate the camera.

Some wiki text to kick off Services API documentation/discussion

https://github.com/NICTA/nationalmap/wiki/Services

I'm entering this an issue to make it easier to track comments. This should be up and running later today.

We still don't have a web page for national map. As well as the general info, it needs to point that is still very much proof of concept software software. Also we need to think about whether the base link for nationalmap should go to the page or the viewer. Safer to go the page to set to set expectations, explain things, etc.

Hilary is setting up a FAQ page. We need to populate it.

Some random ones to start with:

• What is the National Map? (for answer, just link to about page)
• I'm a data owner in Australia. How do I get my data on to National Map?
• I like the Australian National Map. How can I set one up for my country or for the world?
• What data formats are supported?
• What browsers are supported?

There are caching solutions for both NM and the GeoServers we host with data. We need to tune these before the release. Possibly get some of Damon's time?

Make sure that all the data formats we support can be handle via drag and drop, file open, url via ?data_url=, and services returning urls. We are pretty close at this point and just need to test and cover gaps I think. If it too much of a hassle we can note it in release notes and finish it up post-poc

This relates to #82. One of the main initial targets for NM is developers finding and using open data. It is important that they understand what they can and can't do with any data accessed through the NM. We should try to ascertain any usage constraints and make those clear near the top of the info panel. This is probably not going to be tidy/easy :-(

In some existing services (eg GA's surface geology) the licence info seems to be there but is given in "AccessConstraints" (they say the data set is CC-BY there). From a quick look at the WMS specs, it seems that this is intended for describing access constraints rather than usage constraints but there doesn't seem to be a better way of describing usage constraints in WMS (I could be wrong). So one option is to repeat the AccessConstraints property near the top of the info panel (as well as keeping it in place where it is). However if we do this, we'd need to be careful as the default value specified in the WMS spec is "none" meaning "no access constraints" which is clearly different from "no usage constraints" (most of the NM WMS services seem to have "none" even though they are intended to be CC-BY and CC-BY DOES have usage constraints - ie you have to give credit when you use it) so we wouldn't want to show "none" as the usage constraint.

For data.gov.au services, we could get the data from CKAN.

Ideally, we should work out the best approach for NM and create some guidance for the data custodians to make sure that they are putting the right info in the right places. If WMS (and I guess WFS but I haven't checked the spec) don't handle this well, this could be a bit of a hack).

I'm assuming we won't get this sorted for POC but if there is anything simple we can do to go part of the way (given that lots of developers will be using the data that access via NM and will want to know what they can and can't do with it), that would be good.

Right now we're using default styles for everything which is very limited. We should create better styles where possible.

I'm not sure if we can do anything about this but this is really bugging me for going from a national view to a localised data sets (eg a council area) since we just moved over from some of the WFS data sets to using WMS equivalents (eg all the data.gov.au WFS services such as bike racks). When viewing the whole country and then choosing a WFS for eg bike racks in the Gold Coast, we would show the points and zoom in and all looked great. When doing it with a WMS, it gets the high level tiles and these are huge and occlude the whole area until we get to a lower tile level. It looks much more clunky with WMS than with WFS. I assume this can be addressed with styles on the WMS server but this is happening with data.gov.au data sets and we may not have much control of the tiling.

Can we do anything about this (eg finish zooming in before loading the WMS tiles)?

The things we do proxy could also be a big problem. To improve performance I think we need to:

• get more cores on the vm or get a new box
• add multi-threaded support to node via cluster (e.g. like GeoSpace)
• tune varnish to do as much caching as possible of wms tiles.
• point at our geoserver.research.nicta.com.au service as much as possible instead of GA for wms display.
• point to GA, BOM, data.gov.au as much as possible for data links given to user.

I thought this was covered somewhere but can't see it so here it is (kill if I've missed it)... It's related to #37 . We need a new look "info" panel for a data set/service as discussed with the newer look styling and with URL (copyable) and some key metadata. Ideally we'd have at least data custodian, description and licence but I realise that we're probably getting different data from different services.

The more I think about the open proxy the more issues I see that can bring out server down. I think we need to turn this off and just let people know that the data source they're tying to get it should provide CORS support (popup?).

In Chrome OSX there is a display problem with the contents of the "Add Data" panel, running under the right edge.

See screen:

@kring & @kgrochow

http://nw8f6t.axshare.com/

Work in progress

What is the elevation reported in the header with respect to? I (the layperson) find it somewhat unintuitive. Does its accuracy warrant presentation to one decimal place? It might need further explanation.

As in Hilary's design:

For example, users should be able to specify the URL of a WMS server, ArcGIS MapServer, or a URL of a single GeoJSON or KML file.

This requires that we either make the user specify the type of service, or we try to deduce it automatically by making several different requests.

Please append any comments you have after trying it out

From Meena:
PDF showing the Data Panel IA within the National Map. There are two options.
Please read the notes in orange on the PDF. Should explain everything.
http://wiki.inside.nicta.com.au/download/attachments/89458324/Data_IA.pdf?api=v2

Also attached is a spreadsheet showing where all the data in the current ‘Data collections’ and ‘Maps’ should be placed.
http://wiki.inside.nicta.com.au/download/attachments/89458324/National%20Map%20Topics.xlsx?api=v2

HC: I like both options.
I think the other option of no “Data Collections” is an nice alternative.
Love “Editor’s Picks” as a category.
I also think your solution for a third level (topic 2) is well considered for scalability.
Do we need to run this by Margie Smith?

I believe the problem is that IE11 exposes the experimental-webgl context name instead of webgl, so our feature detection thinks WebGL isn't available.

Hilary has set up a page with basic info. I need to go through and add more.

The stored camera params don't take tilt and view direction into account

Give the user a way to download the actual data.

We currently show metadata for WFS features when the user clicks them. This can be done for WMS features as well by doing a GetFeatureInfo request to the WMS server on click, as long as the server supports it (most do).

This is started in the wmsFeatureInfo branch.

I know this is happening because we add and remove items at the top, but it's very unintuitive and annoying when you're trying to explore the list. Can we just offset since we know that it will be added or removed?