Thanks all for the helpful responses. I'll explore using the Overpass
API and its "permanent ID" feature [1] for now. I do tend to agree
with Joost that it makes sense for OSM to have a policy for external
identifiers -- even if the threshold is not one that this project can
meet yet. :)
It'll be
sent from a phone
> Il giorno 09 ago 2016, alle ore 10:09, Rory McCann ha
> scritto:
>
> The suggestion of looking for "a fast food restaurant named McDonalds
> near the place" will solve that problem.
yes, besides the fact McDonald's reviews are a bit pointless
Re: Erik
> Last but not least, do you have a sense how common this category of
change is for typical POIs?
I have no idea, but I would say fairly common. I analysed the evolution of
nature reserves in Belgium as a test case, and they do really evolve.
Starting their life as a node, then a way,
On 08/08/16 22:52, Erik Moeller wrote:
> From a data consumer's point of view, when
> I look up the original node ID, do I just get a "not found", or is
> there an easy way to tell that there's a new way or relation now
> representing the same object?
Alas, no. There is no "parent objects" like
Hi Clifford,
Let me clarify that we're discussing OSM tagging with Wikidata IDs, not
Wikipedia articles. They are two related but different concepts.
Pine
On Aug 8, 2016 22:05, "Clifford Snow" wrote:
>
> On Mon, Aug 8, 2016 at 9:42 PM, Pine W
On Mon, Aug 8, 2016 at 9:42 PM, Pine W wrote:
> Speaking as an OSM novice but an experienced Wikimedian, having Wikidata
> ID tags makes sense to me. This sounds like something that could benefit
> Wikidata, Wikipedia, and other projects that recognize Wikidata IDs. There
>
Speaking as an OSM novice but an experienced Wikimedian, having Wikidata ID
tags makes sense to me. This sounds like something that could benefit
Wikidata, Wikipedia, and other projects that recognize Wikidata IDs. There
might be no need to have multiple external ID tags in OSM if the Wikidata
tag
On Mon, Aug 8, 2016 at 10:52 PM, Erik Moeller wrote:
>> - add an external ID to OSM. This would be analogue to the current wikidata
>> tag.
It's better not to add external IDs to OSM. It would be OK if there is
only 1 project in the world that would do this, but if every pet
sent from a phone
Il giorno 09 ago 2016, alle ore 00:46, Nicolás Alvarez
ha scritto:
>> From a data consumer's point of view, when
>> I look up the original node ID, do I just get a "not found", or is
>> there an easy way to tell that there's a new way or relation
2016-08-08 17:52 GMT-03:00 Erik Moeller :
> On Mon, Aug 8, 2016 at 2:56 AM, joost schouppe
> wrote:
>> Keeping OSM and an external database linked is no mean feat. Say you load a
>> McDonalds POI to your database and someone reviews it. But then a
On Mon, Aug 8, 2016 at 2:56 AM, joost schouppe wrote:
> Keeping OSM and an external database linked is no mean feat. Say you load a
> McDonalds POI to your database and someone reviews it. But then a mapper
> comes along and changes the node to a line. Upon the next
Keeping OSM and an external database linked is no mean feat. Say you load a
McDonalds POI to your database and someone reviews it. But then a mapper
comes along and changes the node to a line. Upon the next update of your
POI database, your review will not find the object it linked to before,
On Fri, Aug 5, 2016 at 7:48 PM, Pine W wrote:
Hi Pine,
Nice to run into you here!
> Hod do you plan to develop readership for this site? Yelp seems to have a
> commanding lead.
To begin with, I think the most important question is whether this is
something of importance
Hi Erik,
Interesting project, though I must admit some caution about its success.
How do you plan to develop readership for this site? Yelp seems to have a
commanding lead.
Pine
On Aug 5, 2016 18:17, "Erik Moeller" wrote:
> Hi Michał,
>
> Thanks for your comments!
>
> On
Hi Michał,
Thanks for your comments!
On Fri, Aug 5, 2016 at 4:55 PM, Michał Brzozowski wrote:
> Have you devised any robust algorithm for linking OSM primitives to
> objects in the external database? In general case, it seems really
> hard to track objects as they get
Have you devised any robust algorithm for linking OSM primitives to
objects in the external database? In general case, it seems really
hard to track objects as they get converted from nodes to areas, or
decide whether given OSM feature is no longer representing some entity
in the external
Hi all,
I'm working on this project:
https://lib.reviews/
The front page explains the goal: to build a free, open and non-profit
community focused on reviews. Review content is under CC-BY-SA while
the codebase is under CC-0.
Basic functionality to write reviews is there (we identify things to
17 matches
Mail list logo