I would personally find it less challenging than using the OSM API to bring OSM tags back into a shapefile and dumping it to ArcGIS Online.
But yeah, it's not like either option is super user-friendly.
Top-level
I would personally find it less challenging than using the OSM API to bring OSM tags back into a shapefile and dumping it to ArcGIS Online. But yeah, it's not like either option is super user-friendly. 3 comments
There are a few "easier" options I've seen out there, where you basically just edit a config file, and click "run". But step 1 is usually something like "pull this Docker image" or "clone this git repo", which is an automatic turnoff for a lot of folks. I do think there's some value in the model Esri's followed on this. They have an osm2pgsql service running updates at 15-minute intervals, and they make access to those services open to anyone. Those specific services don't have the specialized fields that Utah needs. I like to imagine if a wider group of organizations could coalesce around a schema and a geographic area of interest, maybe they could collectively support a shared instance. |
@jcarlson I hadn't realised how nerfed the shapefile is. Using it seems like a mistake.
But even asking people to do the pbf is going to discourage a lot of people.