All Projects

When calling OpenLayers.cdauth.NameFinder._closeAutoSuggest(), not only the timeout for connecting to the namefinder has to be aborted but also the actual loading (execution of NameFinder.find()). Otherwise the autosuggest box might open even though the focus is not in the input field anymore.

Line: 1681
Char: 6
Error: Object doesn't support this property or method

White spaces have to be removed properly from the output of the JSP pages. For example the GPX output will not be valid XML else.

It will probably have to be configured in Maven that all %>\n are replaced by %> in the JSPs before they are compiled.

The replacement has to work together with maven-jspc-plugin.

Sometimes, the analysation of too large objects is requested. They don’t fit into memory, which causes osmrmhv to re-fetch loads of objects from the API. To temporarily avoid that (until #63 is implemented), implement a time limit for requests that kills an analysation once it lasted for 10 minutes.

History Viewer takes very long time to analyse even small relations as it has to fetch the history of all ways and nodes.

Instead of having a long-loading page, the analysation should be started in the background. A static page should be cached that is available for 24 hours. The user should be redirected to that page immediately and it should reload itself frequently. There should be an option to open an alert box or to send an e-mail when the analysation is finished.

Relations that consist of one segment that is a closed circle are not analysed properly in Route Manager.

Relation 375627 is an example.

When multiple AjaxProxyXMLHttpRequests are running at the same time, some of them seem to get lost. This happens very often in all browsers except Firefox.

As soon as the routing and the master branch are merged again, split up prototypes.js into one file per class and use a build tool.

When the memory runs low, drop items from the cache. Use SoftReferences for that.

The error is in FacilMap.Util.addCSSRule() as document.styleSheets[0] is not defined.

Make it possible again in Route Manager to refresh a relation from the server without using the local cache.

Find a simple mechanism to cache the relations that contain a GeographicalItem. Currently, these are cached in the object itself, which is ineffective as objects are replaced regularly.

The tag diff that was previously available in the PHP version of OSM History Viewer should be implemented in the JSP version.

The distances to the next segment in the Route Manager segment table should be clickable to zoom to the gap between the two segments.

With high zoom levels and in south-eastern positions, the coordinate grid lines disappear reproducably. This could perhaps be caused by a bug in OpenLayers. The coordinate numbers are still displayed, though.