[OSM-talk-be] mapping farm-shop

[Glenn Plas]

On 21-04-16 15:58, joost schouppe wrote:
> No amen from me :) - as I just daid: the arguments used can be used for
> anything we do.

Not at all..  we are in the business of mapping, not groceries lists.
You need to stay loyal to the core idea and stop putting information in
OSM that is probably already out-of-date the day after you enter it.

URL's have a much longer lifespan.  Or should have atleast...  And it's
only 1 edit away from being fixed.  If you enter a list of 200 products
and need to verify that , you have lots of work.  And no one uses OSM to
get grocery lists.  But we do use OSM to get to the grocery shop.

It definitely cannot be used for anything we do as we aggregate on-topic
data, we're not making milkshakes here.  We structure data into usuable
information.

> 
> URLs aren't very stable either. Marc had to change the reference to all
> historic objects because the Flemish government changed their website
> architecture. No reason not to do this.

We can't be held accountable for the instability of a certain site.  it
goes for ALL url's that are present in OSM, including source.

  That being said, a change like that could be automated if there is a
pattern in the changes.   We can't automate grocery list updates as it
differs per shop.  So URL's a much more stable than general lists.

> 
> I stumble upon out of date objects not touched in three years all the
> time. But that's no argument not to map roads.

I never claimed that argument.  Did you misread or have I miswritten
something ?   This statement confuses me a bit.

> 
> What is hard or not to keep up to date depends on building a community
> around it, not so much on the data itself. If you build a pretty
> interface around a bit of data, it will probably get updated. If it's
> not visible, it probably won't.

Being an einzelganger working solo is by definition not a team.  If
someone likes to go all 'Don Quichot' in OSM he's on his own... we can't
stop this of course.

> 
> Of course, I wouldn't encourage someone to map the color of the lettuce,
> but as Pieter says, the idea is to map broad categories.

So we want to map details... but not too much.. somewhere halfway is
good enough ?  Now I'm totally lost.  We don't want too much accuracy
because we deep down realise updating this is gonna be hard work, yet
URL's are not thrustworthy.

If you checked the urls I gave, you'd realise that the producers
actually update their inventory themselves.  Can this get any better
than that ?

Duplicating certain data is so counterproductive at times ...*sigh*

Glenn


> 
> 
> 
> 
> _______________________________________________
> Talk-be mailing list
> Talk-be at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be
>