Discussion page for Maxheight Map
Please add your comments, questions, bug reports, etc. below.
Move section "Sidebar" up
Sidebars are a GUI element which are not common in the OSM-Map context. Therefore it should be located at a more prominent place in the documentation.
I suggest before the section "Check existing values (Overlays)" or even before the section "Missing maxheight Tags". --EvanE (talk) 14:46, 6 March 2013 (UTC)
- I changed the default logic for the 'West' Sidebar to always show up if screen width permits (more than 800 pixel wide). This way, a user should see all available options on the map right from the start. As the sidebar description itself also takes up most of the space in the table of contents, it shouldn't be necessary to move sections around anymore. HTH. --Mmd (talk) 19:22, 10 March 2013 (UTC)
Recommendation for mass import of bridge data
I discovered this US DOT FHA supplied bridge data , what is the the recommended way to import mass data into OSM for Maxheight and other truck related fields for bridges? --Jnimble (talk) 21:29, 15 August 2017 (UTC)
- The import process is quite involved (licensing, community approval, documentation, etc.), see Import/Guidelines for all the gory details. Mmd (talk) 07:45, 16 August 2017 (UTC)
I believe that displaying direction-specific restrictions (e.g. hgv:forward=destination) could greatly benefit the map. It would be better to display both lanes separately (I like how this map does this with parking restrictions) but marking it with the same colours and in dashed line would also work great (and points can be displayed the same way). --VileGecko (talk) 15:16, 29 August 2020 (UTC)