-
Notifications
You must be signed in to change notification settings - Fork 926
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move export tab to right hand tool pane #3040
Comments
I also never use the export. But this option is one of the mayor difference to other mapping data sources. |
I find the export button a bit confusing, because the API is reserved for editing purposes. Maybe it should be renamed to "get the data" or something like this, with links to the planet and extracts, it is already there and shows when you select an area that is too big: "This area is too large to be exported as OpenStreetMap XML Data. Please zoom in or select a smaller area, or use one of the sources listed below for bulk data downloads." |
Just for clarification I am not asking to remove the feature, just move it's view to another button that is less-prominent. |
Yes we're well aware that this is really just a trojan horse because you didn't think you'd be able to persuade us to add a Wiki tab unless you first removed something else - it would probably have helped your case here if you had been up front about that when opening this. Personally I would be quite happy to remove the export button because I can't see that it gets any significant use because it's not really very useful. It's one of those things that seems reasonable on the surface but because it relies on an API that is only designed to deliver up small areas it's hard to see that it has much practical use, as the fact that we've had to add lots of hints on how to get larger areas to the panel! |
This was not my intent at all. I just thought of the 2 improvements when thinking about improving the heading in-general. |
Current limit of 50'000 nodes is only in place for compatibility reasons with the Rails port, most likely to have sane limits for memory and cpu consumption on the Rails port in place. I don't think the current cgimap implementation was specifically designed to only serve up small areas. I'm not aware of any technical limits that would break it when exceeding 50k nodes (e.g. by increasing the respective config settings). |
Well no but it's never going to scale to downloading the sort of size of area most practical uses would require nor do we particularly want it to when extracts are a much better solution. |
Apologies if that was not your intention @lectrician1 it just seems like an extraordinary coincidence that the two were opened at the same time. I was actually under the impression that they were pull requests, and it seemed implausible that somebody would have done the large amount of work that moving this would involve on a whim but I see that they are actually just issues. |
Well, do not think somebody wants to do something bad. Maybe he just thought about the UI as a whole and stumbled upon this. it seems like he thought about it as well, because the issues were made close to another, timewise. If he would have made this issue after you declared you do not want to change this, maybe. But even then, that does not change anything - he is correct, this button should not be that porminent up there, it should be in the sidebar. |
Export was moved in #5151, therefore this issue may no longer be relevant. If you still want to move Export elsewhere or rename it, it's better to open a new issue. |
The
Export
button to the right of theEdit
andHistory
buttons is rarely-used.The majority usage population of the OSM website are mappers like me.
I never have used the
Export
feature and probably never will because other file export options such as from the Overpass API and JOSM's import are much more convenient.Also, the pane does not even explain that it's exporting in the
.osm
format, offer to export in other formats say through a dropdown menu, and only has links to other sites.It does not make sense to have it as a top-level heading link.
I think it's pane contents should be either:
Share
button on the options pane right of the map and the hover text be renamed toShare/Export
.Here is what the site would look like without it:
The text was updated successfully, but these errors were encountered: