William Edmisten <[email protected]> writes: > My name is William Edmisten (wcedmisten). I've been mapping in OSM for > almost a year, but have no relevant affiliation with any other > organizations. > > I am writing to propose an import of the HIDFL Hospital dataset > <https://hifld-geoplatform.opendata.arcgis.com/datasets/hospitals/explore> > (8,013 records), and to discuss possible ways in which this dataset could > be used.
As someone who has worked on a successful import, a word of caution: doing an import is almost certainly 10x harder than anyone who hasn't been all the way through it thinks. I don't mean to discourage you, but to calibrate expectations. It's not formally part of the norms, but I think imports should be done with code, basically a program that takes the OSM db as it is and the import db and produces a set of proposed editing actions (additions/conflations) and things to inspect (object in OSM but not in import). That can then be debugged before any changes are made. It is critical that it be automated so that it can be re-run with little effort. I wonder what quality checking you have done on the database. An example might be to look at a county and the contents of OSM vs the contents of the DHS database, and check that that everything in the DHS database that is in OSM matches, and that things not in OSM actually exist. This should be the output of the program I described in the previous paragraph. Greg _______________________________________________ Imports mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports
