Hi Riley, If you've checked a few and the quality looks good, then I think that's fine, and I'm okay these being imported.
However I think the import should: 1. Only import STATUS=YES, unless we know what STATUS=NO or STATUS=null means. 2. Leave out the refs/ids unless these are surveyable. 3. Convert the BBQ_TYPE_CODE to fuel=electric|gas|wood 4. Ensure you don't add duplicates (so don't import over the top of existing mapped bbqs) So the features are only tagged with: amenity=bbq fuel=* I don't mind either way if the source tag is used on the object or on the changeset. What tools/process were you going to use to get the file in shape? The way I'd do it is download the GeoJSON file at http://actmapi-actgov.opendata.arcgis.com/datasets/cce3d3c3ed9d4a5d894c26a3cf7f8757_0.geojson then just open it in JOSM with the GeoJSON plugin, and do the mass tag filtering/cleanup in JOSM with the search tool, then I'd use the Conflate plugin to merge with what's existing, probably keeping the original geometries. How do you plan to do this? On Wed, 10 Oct 2018 at 12:26, Riley Baird <ri...@mailo.com> wrote: > > On Mon, 8 Oct 2018 18:09:20 +1100 > Andrew Harvey <andrew.harv...@gmail.com> wrote: > > > On Sun, 7 Oct 2018 at 17:48, Graeme Fitzpatrick <graemefi...@gmail.com> > > wrote: > > > On Sun, 7 Oct 2018 at 16:19, Riley Baird <ri...@mailo.com> wrote: > > >> At present, the data is released under CC BY 4.0 international, so it > > >> appears that I would have to send a message requesting permission to > > >> use it in a way compatible with the OSM licence. > > > Have a look at > > > https://wiki.openstreetmap.org/wiki/Australian_Data_Catalogue - we've > > > already been given permission to use that info, together with a heap more > > > ACT data. > > > > ^ this, we already have the waiver completed for ACTMapi data which > > includes the BBQ dataset. > > Thanks, that makes things much easier! > > > On Mon, 8 Oct 2018 at 00:27, Mateusz Konieczny <matkoni...@tutanota.com> > > wrote: > > > What was your way of checking quality of this data? I had experience with > > > some > > > official data that was good enough to help with mapping (detection of > > > places where features > > > were not mapped) but was full of mistakes including poor locations and > > > nonexisting objects. > > > > I agree with this, I've seen both good and poor data, so it's a good > > idea to do some basic checking of the data quality before bringing it > > in. > > Right, is that just basically visiting places? What do you think a > reasonable number to check would be before importing? > > > > As a start, I was considering importing their "Public Barbeques in the > > > ACT" dataset, which does not appear to currently be included in the map. > > > > Do you have a plan in place of how you'd do the import? Ensuring > > correct tags are used and data is conflated with whats in OSM already? > > Not in detail yet, I'll be able to get a better idea once I can read > the import documentation. > _______________________________________________ Talk-au mailing list Talk-au@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-au
