All Projects

When a segment as been removed from a relation and later been re-added, the first “adder” might be shown instead of the second.

The Permalink saving of the visibility of search result markers should be moved to the Markers layer for more generic use.

To prevent memory leaks, the destroy() methods should be overloaded everywhere to remove member objects.

Make the list of permalinks expandable and hidden by default. Instead, display the tags and other information about the appropriate OSM element there:
- Requires change of the LonLat markers function (find out which element was clicked by talking to the API)
- Normally select ways or in reasonable cases relations (type=route)
- Shift/Ctrl+click change mode to way-select or node-select
- Requires change of the search result display:
- Get OSM ID from search results and load data from the API.

Perhaps also show directives when hovering the map?

As soon as Nominatim v2 is online (see http://open.mapquestapi.com/nominatim/), switch to it.

As long as no start and destination points have been searched for, display draggable markers in the input fields so that one can drag them on the map without having to type in a place name.

When performing a search with multiple results, selecting any of them but the first one and then reloading the page, the list of results is hidden (which is the desired behaviour). However, the previous choice was lost from the favourites, so when now trying to calculate directions, the first result is selected again. A cookie-based favourite solution is not acceptable as the page should still work as expected when sending a link to someone else.

Add layer(s) from http://openseamap.org/

Instead of fetching each object on its own, make the API asynchronous so that a list of required objects is aggregated and the request is performed at once. This has the following advantages:
- Multithreaded API requests, useful in case any API mirrors exist
- Proper solution to the problem of too large objects being analysed. When the all-at-once fetch fails because of memory restrictions, the object is too large.

Gpx extracting from a multipolygon relation with disjunct polygons results in only one polygon.

E.g. the relation [1] contains the borders North and East Tyrol, which are two disjunct polygons (no common node). The resulting gpx file [2] only contains the border East Tyrol.

[1] http://www.openstreetmap.org/browse/relation/52343
[2] http://osmrm.openstreetmap.de/gpx.jsp?relation=52343

Currently the hovering of properties list makes the screen very jumpy as the sizes of the properties lists are quite random, and selecting one below the currently hovered one in the list becomes impossible as the point where one is supposed to hover the mouse over changes immediately when the previously hovered one disappear and the new one appears.

The old Relation Analyzer exported relations as tracks (trk), osmrm now uses routes (rte).
Unfortunately, those can not be imported in josm and some other programs, and GPS units dont accept routes with many route points. The track format is easyer to handle.

The remote node is added to the map as a line where the start and end of the match. As a result, it is not displayed. If the coordinates of the end of the line to add 0.000001, it will appear as a dot.

How to reproduce:
- analyse a (still open) changeset
- wait for the changeset to close
- after the changeset has been closed, analyse it again with osmhv

Result:
osmhv shows the former analysis while this should have been repeated since the changeset was not closed the first time, and new changes have been done.

(Thanks for this useful tool!)

Can you add a "Notes" Layer (http://wiki.openstreetmap.org/wiki/Notes) besides the OSMBugs Layer?
At the moment there is no easy way to work with both systems.

Off-topic:
Thanks a lot. You are doing great stuff. I use facilmap all the day and recommend it to others. Thank you.

Hi,

OSB bug creation has been disabled on the OSB homepage.
Other apps have disabled it too and switched to OS Notes.

Would be cool if could disable bug creation, too.
see also:
https://wiki.openstreetmap.org/wiki/Openstreetbug

Regards
Werner

http://osmhv.openstreetmap.de/changeset.jsp?id=21344911

gives

java.lang.NullPointerException

Trying to see http://osmhv.openstreetmap.de/changeset.jsp?id=22395310 it' s displaying this error messagem:

eu.cdauth.osm.lib.APIError: Server sent no data.

OSM Route Manager fails, when Relation includes exclaves or enclaves. Example: http://osmrm.openstreetmap.de/relation.jsp?id=2083535 vs. http://www.openstreetmap.org/relation/2083535 (also: http://www.openstreetmap.org/relation/62743 or http://www.openstreetmap.org/relation/62408)

OSM Route Manager fails, when Relation includes exclaves or enclaves. Example: http://osmrm.openstreetmap.de/relation.jsp?id=2083535 vs. http://www.openstreetmap.org/relation/2083535 (also: http://www.openstreetmap.org/relation/62743 or http://www.openstreetmap.org/relation/62408)

http://osmhv.openstreetmap.de/ has been failing with the error: "The connection to the server was reset while the page was loading." for at least the last few days. Everything else on openstreetmap.de seems to be working.