With the announcement yesterday that SteveC has joined Bing Maps and that their imagery will become available for tracing, I started wondering about adding field boundaries near here when the imagery becomes available. These are my thoughts on mapping individual fields:
- From the imagery, tag as many of the field boundary ways as possible with barrier=hedge/barrier=ditch/barrier=fence (or whatever, as appropriate).
- Complete the field "boundary" with untagged ways, to form a closed area, with barrier=gate nodes if appropriate (possibly can't be determined from imagery).
- Use a multipolygon relation tagged as landuse=farmland with the boundary ways as the members, role outer.
- If the field has a name that you know (or have compatible source for) that tag can also go on the relation as name=*
Thoughts or comments? I'll test the above on a few fields once the imagery becomes available and see how it goes. --EdLoach 09:21, 24 November 2010 (UTC)
- Further suggestions received - one large landuse=farmland area with barrier=* ways on top. May be simpler. --EdLoach 09:40, 24 November 2010 (UTC)
Redirected to landuse=farm
This page is redirected to landuse=farm. Maybe that's not the best thing, but in September somebody got rid of the redirect and copied the exact contents of Tag:landuse=farm here instead. That's pretty silly given that this content includes an explanation of why landuse=farmland is not the best tag to use.
For now I've put back the redirect, but maybe it should have explanatory content similar to the Farm page on here
-- Harry Wood 13:45, 22 February 2011 (UTC)
- I'm amazed at how old this is. Either way, I'm copying the content Tag:landuse=farm over here, as it is already so edited as to only point to the usage of Tag:landuse=farmland. I'll try to edit the contents to deprecate Tag:landuse=farm. Messy Unicorn (talk) 08:54, 28 September 2014 (UTC)