Re: [talk-au] Rock Overhangs

I support natural=rock_overhang, or something similar. David On 14 April 2019 10:14:44 pm AEST, Andrew Harvey wrote: >Ok, thanks for the feedback. Let's gather some global thoughts on this, >I've posted >https://lists.openstreetmap.org/pipermail/tagging/2019-April/044554.html > >On Sun, 14

Re: [talk-au] Rock Overhangs

On Mon, 15 Apr 2019 at 07:55, David Wales wrote: > I support natural=rock_overhang, or something similar. > Yes, that seems the best answer. Thanks Graeme ___ Talk-au mailing list Talk-au@openstreetmap.org

Re: [talk-au] Importing Hobsons Bay City Council tree data into OSM

Note that https://wiki.openstreetmap.org/wiki/Import/Guidelines requires some documentation of import itself on the wiki. Apr 14, 2019, 7:34 AM by david.sisour...@hotmail.com: > > including the tree circumference > >  Are there plan to

Re: [talk-au] Rock Overhangs

Ok, thanks for the feedback. Let's gather some global thoughts on this, I've posted https://lists.openstreetmap.org/pipermail/tagging/2019-April/044554.html On Sun, 14 Apr 2019 at 16:23, Roger Browne wrote: > I've never been happy about "natural=cave_entrance", yet I have used it > several

Re: [talk-au] Talk-au Digest, Vol 142, Issue 14

Hi Mateusz, Thanks for the feedback. I have read the Import Guidelines and I will be documenting the import on the wiki by tomorrow noon and you will see this on the import catalogue page at that time. I do not think that the outdated tree circumference data would be an issue. Going by what

Re: [talk-au] Importing Hobsons Bay City Council tree data into OSM

Great working on sourcing those waivers! Do you either have a sample .osm file or could you post an example of what tags/values will be imported? Can you say anything further about how you will transform the data? ie. removing "Unknown" values etc. Regarding the source tag, I think it must be on

Re: [talk-au] Importing Hobsons Bay City Council tree data into OSM

Thanks Andrew, I have looked at all of the tags in the raw data and have created a Python file to process this. I have considered the ‘Unknown’, ‘Not Applicable’ and also removed the trees where they are ‘stumps’ or ‘vacant’. The data is linked here:

Re: [talk-au] Rock Overhangs

I've never been happy about "natural=cave_entrance", yet I have used it several times because it seems to be the least bad of the tags currently in use. The use of "amenity' is just wrong, because an amenity is something that is provided for a purpose (such as a cafe, bicycle parking, a charging