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)
It would be really useful if maxweightrating and maxweightrating:hgv could be included on the map, as virtually all roads in the UK with a weight limit use this tag. Nathan A RF (talk) 12:32, 31 August 2021 (UTC)
Also I've noticed that tags marked with 'forward' or 'backward' don't show at all. Could this be fixed too? Nathan A RF (talk) 12:02, 4 September 2021 (UTC)
Is it still maintained?
I would have appreciated if you contacted me first before changing the mapheight map wiki page and change the website. Would you like to propose a pull request? Mmd (talk) 12:52, 1 December 2021 (UTC)
- Hello. Are you still willing to maintain the project? If yes, could you please unarchive the project? We only saw that it did not get any update in quite some time and issues were not being addressed. Here are our patches so far: https://github.com/Yogurt4/osm-maxheight-map/commits/master The software would need its library patched badly, because some of them are close to a decade old. We have also noticed that you seem to have hardcoded the dev overpass endpoint. After some experimentation, we realized that the reason is that your algorithm regularly overloads the product servers (that should be used for this). Any chance to fine tune this? Are you willing to cooperate in such improvements, or what are your plans for it? Thanks. -Bkil (talk) 16:12, 1 December 2021 (UTC)
- Thanks for your interest in the project. I moved it to archive mode in the meantime, because there wasn't much interest anymore. Now that I have unarchived the project again, you could create some pull request with your changes. Ideally your changes should be split up into several smaller commits, so it's easier to review and apply single commits if needed. I can merge them and deploy a new version afterwards. I'm using the dev instance, because I'm also operating this Overpass dev instance. ;) There's no easy way to improve the performance on the production server, as respective enhancement requests haven't been addressed for years. And yes, you need changes in the Overpass API code, optimizing queries alone will not work. Mmd (talk) 16:24, 1 December 2021 (UTC)
- As you've already noticed, the code is pretty old, and nowadays you wouldn't need php anymore. So that change is fine. Mmd (talk) 16:38, 1 December 2021 (UTC)
By the way, quite a few are using your tool, here's a recent conversation about it:  Have you considered creating a SIG/working group for it on the OSM wiki or would there be some other page to show support and spread the word? Should there be perhaps a tag that users should add to their changesets for example? I think not many know about this, but the issue it solves does seem to come up from time to time, so maybe there should be some more wiki interlinking, news items about it or an article through WeeklyOSM after a refresh? -Bkil (talk) 16:43, 1 December 2021 (UTC)
- I pushed most of your proposed changed to the site now, including the Hungarian translation, There may be some (hopefully minor) glitches left, like the Firefox fix I still need to commit. The code is still pretty outdated. Any sort of decent modernization would take much more time, and I didn't want to delay your changes for too long.
- IIRC, the site was featured at least three times on WeeklyOSM. I don't recall much other activities to promote the site. I see my focus mainly on the tool creation side of the house, less so to set up a working group (I don't have the bandwidth to contribute to such a group). Mmd (talk) 20:06, 4 December 2021 (UTC)
Add support for imperial/US customary units
It would be good if this tool could support feet and inches. On github there is a request for this: https://github.com/mmd-osm/osm-maxheight-map/issues/3
In the UK, although there a growing number of either dual metric/imperial or just metric signage, there are still many older signs only using feet and inches.
In the USA, I assume most, if not all of the signs also use feet and inches.
Might be a bit of work to add for example a feet/inches slider, but even just parsing imperial units so they are recognised rather than being coloured red all the time would be good. :) GinaroZ (talk) 22:48, 17 December 2021 (UTC)