Implement an API call like http://www.openrailwaymap.org/api/switch.php?switch=23&ref=KNG or http://www.openrailwaymap.org/api/switch.php?switch=23&name=Neuss+Gbf to request the position of a switch with the given ref value that is part of the given facility, specified with ref or name.

This API request should also be integrated into the search engine, e.g. searching for "switch 23 neuss gbf" or "w23 kng" should return all matching switches. Clicking on such a search result should center the map on the position of the requested switch.

Calling http://www.openrailwaymap.org/index.php?switch=23&ref=KNG or http://www.openrailwaymap.org/index.php?switch=23&name=neuss+gbf should center the map on the position of the requested switch.

Improve the support for mobile devices such as smartphones and tablets.

• Optimize the existing web app for mobile devices
• Develop a native app for Android, iOS, Windows Phone, Firefox OS, etc. with higher performance and offline functionality

Implement an API call like http://www.openrailwaymap.org/api/route.php?ref=2610 to request the trace of a route with the given ref and return a single geometry built from all ways that are part of the requested route. The geometry could be returned as GPX, GeoJSON, simple JSON, KML or GML. For the output formats see also Issue #7.

This API request should also be integrated into the search engine, e.g. searching for a route number like "2610" should return all matching routes. Clicking on such a search result should highlight this route on the map and pan the map to the outer envelope of the way.

Calling http://www.openrailwaymap.org/index.php?ref=2610 should highlight the requested route on the map and pan the map to the outer envelope of the way.

Instead of ref the software should also support a parameter name.

To avoid wrong data which is related to the direction of a way, JOSM should show a warning when the user tries to

• reverse the direction of ways which consists of signals
• reverse the direction of ways tagged with railway:bidirectional

JOSM already shows a warning message when a way tagged with maxspeed=forward/backward is reversed.

The name=* tag should be rendered on sidings, yards, spurs, ... too, not just on main tracks.

Train protection systems (German "Zugsicherungssysteme") should be rendered in signalling layer.

Here a first draft of a rendering scheme for the german train protection systems:

railway:pzb=yes, railway:lzb=yes => GREEN

railway:pzb=yes, railway:lzb=no OR railway:pzb=yes, railway:lzb=null => RED

railway:pzb=no, railway:lzb=yes OR railway:pzb=null, railway:lzb=yes => YELLOW

railway:pzb=no, railway:lzb=null, railway:pzb=no, railway:lzb=no => BLACK

railway:pzb=null, railway:lzb=no OR railway:pzb=null, railway:lzb=null => GRAY

railway:etcs=yes/no/0/1/2/3 => ???

Please render maxspeed:forward and maxspeed:backward in maxspeed layer.

Possible implementations:

Equal altering of way colour
Altering between the two colors, and speed could be written with an arrow to show the direction, like this: < 80 - 100 >

Altering of way colour depending on direction
A stroke of 2/3 length with the colour of maxspeed:forward, a stroke of 1/3 length with the colour of maxspeed:backward.

Arrow icons
Arrows: <---> <---> <--->
Colour: aaabb aaabb aaabb
a = maxspeed:forward=*
b = maxspeed:backward=*
left = forward direction of the OSM way

Render way borders
This solution needs the offset property of MapCSS.
Render the right half of the way with the color of maxspeed:forward=*, the left half of the way with maxspeed:backward=*.

Currently non operational lines, railway=construction (and maybe others), show up the way as currently operational lines in the maxspeeds view. Lines of the past and lines of the future should be clearly distinguishable from actual lines or moved to and different view.

The search engine should also consider names in other languages tagged with name:=* to allow the user to search for stations without knowing it's native name.

Example: A user should find stations in Moscow not just by typing in "Москва", but also by entering "Moskau" (German).

Make the data accessible via a Web Feature Service (WFS) and formats such as GML.

Use https://github.com/humangeo/leaflet-tilefilter for optimizing the used basemaps.

Reducing the contrast or making the background transparent should improve the readability of the whole map.

The currently used https://github.com/Zverik/leaflet-grayscale would become redundant.

The search engine/API should perform an internal transliteration of special chars for a more tolerant matching of names. Otherwise it is difficult for users to search for a station in another country due to different keyboard layouts without special characters.

Examples:

• Děčín -> Decin
• Düsseldorf -> Dusseldorf
• Rzeszów -> Rzeszow
• ...

Include bridges and tunnels into the search engine by considering the tags bridge:name=* and tunnel:name=*.

The canvas overlay is not rendered in Internet Explorer 10.
It is supposed to be a bug in Kothic JS (https://github.com/kothic/kothic-js).

Implement a function that allows the user to export any map view as PNG bitmap image or PDF document and download it. It should be possible to set a custom bounding box and scale.

Links that might be interesting:

• https://github.com/mapbox/leaflet-image
• http://www.nihilogic.dk/labs/canvas2image/
• implementation used on http://www.openstreetmap.org/

Libraries for PDF generation:

• https://parall.ax/products/jspdf
• http://pdfmake.org/#/
• http://pdfkit.org/
• http://mrrio.github.io/jsPDF/

A horizontal rendering artefact is shown on http://www.openrailwaymap.org/?lang=en&lat=47.000392519634396&lon=8.387374877929686&zoom=10&style=standard See attached screen shot. (On Firefox 24.0). The artefact is limited to some zoom levels. It does not show on other zoom levels.

Add a map rendering style that visualizes track gauges tagged with gauge=* and maybe also racks tagged with rack=*.

When I type "Rzeszow" then search engine should find "Rzeszów Główny", not only when I type "Rzeszów".

Add a data validator feature to make it easier for users to check the validity of the mapped data and correct mistakes.

This could be realized with these methods:

• A separate map layer
  • highlighting data mistakes and showing a short hint what the problem is
  • needs a connection to the editors ("JOSM Remote Plugin" or iD-link)
  • easier to browse the map than in an editor
• A JOSM plugin
  • would make it easy to correct the mistakes instantly

It is useful to list up all data checks in the OpenStreetMap Wiki.

Build a page showing interesting statistics such as:

• Number of stations in the world
• Number of stations per country
• Total length of railroad tracks in the world
• Total length of railroad tracks per country
• ...

Feel free to add more aspects!

Create a typfile to create Garmin gmapsupp.img files for using OpenRailwayMap offline on Garmin GPS devices.

After that, set up a rendering stack to offer ready-to-use maps for downloading.

Write a detailled documentation in the README.md file about the installation of OpenRailwayMap.

Add an option below the search box and to restrict a search request to the currently showed bounds of the map.

In the backend this needs to implement an additional URL parameter for API requests to restrict search request to a specified bounding box.

Add a reverse geocoding API. After sending a lat/lon position, the API should return information such as:

• Track ref (e.g. 'Track 4')
• Line ref (e.g. 'Line 2610')
• Track position (e.g. 'km 42.56')
• Current maxspeed
• Next signal
• If the given position is within a station, halt or other facility, return name, uic_ref, short name, etc.
• Next station, halt or other facility
• ...

Also think about a UI integration of this API.

Improve the rendering of signals so that it is clear which signal belongs to which direction. Therefore align signals on the track depended on their orientation

This may need some modifications of Kothic JS.

The performance of the browser-rendered map is still very bad. Find ways to speed up the rendering for a nicer user experience.

As $_GET['id'] is passed straight into javascript maybe consider using json_encode instead.

http://www.openrailwaymap.org/?id=alert('hi')

This feature is on main OpenStreetMap page. Current position is saved in cookie and when I reopen map then I don't must search it again.

The permalink should save the selected background map layer.

The API should return the data not just as JSON, but also in XML or GML format.

Zoom level 14 shows more recent data than zoom level 15 (see attached screen shots)

• data has been changed two day ago
• screen shots have been take at the same time
• seen on Firefox 25.0
• [zoom level 14]
  
• [zoom level 15]
  

The map icons should be organized in a folder structure.

Example where this occurs:

• http://www.openrailwaymap.org/?lang=en&lat=52.44811097993511&lon=13.335886895656586&zoom=18&style=maxspeed (proposed)
• http://www.openrailwaymap.org/?lang=en&lat=51.23910950635014&lon=11.594760417938232&zoom=15&style=maxspeed (construction)
• http://www.openrailwaymap.org/?lang=en&lat=47.98457199594167&lon=7.846025973558426&zoom=19&style=maxspeed (abandoned)

(as I think about it, rendering construction might be useful, but it should be clearly distinguishable. like pale or dashed or both.)

Evaluate live-rendering of bitmap tiles with Mapnik. This would probably effect a faster and smoother map than a browser-rendered canvas map.

The tagging should be expended to more countries:

1. The country-specific tagging documentation in the OSM wiki should be extended: http://wiki.openstreetmap.org/wiki/OpenRailwayMap#Country-specific_tagging
   There it is specified how to country-specific features - e.g. which tags have to be used for a certain signal in a certain country. You can also add some tagging examples for each country.
2. Based on task 1, add JOSM preset files for more countries.
   A list of currently available presets: https://github.com/rurseekatze/OpenRailwayMap/tree/master/josm-presets

The night bus routes 3092389 and 3092390 are members of a tram route master relation. Therefore the maxspeed of the member highways is shown in the maxspeed layer. This should not be the case.

http://wiki.openstreetmap.org/wiki/Taginfo/Projects

It would be nice to have an edit link to edit on the current map position.

Add a rendering style with the focus on the history of the railroad network. It should highlight disused, abandoned and razed tracks, stations and amenities and visualize dates tagged with start_date=* and end_date=*.

A very nice feature would be a "time machine mode": By selecting a date, e.g. with a zoomslider, the user can visualize the railroad network at the selected date.

Grayscale layers are not shown in Internet Explorer 10.

It seems that the leaflet-grayscale plugin does not support IE properly. A bug report at this project may be helpful.

The current design of the website is not very nice-looking.

Implement a feature that allows users to change the rendering style and load own stylefiles.

This would it make easier for others to create new rendering styles or improve existing ones.

In order to make sharing OpenRailwayMap links more conveniant (and thus more popular) the URL to the current map view should be continously updated. Just like the main OpenStreetMap map one could easiler copy&paste the URL for the current map view from the browser's URL line.

Evaluate forms of integrating live traffic based on timetable data and realtime positions (see http://www.apps-bahn.de/bin/livemap/query-livemap.exe/dn?L=vs_livefahrplan&livemap=yes as an example).

Develop an algorithm which generates track diagrams from OpenStreetMap data by simplifying the data and rendering it as a bitmap or SVG image.
Example: http://fahrweg.dbnetze.com/file/2420906/data/KNIV_ISR.svg

This track-diagram-generator should be accessible with an API request such as http://www.openrailwaymap.org/api/trackdiagram.php?ref=Nievenheim&operator=DB.

Also think about an integration of this generator into the user interface.

The HTML code should be optimized, so that the website can be found with search engines.

It is also necessary to improve the texts because the description/extract that is currently shown by e.g. Google is not very informative.

Develop native apps for mobile devices.

They would offer some advantages compared to a webapp:

• offline mode
• higher performance
• better connection to GPS for mapping, geocoding, localizing and augmented reality
• connection to camera for mapping and augmented reality
• interfaces to timetable apps
• ...

Hi,
abandoned and razed railways often share a way with highways. In these cases the maxspeed of the highway is shown.
Example:
http://www.openrailwaymap.org/?lang=de&lat=49.31348478032425&lon=8.453121185302734&zoom=14&style=maxspeed

Highlight the bounds e.g. of a station when the user has clicked on a search result of this station.

Comparable to Google Maps which highlights the boundary of a city on the map. Example: https://maps.google.de/?q=buxtehude