2
2
Fork
You've already forked overpass-api-python-wrapper
2

implement basic OSM types and option to return them #148

Open
opened 2022年03月23日 18:33:06 +01:00 by mvexel · 4 comments

Right now we return raw-ish data (JSON / dict, GeoJSON, CSV) which is fine but puts the burden of parsing it into OSM features on the user. Since extracting OSM features is the first thing anyone would probably want to do, it would seem to make sense to implement basic OSM types (Node, Way, Relation) and offer the option to return collections of those instead.

We could borrow from https://github.com/osmlab/osmdiff/blob/master/src/osmdiff/osm/osm.py

(As a bonus, these already implement __geo_interface__, see #147)

Right now we return raw-ish data (JSON / dict, GeoJSON, CSV) which is fine but puts the burden of parsing it into OSM features on the user. Since extracting OSM features is the first thing anyone would probably want to do, it would seem to make sense to implement basic OSM types (`Node`, `Way`, `Relation`) and offer the option to return collections of those instead. We could borrow from https://github.com/osmlab/osmdiff/blob/master/src/osmdiff/osm/osm.py (As a bonus, these already implement `__geo_interface__`, see #147)
Author
Owner
Copy link

I updated osmdiff recently and the __geo_interface__ interfaces are in better shape now. They still require some testing, especially relations.

I'd love to consider this for the next point version.

I updated `osmdiff` recently and the `__geo_interface__` interfaces are in better shape now. They still require some testing, especially relations. I'd love to consider this for the next point version.
Vectorial1024 commented 2024年04月24日 12:58:30 +02:00 (Migrated from github.com)
Copy link

I noticed another Python library overpy, it seems to provide some basic util functions to loop over overpass results. Would overpy be good enough for this?

I noticed another Python library `overpy`, it seems to provide some basic util functions to loop over overpass results. Would `overpy` be good enough for this?
Author
Owner
Copy link

I don't know about overpy more that that it offers comparable functionality to this library. If it fits your use case, by all means go ahead and use that (for now)!

I don't know about `overpy` more that that it offers comparable functionality to this library. If it fits your use case, by all means go ahead and use that (for now)!
mvexel added this to the v1.x milestone 2026年05月04日 01:51:45 +02:00
Author
Owner
Copy link

we can revisit after the 1.0 plumbing is done

we can revisit after the 1.0 plumbing is done
Sign in to join this conversation.
No Branch/Tag specified
main
tutorial/d1-httpx-nvim
0.8.x
dev-contributor-tooling
1.0-dev
dev
feature/api-modernization
maintenance/base-0.8
maintenance/geojson-fixtures
archive/async-models
maintenance/endpoint-guard
maintenance/live-query-tool
maintenance/modernize-plan
archive/dev-prebaseline-20260502
archive/modernize
archive/chore-tests
chore/poetry
archive/readme
v0.8.2
v0.8.1
v0.8.0
v0.7.2
0.7.1
0.7.0
0.6.1
0.6.0
0.5.7
0.5.6
0.5.5
0.4.0
0.1.0
0.0.2
0.0.1
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
mvexel/overpass-api-python-wrapper#148
Reference in a new issue
mvexel/overpass-api-python-wrapper
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?