osm_easy_api - Brand new Python package for parsing osm diffs and communicating with the osm api.Posted by kwiatek_123 on 7 March 2023 in English (English).
Hello! I would like to present a python package written by me.
What’s the point of this package?
This package was created to provide an easy way to create automated scripts and programs that use diff and/or osm api. The main advantage is the classes (data_classes) that provide data of elements (node, way, relation, OsmChange, etc.) in a readable way and the possibility to use them in diff and api without worrying about missing data or dictionaries. You can easily find nodes in diff, add a tag to them and send the corrected version to osm.
More on github
I would love to see your project written using this package!
Comment from 快乐的老鼠宝宝 on 7 March 2023 at 23:59
I’m glad to see this diary, I’m the author of another project Keqing (although the repository is currently owned by the organisation, I’m the only one who mainly maintains it), although it started very early but I’m only coding in my free time, because There are still many features waiting to be implemented, so I haven’t dared to introduce it to others. osm_easy_api looks very well developed, so I’m afriaid that I’ll be “reinventing the wheel” in my Keqing package. I actually noticed that we may have already worked towards the same goal, for example on parse data and quick extraction of data that have specific tags. Of course, I don’t have confidence in my own code, my implementation is also not concise enough. As the author of an OSM-related library also based on python, do you have any suggestions on how to reduce duplication of work I’m doing and calling between those 2 package each other?
(Besides, also looking forward to your comments on my humble work)
Comment from kwiatek_123 on 8 March 2023 at 20:54
Thank you for this long and nice comment. I tried to install your package but python can’t find it (I already created an issue). To reduce the amount of code involved in using your package and mine I would suggest that you standardise the element classes. (Either mine or yours). As you might have noticed on github, I don’t expect to be writing an .osm file parser anytime soon, so you can continue working on your package as I’m sure there will be users who need it. Perhaps in the future you can move the code to mine.
Comment from Mateusz Konieczny on 12 March 2023 at 07:01
It may be a good idea to post about it on https://community.openstreetmap.org/ and/or submit it to Weekly OSM and/or post on dev mailing list.
Comment from 快乐的老鼠宝宝 on 12 March 2023 at 07:11
WeeklyOSM to be released this week (usually at 10AM UTC every Sunday, which means that it is not a few hours away) has already collected news about osm_easy_api: https://osmbc.openstreetmap.de/article/28238 So stay tuned :)
By the way, is it possible to have emails sent to the Dev list automatically posted on the community?