|
92 | osmrmhv | osmhv | Bug Report | Critical | http://osmhv.openstreetmap.de/ is timing-out and unreac... | Unconfirmed | |
Task Description
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. |
|
87 | osmrmhv | unknown | Bug Report | High | java.lang.NullPointerException | Unconfirmed | |
Task Description
http://osmhv.openstreetmap.de/changeset.jsp?id=21344911 gives java.lang.NullPointerException |
|
78 | osmrmhv | osmhv | Bug Report | Medium | The remote nodes is not visible on the map | Unconfirmed | |
Task Description
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. |
|
89 | osmrmhv | unknown | Bug Report | Medium | eu.cdauth.osm.lib.APIError: Server sent no data. | Unconfirmed | |
Task Description
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. |
|
65 | osmrmhv | unknown | Bug Report | Low | gpx.jps and disjunct polygons | Assigned | |
Task Description
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 |
|
79 | osmrmhv | unknown | Bug Report | Low | It seems the analysis can't be repeated, useful when th... | Unconfirmed | |
Task Description
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!) |
|
90 | osmrmhv | unknown | Bug Report | Low | Relation includes exclaves or enclave | Unconfirmed | |
Task Description
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) |
|
91 | osmrmhv | unknown | Bug Report | Low | Relation includes exclaves or enclaves | Unconfirmed | |
Task Description
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) |
|
8 | osmrmhv | osmhv | Bug Report | Very Low | Re-adding of a segment to a relation shows wrong author... | Assigned | |
Task Description
When a segment as been removed from a relation and later been re-added, the first “adder” might be shown instead of the second. |
|
63 | osmrmhv | lib | Feature Request | Low | Asynchonous API | Assigned | |
Task Description
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. |
|
69 | osmrmhv | osmhv | Feature Request | Low | Please make hovering to not open below but to right of ... | Unconfirmed | |
Task Description
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. |
|
70 | osmrmhv | osmrm | Feature Request | Low | change gpx export from route to track | Unconfirmed | |
Task Description
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. |