Open noelmcloughlin opened 3 years ago
Thanks for the proposal. There will be some improvements on QuickOSM in the coming weeks, so indeed, it would be nice to avoid a fork if possible.
I wasn't too much aware of the OHM project.
Support for OHM should be incrementally added to QuickOSM Plugin.
Can you describe what do you plan to add "incrementally" ? Linked to #281 which is the first one.
OSM and OHM have 95% overlap.
Can you also describe what is the 5% ? Do you mean some features in QuickOSM will raise an error if used with the OHM API ?
I'm a novice but OHM uses the same technology stack as OSM - for example, I used JOSM with OHM by just changing endpoints.
I have very little experience in QGIS and digital mapping so I'm cannot give expert opinion on incremental (or big bang) support for OHM end users - maybe QuickOSM could provide a QuickOHM menu option which talks to OHM endpoints.
All features in QuickOSM should work with OHM API without error is my understanding.
I have just merged #281 so in the next version of QuickOSM, users can switch the Overpass server. In the meantime, you can edit the JSON file in your profile to add this server.
@Gustry - that sounds great. Being able to switch server endpoints should keep OHM in the loop!
Being able to switch server endpoints should keep OHM in the loop!
It's already possible, in the "Configuration" panel, or also in the Processing algorithm if you are in QGIS Modeler
Do we need to keep this ticket open or is there something else you expect ?
Hi @Gustry @jeffreyameyer It would be good to have a QuickOHM menu option in this QGIS plugin. Is that something that is possible? So QGIS can support both OSM and OHM which are different mapping infra providers.
Can you also describe what is the 5% ? Do you mean some features in QuickOSM will raise an error if used with the OHM API ?
OHM’s Overpass API instance is 100% compatible with OSM-based instances. The only thing that differs is a few tagging conventions. Users of this plugin would need to be familiar with these tagging differences when crafting custom queries in QuickOSM, but otherwise I don’t see anything in QuickOSM that would be affected.
Is your feature request related to a problem? Please describe
The plugin does not support OHM.
Describe the solution you'd like
Support for OHM should be incrementally added to QuickOSM Plugin.
Describe alternatives you've considered
I considered forking QuickOSM to QuickOHM but that would bad idea - OSM and OHM have 99% overlap probably.
Additional context