Re: [talk-au] Fwd: vine row tagging

On Fri, 16 Oct 2020 at 13:52, John Bryant wrote: > > I'm not totally full bottle on all the mailman list management variables, > but I think it's managed with the reply_goes_to_list setting here: > > https://www.gnu.org/software/mailman/mailman-admin/node11.html > Thanks, John, but not

Re: [talk-au] Fwd: vine row tagging

On Fri, 16 Oct 2020 at 05:37, Graeme Fitzpatrick wrote: > Resending message to the list :-( > > How do we fix it so that "Reply" goes to the list, not just the last > poster? > I'm not totally full bottle on all the mailman list management variables, but I think it's managed with the

Re: [talk-au] Fwd: vine row tagging

Thanks Ben, That's a good point re: accuracy. But absolute position within a few meters may be OK, if the relative position is maintained. Vine rows are generally visible on imagery and could be mapped that way. It's also not unusual for a vineyard to survey their rows with high accuracy GPS.

Re: [talk-au] Fwd: vine row tagging

On Fri, 16 Oct 2020 at 13:54, Benjamin Ceravolo wrote: > I understand the principal being explained above as to why Vire rows are > wanting to be mapped, but my question is is it even practical within the > use of the map considering that viren reos are approximately 1.5m apart and > all but the

Re: [talk-au] Fwd: vine row tagging

Thanks Ian, that's a very good point re: consistency with orchards & plantations. Whether this style of mapping will actually prove to be broadly useful, time will tell I suppose, but seems better to start off aiming for consistency. On Fri, 16 Oct 2020 at 06:41, Little Maps wrote: > That’s an

Re: [talk-au] vine row tagging

Thanks Phil, there's a brief note about denotation=* in combination with natural=tree (and by extension, natural=tree_row?) on the wiki [1]. Combining with crop=grape seems to be a new approach... [1]

Re: [talk-au] Fwd: vine row tagging

I understand the principal being explained above as to why Vire rows are wanting to be mapped, but my question is is it even practical within the use of the map considering that viren reos are approximately 1.5m apart and all but the most high end GNSS (GPS) units are +1m accuracy. My point being

Re: [talk-au] Fwd: vine row tagging

That’s an interesting development in OSM micro-mapping John. Can I put a vote in for using natural=tree_row rather than barrier=fence, if no better options are available. I’m not arguing from the point of rendering, but from the perspective of developing a tagging scheme that will be useful in

[talk-au] Fwd: vine row tagging

Resending message to the list :-( How do we fix it so that "Reply" goes to the list, not just the last poster? Thanks Graeme -- Forwarded message - From: Graeme Fitzpatrick Date: Thu, 15 Oct 2020 at 17:20 Subject: Re: [talk-au] vine row tagging To: John Bryant On Thu,

Re: [talk-au] vine row tagging

Hi Folks, Where does the denotation=agricultural come from as it doesn’t appear to be a regular combination with crop=grape ?? https://taginfo.openstreetmap.org/tags/crop=grape#combinations Cheers Phil From: Andrew Harvey Sent: Thursday, 15 October 2020 7:52 PM To: John

Re: [talk-au] vine row tagging

I think it's fine to map these in OSM, like all other things in private property it does make it harder to validate and determining the exact crop from imagery might be a stretch, but I don't think this is enough of a reason to not map. I agree with the suggestion of natural=tree_row +

Re: [talk-au] vine row tagging

Thanks Simon, putting the data into OSM isn't meant to replace GIS, all the things you mention are certainly part of the professional viticulture community's practice. I believe this idea is more around enabling a different kind of access to information, and exploring the possibilities of using an

Re: [talk-au] vine row tagging

On Thursday, 15 October 2020 6:23:36 PM AEDT John Bryant wrote: > This is part of a viticulture community-driven project to build consensus > around use & sharing of data, and part of the discussion is around data > ownership and openness. The project has the Australian Farm Data Code [1] > as one

Re: [talk-au] vine row tagging

Thanks Brendan, this is an interesting idea! There's definitely some interest in capturing data at the vine level, but it presents some complications for some in the viticulture community, so vine rows are seen as a suitable level of abstraction for this stage. barrier=fence... also

Re: [talk-au] vine row tagging

Thanks Adam, On Thu, 15 Oct 2020 at 14:44, Adam Steer wrote: > What are the owners of the properties containing vines saying? Are they > fully aware that their farm data will be open for everyone to see? > This is part of a viticulture community-driven project to build consensus around use &

Re: [talk-au] vine row tagging

Depends of level of detail sought, but each grapevine could be marked as natural=shrub . My first thought was to use barrier=fence , but the wiki defines it as a "freestanding

Re: [talk-au] vine row tagging

Hey John What are the owners of the properties containing vines saying? Are they fully aware that their farm data will be open for everyone to see? ...and what data/tagging useful to them? Cheers, Adam On Thu, 15 Oct 2020 at 08:40, John Bryant wrote: > So, map the strainer posts on the ends

Re: [talk-au] vine row tagging

So, map the strainer posts on the ends of the rows, rather than the rows themselves, and then the end user could use them to interpolate the row? That's an interesting idea. On Thu, 15 Oct 2020 at 14:33, nwastra wrote: > Many vineyards have numbered rows with a tag on the end strainer posts to

Re: [talk-au] vine row tagging

Thanks Graeme, I appreciate your response, answers to your questions below. On Thu, 15 Oct 2020 at 13:32, Graeme Fitzpatrick wrote: > Do you need to? > Well, they want to map rows, to use OSM in a way that will be useful to the viticulture community. The idea is to add more detail to vineyards

[talk-au] vine row tagging

Many vineyards have numbered rows with a tag on the end strainer posts to assist direction of workers, etc. These could be numbered using the addr interpolation scheme and then individual rows would not need to be mapped but does need a close survey. > On 15 Oct 2020, at 3:32 pm, Graeme