zenwalk / atlasmapper Goto Github PK

What steps will reproduce the problem?
1. Load a AtlasMapper client using a Google base layer, on a mobile device
2. Disable all layer but the Google base layer
3. The map do not pan / zoom using mobile gesture.

What is the expected output? What do you see instead?
Expecting the map to behave the same way as WMS base layers

What version of the product are you using? On what operating system?
1.3-rc1

Please provide any additional information below.
It works as long as other layers are on top of the base map. An easy fix is to 
load a dummy layer containing no data to handle mobile gesture.

What steps will reproduce the problem?
1. Add a base layer (World_NE2-coast-cities-reefs_Baselayer)
2. Reduce the opacity to about 50%
3. Zoom in / out in different regions

What is the expected output? What do you see instead?
The base layer show some artefacts from the old tiles (the one that were there 
before zooming). Those tiles can only be seen when the base layer is not at 
100% opacity.

What version of the product are you using? On what operating system?
1.2-rc1

Please provide any additional information below.
Most of the time, the old tiles are removed, but not always. This glitch occur 
more often with the layer group "World_NE2-coast-cities-reefs_Baselayer" than 
with the plain base layer "ea:World_NED_NE2", even if they are using the same 
imagery and came from the same server (GWC).

What steps will reproduce the problem?
1. Open the AtlasMapper
2. Move the legend
3. Change the size of the browser

What is the expected output? What do you see instead?
The legend should stay approximately in the same location. Some consideration 
is needed to ensure it stays on screen but what happens now is the position is 
reset to the default top right corner.

What version of the product are you using? On what operating system?
Windows 7, Firefox

[deleted issue]

If your selected layer is not displayed you might think that the options panel 
refers to a visible layer. 

Show layer name in the options panel to avoid confusion.

What steps will reproduce the problem?
1. Install the AtlasMapper
2. Generate the demo client, the one that is there by default
3. Load a google layer. The projection is not a google one so the client become 
in a unstable mode

What version of the product are you using? On what operating system?
1.2-rc1

Please provide any additional information below.
The projection for the demo client should be the google one (900913)

What steps will reproduce the problem?
1. Perform a feature popup using Chrome Browser

The popup ballon always seems to have left and right scrollbars, even though 
they are no necessary.

What version of the product are you using? On what operating system?
Windows 7, Chrome

When we were generating a popup with an embedded iframe the following styles 
overcome the problem:
<style>
    .olFramedCloudPopupContent {
        overflow:hidden
    }
</style>

[deleted issue]

[deleted issue]

This problem occurred when doing a hot deploy of the AtlasMapper on Tomcat 7.0 
on a windows XP box. When the the admin page was looked at the following error 
messages were returned.

HTTP Status 500 -

type Exception report

message

description The server encountered an internal error () that prevented it from 
fulfilling this request.

exception

org.apache.jasper.JasperException: Unable to compile class for JSP: 

An error occurred at line: 14 in the generated java file
Only a type can be imported. au.gov.aims.atlasmapperserver.User resolves to a 
package
....
An error occurred at line: 59 in the jsp file: /admin/clientsConfigPage.jsp
ConfigManager cannot be resolved to a type
56:         <script type="text/javascript" src="../javascript/Frameset.js"></script>
57:         <!-- Send the client name to the clients config page -->
58:         <script type="text/javascript">
59:             <% ConfigManager manager = 
ConfigHelper.getConfigManager(this.getServletConfig().getServletContext()); %>
60: 
61:             var userName = 
'<%=Utils.safeJsStr(request.getAttribute("loggedUser.name")) %>';
62:             var demoMode = <%=manager.isDemoMode() %>;

On inspection with a working version of the AtlasMapper it seemed that the hot 
deploy did not create the compiled version of the JSP pages.

The fix was to stop Tomcat, delete the AtlasMapper directory in 'webapps' then 
restart tomcat. 

What version of the product are you using? On what operating system?
Windows XP, Tomcat-7.0.27, Java JDK 1.6.21

What steps will reproduce the problem?
1. create a new ncWMS datastore
2. add a URL with no "." in the host name
3. fails verification

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

When the "Data source configuration" window is left open and the user session 
times out the "Data source ID" has a validation error of:
"Unable to validate the field: The response returned by the user is invalid."
This message is not particularly useful.

What is the expected output? What do you see instead?
Ideally the application should give the opportunity to log back into the server 
without loosing existing changes, or it should have a more accurate error 
message.

Work around:
If you notice this problem then open another tab in the browser and re-login to 
the server. The session is shared across all tabs in a browser and so the 
validation will now work.

What steps will reproduce the problem?
1. Load a client with a base layer
2. After load, some tiles are missing on the map

What is the expected output? What do you see instead?
Expecting no missing tiles

What version of the product are you using? On what operating system?
IE6 windows

Please provide any additional information below.
The tiles appear when the layer is hidden/shown, map pan around far enough than 
come back, zoom out/in or resize the browser window. According to some post, 
the tiles are there but IE6 refuse to display them.

What steps will reproduce the problem?
1. Fresh installation of AtlasMapper 1.3-rc3
2. Enable Add and Remove buttons in Advanced client config
3. Build the demo client and view it.
3. Add Bunyip sightings KML as a layer.

What is the expected output? What do you see instead?
The legend for the KML appears, but no data points.

What version of the product are you using? On what operating system?
1.3-rc3, windows

The rules that apply to caching of the capabilities documents for datasources 
is unclear. Notes on this topic should be added to the text on the datasources 
page.

It is unclear when the clear capabilities button needs to be pressed.

[deleted issue]

[deleted issue]

What steps will reproduce the problem?
1. Create a new data store
2. put the getCapabilities URL as the WMS service URL
3. Create a client based on the new datastore
4. Layers do not show in the client (although they appear in the legend)

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

What steps will reproduce the problem?
1. Add multiple layers to the AtlasMapper
2. Perform a feature request by clicking on the map
3. Only the top most layer will get the feature request.

What is the expected output? What do you see instead?
Quite often the top most layer is labelling or hillshading which is does not 
produce useful feature request. Potentially we could disable the feature 
request for these layers in the manual override, but this is not always the 
solution. With the current implementation it is not possible to
compare values from different layers at the same location. 

The client should display the feature request to the layers in different tabs 
perhaps.

What steps will reproduce the problem?
1. Generating a client using a data source (or many) from a slow server
2. The generation show a window that says "Please wait..."

What is the expected output? What do you see instead?
A window with a list of all data sources associated with the client, and their 
progress (waiting, downloading / cached, parsing in progress, error / pass / 
okay), with buttons to decide to force the generation if it fail, clear the 
cache of data sources, etc.

Please provide any additional information below.
This feature will require a server status service, and a good refactorisation 
to allow threaded generation.

[deleted issue]

When moving up and down, the scale line stay doesn't scale; it should adjust as 
you approach the poles.

The ScaleLine should be declared like this:
OpenLayers.Control.ScaleLine({geodesic: true})

What steps will reproduce the problem?
1. Create a manual override on a ArcGIS folder
2. Re-generate the client
3. Go back to the manual override

What is the expected output? What do you see instead?
Some parameter has been added to the manual override. The override JS Object is 
modified by the application instead of only using the values.

What version of the product are you using? On what operating system?
1.2-rc1

Please provide any additional information below.

What steps will reproduce the problem?
1. Create a base map which has multiple layer group as default layers
2. Load the map in any browsers

What is the expected output? What do you see instead?
The layers order may not be the same as the one specified in the configuration

What version of the product are you using? On what operating system?
1.2.1

Please provide any additional information below.
First investigations shown that the problem is probably cause by the layer 
groups having to request it's content using Async requests, which may not come 
back in the same order, especially when a layer group contains more layer 
groups.

What steps will reproduce the problem?
1. Add a layer group (the issue doesn't occur if layer group contains only 
deactivated layers)
2. Add a normal layer
3. Move the layer group on top of the normal layer (drag n drop in the layer 
switcher)
4. Open the layer group (chick the + icon in the layer switcher to see the 
content of the layer group)

What is the expected output? What do you see instead?
The layers in the layer group that are shown on the map should be selected 
(checkboxes checked) but they are not.

What version of the product are you using? On what operating system?
1.2-rc1

Please provide any additional information below.
If the layer group is opened (initialised) before it get moved, the issue do 
not occur.

[deleted issue]

What steps will reproduce the problem?
1. Create a manual override on a ArcGIS folder, using selected:false
2. Re-generate the client
3. Add the layer in the client. The layer is selected.

What is the expected output? What do you see instead?
The layer should be deselected.

What version of the product are you using? On what operating system?
1.2-rc1

Please provide any additional information below.

[deleted issue]

What steps will reproduce the problem?
1. Load a map in the browser (any browser that allow zooming)
2. Zoom the page (usually using "Ctrl +", but since this key combination is 
already grabbed by OpenLayers, the zoom as to be done using the browser menu)
3. Click on the layer to trigger a feature request

What is the expected output? What do you see instead?
OpenLayers should reply with a feature request response. Instead, nothing is 
shown.

What version of the product are you using? On what operating system?
Any OS, probably any version of AtlasMapper.

Please provide any additional information below.
The problem is due to the Browser reporting a click on fraction of pixels. The 
feature request works if the value are cast to int before been sent to the 
server.

What steps will reproduce the problem?
1. Open the AtlasMapper in IE9
2. Try to change the base layer, or add a layer. In the Add Layer dialog trees 
don't work and layers can't be selected.

The opacity slider does not work correctly as well.

What version of the product are you using? On what operating system?
Windows 7 with IE9

Please provide any additional information below.
The GeoExt library used by the AtlasMapper does not work correctly in IE9. A 
partial attempt at a fix was done by adding a tag to tell IE9 to emulate IE8, 
with out this none of the AtlasMapper worked.

What steps will reproduce the problem?
1. Create a map
2. Add a layer twice
3. Choose a different style all layers
4. Click the save state button

What is the expected output? What do you see instead?
The 2 layers should conserve their style. They both share the same style.

What version of the product are you using? On what operating system?
1.3-rc3

Please provide any additional information below.
This bug has probably been in the application since the first release of the 
save state.

[deleted issue]

[deleted issue]

The 'Client base URL', 'Generated File Location' fields in the client 
configuration dialogue become linked when multiple client configuration 
dialogues windows are opened. Changing between tabs on one dialogue triggers a 
copying and moving of these fields from the second dialogue.

What steps will reproduce the problem?
1. In the AtlasMapper server configuration create a new client. Open the 
advanced tab. Scroll down to watch the 'Client base URL' and 'Generated File 
Location' fields.
2. Open a second pre-existing client and go to the advanced tab. 
The 'Client base URL' and 'Generated File Location' fields on the new client 
will disappear and be added to the pre-existing clients setting, creating 
duplicates.

The dialogues should be independent.

[deleted issue]

What steps will reproduce the problem?
1. Load a PNG layer which has alpha pixels (such has hillshading) in IE8 or IE7.
2. Change the opacity to 80% ~ 90%.
3. The layer become all black.

What is the expected output? What do you see instead?
The layer should become more transparent, has it appear in other browsers.

What version of the product are you using? On what operating system?
IE8 and IE7 on Windows

Please provide any additional information below.
It's a bug related to the way Internet Explorer handle transparency on PNG.

What steps will reproduce the problem?
1. Create a data source that is pointing to a service that returns a 
capabilities document that is broken. (See the attached broken capabilities 
file)
2. Add this data source to a client.
3. Build the client.

What is the expected output? What do you see instead?
No warning is provided that the datasource was broken and as a result none of 
the layers from the source appear in the client.

What version of the product are you using? On what operating system?
1.2-rc1, windows

What steps will reproduce the problem?
1. I install 1.0 with windows 2008 server. The map can be shown under godiva2 
(the default viewer of ncwms)
2. I add the sources with full url: 
http://152.83.64.47:8080/ncWMS/wms?SERVICE=WMS&REQUEST=GetCapabilities&VERSION=1
.3.0
3. The new layer filled the full maps when I add a layer from ncwms
4. An error message show "The CRS EPSG:900913 is not supported by this server" 
when I right clicked the figure.
5. The same error message is got when I change project to epsg:4326 in the 
client setting.

What is the expected output? What do you see instead?

I expect view a new layer in the map window. A pink figure fill the whole map.

What version of the product are you using? On what operating system?
ncwms 1.0, AtlasMapper 1.3, XAMPP 1.8.1, Tomcat 7.0.30, JRE7, windows 2008

Please provide any additional information below.

What steps will reproduce the problem?
1. Go to the layer options
2. Change the value of the opacity slider
3. Move the legend window (or any other window) on top of the opacity slider

What is the expected output? What do you see instead?
The opacity slider is not completely hidden by the window, the slider's "thumb" 
is shown on top.

What version of the product are you using? On what operating system?
All OS

Please provide any additional information below.
The problem can be fixed by setting the slider property "topThumbZIndex" to 
"auto". Note that this property is NOT documented in the ExtJS API.

[deleted issue]

What steps will reproduce the problem?
1. Load a client with a NCWMS layer.
2. Go to option panel.
3. The layer reload even if no options has been changed.

What is the expected output? What do you see instead?
The layer should not reload if the options haven't changed.

What version of the product are you using? On what operating system?
v1.0 (OS independent)

Please provide any additional information below.
Need to add a check on the option values, for NCWMS date/time field, to avoid 
trigger the reload (change) event if the values haven't changed.

[deleted issue]

What steps will reproduce the problem?
1. Fresh install of the AtlasMapper.
2. Create the demo client

What is the expected output? What do you see instead?
The demo client does not have the add and remove layers enabled by default.

What version of the product are you using? On what operating system?
1.3-rc3

Workaround:
Go to the client configuration/advanced and check the "Show Add [+] and Remove 
[-] layer buttons"

[deleted issue]

What steps will reproduce the problem?
1. Load a KML to the map
2. Load the same KML in Google earth
3. The layer looks much better in Google earth

What is the expected output? What do you see instead?
The KML should look similar in both softwares.

What version of the product are you using? On what operating system?
1.3

Please provide any additional information below.
OpenLayers do not provide complete KML support. Extending the KML layer class 
should allow the application to workaround this issue. Adding support for KMZ 
would also be a very nice improvement.

[deleted issue]

What steps will reproduce the problem?
1. Add 2 layers that has the same grand-parent folder but not the same parent 
folder
2. Remove one of them
3. The grand-parent folder get deselected, even if it still contains something.

What steps will reproduce the problem?
1. Generate a client using data source that produce errors.
2. The client generation is aborted, but the error message is hopeless: "See 
server logs"

What is the expected output? What do you see instead?
Having a list of errors that explains what goes wrong during the generation, 
and with which data sources.

What steps will reproduce the problem?
1. Create a client, do not set the list base layer fields
2. Generate the client
3. Go to list.html

What is the expected output? What do you see instead?
The layer preview border should be around the image. Instead, it's of a fix 
width/height of 200x180.

What version of the product are you using? On what operating system?
1.2

Please provide any additional information below.

What steps will reproduce the problem?
1. Create a new client using only one data source
2. Edit the client
3. The data source is not checked, so the generation doesn't work properly

What is the expected output? What do you see instead?
The client should have the data source chosen when it was created.

What version of the product are you using? On what operating system?
Introduce around version 1.0, fixed in 1.2.1

Please provide any additional information below.
An easy work around for this bug is to re-select the data source after creation.