[Talk-GB] Mapping Field Boundaries

Gregory nomoregrapes at googlemail.com
Mon Aug 20 13:30:50 BST 2012

The height=* tag may also be relevant.

I would go with condition=* for the reasons of reuse-ability and ease of
Although it is tricky to avoid being subjective. Document values on the

On 19 August 2012 19:33, Graham Jones <grahamjones139 at gmail.com> wrote:

> Hi,
> I much prefer re-usable keys, so would favour 'condition=' over
> 'dry_stone:condition='.   The second one would be very specific to dry
> stone walls, but the general 'condition' one could be used for any feature.
> This is in part biased by the way I produce maps - I use mapnik rather
> than maperitive, so maintain a postgresql database of osm data.  Adding an
> extra key means adding an extra field to the database, which is a pain!
> Graham
> On 19 August 2012 18:59, Dudley Ibbett <dudleyibbett at hotmail.com> wrote:
>>  Hi
>> Over the last few months I've been mapping field boundaries in
>> Derbyshire/Peak District.  The condition of "dry_stone" walls varies
>> greatly.  One thing I would also like to do is tag the condition as this
>> information could well be useful in preserving the landscape character.
>> There are grants available for repairs etc.  I am also tagging stiles but
>> again the condition varies significantly.  Our local Parish Council
>> actually has money to repair stiles but doesn't spend it.  I have been
>> asked to carry out a survey of the footpaths and it would be good to tag
>> the type of stile at its condition.
>> Searching on the web I can find reports on surveys that define systems
>> for classifying the conditions of stone walls.  I've emailed the British
>> Stone Wall Society to see which they would recommend.  A DEFRA approved
>> system would seem to make sense should anyone want to use the information
>> to get funding for repairs.
>> I have yet to find any system for classifying the condition of stiles.
>> I've only found comments with regard to the land owners requirement to
>> ensure they are safe.  Has anyone come across a system?  I have also asked
>> the BSWS about this.
>> The other issue I will have is how to tag the condition.  I've found
>> "building:condition="  as a tag so I guess you could use
>> "dry_stone:condition=".  I might actually be easier just to use an
>> additional tag "condition=".
>> I've no experience of using maperative to make maps but was wondering if
>> anyone knows how easy it would be to change its set up with regard to the
>> about tags.  i.e. would "dry_stone:condition="  be more difficult to work
>> with if you wanted to produce a map of walls with the condition identified
>> against them than a separate "condition=" tag.
>> "condition" is also something that will change with time.  Given the
>> possibility of developing mobile phone apps to do updates of this, would
>> again having a separate "condition=" tag be easier?
>> I should add that I currently mark a barrier as a "wall=dry_stone" even
>> though it may be a long pile of stones and a fence now runs parallel to
>> it.  I take the view (it is one I checked with a landscape architect) that
>> the landowner would probably not have the fence there if the old wall
>> wasn't there.  There is also the hope that it might one day be rebuilt.
>> Any comments about the use of "dry_stone:condition=" or "condition="
>> would be helpful.  (Having written this I'm leaning towards "condition=" as
>> a separate tag)  Any views on a system for classifying the condition of
>> stiles and stone walls would also be useful.
>> Best Regards
>> Dudley
>> _______________________________________________
>> Talk-GB mailing list
>> Talk-GB at openstreetmap.org
>> http://lists.openstreetmap.org/listinfo/talk-gb
> --
> Graham Jones
> Hartlepool, UK.
> _______________________________________________
> Talk-GB mailing list
> Talk-GB at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk-gb

osm at livingwithdragons.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-gb/attachments/20120820/56a8a2cd/attachment.html>

More information about the Talk-GB mailing list