You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's produced by using imposm to import the linestrings for bridges, and ogr2ogr to import the dpwh geojson into postgis, and then running a query to find the OSM nodes close to the DPWH locations. Based on that I created JOSM load_and_zoom URL's, but other types of urls can be created too of course.
Future improvements could be to create urls that prompt JOSM to create tags, for semi-automatic mapping. Automated compliance check (using man_made or highway for example) is also possible.
Let me know if this is helpful, I'm planning to release the tools/scripts (docker+nodejs+postgis) opensource and see if i can help out a bit more.
Cheers
ps the distance from DPWH locations it scans for OSM nodes is 200m right now. This can be adjusted.
The text was updated successfully, but these errors were encountered:
@coostendorp , that looks awesome! Thank you for your effort. The candidate IDs of the OSM elements can be fed back to the tasking manager instead of the location.
Unfortunately, we haven't completed the clean-up and processing of the dataset yet.
We hope you will continue with your plan to release the tools/scripts that made this possible, because they can certainly help create better micro-tasking tasks! Thank you!
Hey all, I am playing around with GIS related tech, and came across this project, and did some tooling (that i will share separately later).
An early result is the following sheet: https://docs.google.com/spreadsheets/d/1tPG7NJx7EuEXjY7HCg8oY9Cyqwz1H0JrXsSf5dyE_k0/edit?usp=sharing
It's produced by using imposm to import the linestrings for bridges, and ogr2ogr to import the dpwh geojson into postgis, and then running a query to find the OSM nodes close to the DPWH locations. Based on that I created JOSM load_and_zoom URL's, but other types of urls can be created too of course.
Future improvements could be to create urls that prompt JOSM to create tags, for semi-automatic mapping. Automated compliance check (using man_made or highway for example) is also possible.
Let me know if this is helpful, I'm planning to release the tools/scripts (docker+nodejs+postgis) opensource and see if i can help out a bit more.
Cheers
ps the distance from DPWH locations it scans for OSM nodes is 200m right now. This can be adjusted.
The text was updated successfully, but these errors were encountered: