Re: [OSM-talk] Tool for tag tracking

2018-01-13 Thread Roland Olbricht 

Hi Pierre,

This new query on the test server reports action=deleted when and object 
is simply modified to remove all tags.

See https://overpass-turbo.eu/s/uJ8


Thank you for pointing to this example. To get the information what has 
happened, please use [adiff:...] instead of [diff:...]. You then get 
back in the -section an element that has "visible=true" or 
"visible=false", according to whether the object got irrelevant or got 
deleted. As a drawback, Overpass Turbo then does not show the results.


I should add a paragraph for this in the documentation.

The reason for this behaviour is the underlying metaphor: Filtering for 
a specfic set of data (here: waterways in the given bounding box) means 
that all other data is disregarded, i.e. it makes no difference whether 
it exists or not.


While this is pretty irrelevant as long as you work with the plain 
filtered data, it does make an implication for a diff: there is no 
difference whether an object is newly created or just got relevant. You 
do not even intend the database engine to spend extra time on figuring 
that out. Symmetrically this means that for the extract it is irrelevant 
whether an item got deleted or just irrelevant.


Hence, the database spends no time on that in [diff:..] mode but it does 
in [adiff:..] mode.


> Should there be a an action subtype that reports either tag or geometry
> only actions ?

I would like to avoid having a large number of different actions, I 
prefer giving the information in different attribute or so. Most things 
can happen in combination, further increasing the number of actions if 
actions telled all the details. There had been an older attempt for a 
diff format with more actions, and it was a pain to work with it.


Best regards,

Roland

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Tool for tag tracking

2018-01-12 Thread Pierre Béland 
Thanks mmd and Roland, I was able to test it. 
Since these new queries extend the type of actions to report, 

Should there be a an action subtype that reports either tag or geometry only 
actions ?
det_action = [tag_create, tag_modify, tag_delete, geometry_create, 
geometry_modify, geometry_delete]
This new query on the test server reports action=deleted when and object is 
simply modified to remove all tags.See https://overpass-turbo.eu/s/uJ8
 
Pierre 
 

Le vendredi 12 janvier 2018 12:35:25 HNE, mmd  a écrit : 
 
 
 Am 12.01.2018 um 14:51 schrieb Pierre Béland:
> Hi Roland. Great additions again.
> 
> I cannot access https://dev.overpass-api.de/api_new_feat/ to test.
> 
> Hi have the message Forbidden, You don't have permission to access
> /api_new_feat/ on this server.
> 

Please disregard any line starting with "{{data:overpass,server". Those
are only needed for overpass turbo to know which Overpass server to use.
You should try one of the following query shortlinks as per Roland's
post instead:

https://overpass-turbo.eu/s/uF2
https://overpass-turbo.eu/s/uF4
https://overpass-turbo.eu/s/uF7
https://overpass-turbo.eu/s/uFa


-- 




___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
  ___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Tool for tag tracking

2018-01-12 Thread Marco 

Wow, that's nice, thanks!


Il 12/01/2018 06:31, Roland Olbricht ha scritto:

Hi,

for the sake of completeness, I would like to give a preview what is 
in the development for Overpass API:


Similar to this one

https://help.openstreetmap.org/questions/54268/search-for-objects-created-after-a-certain-date-with-overpass 



you could nowadays search with https://overpass-turbo.eu/s/uF0
for all highways that have changed since the beginning of the year in 
and around Antwerp:


[diff:"2018-01-01T00:00:00Z"];
way[highway]({{bbox}});
out geom;

I suggest the "out geom" mode over recursing to the nodes. Overpass 
Turbo can handle both, but the "out geom" means that there is exactly 
one item per object in question. No unchanged nodes get involved.


The above result is bloated by objects like
https://www.openstreetmap.org/way/469659128/history
It has no change to its highway value but just lost the unrelated tag 
"horse=no".


Here comes a feature in the staging area for the next version into 
play. We do not ask for all changes but just for changes that affect 
the tag "highway": https://overpass-turbo.eu/s/uF2


[diff:"2018-01-01T00:00:00Z"];
way[highway]({{bbox}});
compare(delta:t[highway]);
out geom;
{{data:overpass,server=https://dev.overpass-api.de/api_new_feat/}}

The line "compare(delta:t[highway]);" reads as: keep only objects that 
have changed in the value "t[highway]". The last line is a directive 
to execute the query on the development server.


We could even drill down further and retrieve only objects that have 
been created or deleted: https://overpass-turbo.eu/s/uF4


[diff:"2018-01-01T00:00:00Z"];
way[highway]({{bbox}});
compare(delta:0);
out geom;
{{data:overpass,server=https://dev.overpass-api.de/api_new_feat/}}

This is admittedly hacky and the final implementation might have a 
more straightforward term. The condition for "compare" always 
evaluates to the empty string for non-existing objects. And for 
existing objects to "0" as we just have specified, hence it can tell 
apart existing from non-existing objects.


Can we separate the deleted from the created objects? Yes,
https://overpass-turbo.eu/s/uF7 delivers only created objects:

[diff:"2018-01-01T00:00:00Z"];
way[highway]({{bbox}});
compare(delta:0)
(
  way._(newer:"2018-01-01T00:00:01Z");
  out geom;
);
{{data:overpass,server=https://dev.overpass-api.de/api_new_feat/}}

And https://overpass-turbo.eu/s/uFa delivers only deleted objects:

[diff:"2018-01-01T00:00:00Z"];
way[highway]({{bbox}});
compare(delta:0)
(
  ( ._; - way._(newer:"2018-01-01T00:00:01Z"); );
  out geom;
);
{{data:overpass,server=https://dev.overpass-api.de/api_new_feat/}}

Please note that these are not yet in a published release because 
there may come up a reason to change the syntax. If that happens, I 
will write a mail here again. For example, it might be more concise to 
do these tasks with a three argument "changed" condition. But I have 
not evaluated yet whether this leads to a logically sound syntax.


Best regards,
Roland


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk



___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Tool for tag tracking

2018-01-12 Thread mmd 
Am 12.01.2018 um 14:51 schrieb Pierre Béland:
> Hi Roland. Great additions again.
> 
> I cannot access https://dev.overpass-api.de/api_new_feat/ to test.
> 
> Hi have the message Forbidden, You don't have permission to access
> /api_new_feat/ on this server.
> 

Please disregard any line starting with "{{data:overpass,server". Those
are only needed for overpass turbo to know which Overpass server to use.
You should try one of the following query shortlinks as per Roland's
post instead:

https://overpass-turbo.eu/s/uF2
https://overpass-turbo.eu/s/uF4
https://overpass-turbo.eu/s/uF7
https://overpass-turbo.eu/s/uFa


-- 




___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Tool for tag tracking

2018-01-12 Thread Pierre Béland 
Hi Roland. Great additions again.
I cannot access https://dev.overpass-api.de/api_new_feat/ to test.

Hi have the message Forbidden, You don't have permission to access 
/api_new_feat/on this server.

 
Pierre 
 

Le vendredi 12 janvier 2018 00:33:33 HNE, Roland Olbricht 
 a écrit :  
 
 Hi,

for the sake of completeness, I would like to give a preview what is in 
the development for Overpass API:

Similar to this one

> https://help.openstreetmap.org/questions/54268/search-for-objects-created-after-a-certain-date-with-overpass

you could nowadays search with https://overpass-turbo.eu/s/uF0
for all highways that have changed since the beginning of the year in 
and around Antwerp:

[diff:"2018-01-01T00:00:00Z"];
way[highway]({{bbox}});
out geom;

I suggest the "out geom" mode over recursing to the nodes. Overpass 
Turbo can handle both, but the "out geom" means that there is exactly 
one item per object in question. No unchanged nodes get involved.

The above result is bloated by objects like
https://www.openstreetmap.org/way/469659128/history
It has no change to its highway value but just lost the unrelated tag 
"horse=no".

Here comes a feature in the staging area for the next version into play. 
We do not ask for all changes but just for changes that affect the tag 
"highway": https://overpass-turbo.eu/s/uF2

[diff:"2018-01-01T00:00:00Z"];
way[highway]({{bbox}});
compare(delta:t[highway]);
out geom;
{{data:overpass,server=https://dev.overpass-api.de/api_new_feat/}}

The line "compare(delta:t[highway]);" reads as: keep only objects that 
have changed in the value "t[highway]". The last line is a directive to 
execute the query on the development server.

We could even drill down further and retrieve only objects that have 
been created or deleted: https://overpass-turbo.eu/s/uF4

[diff:"2018-01-01T00:00:00Z"];
way[highway]({{bbox}});
compare(delta:0);
out geom;
{{data:overpass,server=https://dev.overpass-api.de/api_new_feat/}}

This is admittedly hacky and the final implementation might have a more 
straightforward term. The condition for "compare" always evaluates to 
the empty string for non-existing objects. And for existing objects to 
"0" as we just have specified, hence it can tell apart existing from 
non-existing objects.

Can we separate the deleted from the created objects? Yes,
https://overpass-turbo.eu/s/uF7 delivers only created objects:

[diff:"2018-01-01T00:00:00Z"];
way[highway]({{bbox}});
compare(delta:0)
(
  way._(newer:"2018-01-01T00:00:01Z");
  out geom;
);
{{data:overpass,server=https://dev.overpass-api.de/api_new_feat/}}

And https://overpass-turbo.eu/s/uFa delivers only deleted objects:

[diff:"2018-01-01T00:00:00Z"];
way[highway]({{bbox}});
compare(delta:0)
(
  ( ._; - way._(newer:"2018-01-01T00:00:01Z"); );
  out geom;
);
{{data:overpass,server=https://dev.overpass-api.de/api_new_feat/}}

Please note that these are not yet in a published release because there 
may come up a reason to change the syntax. If that happens, I will write 
a mail here again. For example, it might be more concise to do these 
tasks with a three argument "changed" condition. But I have not 
evaluated yet whether this leads to a logically sound syntax.

Best regards,
Roland


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
  ___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Tool for tag tracking

2018-01-12 Thread Tobias Zwick 
Wow, Roland, this is awesome!

So, this seems to make any deliberations of introducing a
survey_date:something tag or similar obsolete, because in the future,
one will be able to search with overpass through the history on a
per-tag basis.

This will make it possible for QA and hm... data-actuality-maintenance
tools (made up this term, this category of tools doesn't exist yet I
guess) to find data that haven't been changed for a long time and should
be re-checked some time.
I am thinking of finding automatically certain data points (tags) that
haven't changed in the database for X months and should be re-surveyed.
Will that be possible also (checking for "last change on tag older
than...")?

This feature makes it possible to greatly improve the maintainability of
data in openstreetmap.
For example the smoothness of streets and cycleways in particular is
something that should be revisited every few years, same as the street
surface especially in developing countries. Also, the presence of
cycleways on streets might be something that should be re-checked every
decade or so at least. Etc etc

Great work!

Cheers
Tobias

On 12/01/2018 06:31, Roland Olbricht wrote:
> Hi,
> 
> for the sake of completeness, I would like to give a preview what is in
> the development for Overpass API:
> 
> Similar to this one
> 
>> https://help.openstreetmap.org/questions/54268/search-for-objects-created-after-a-certain-date-with-overpass
>>
> 
> you could nowadays search with https://overpass-turbo.eu/s/uF0
> for all highways that have changed since the beginning of the year in
> and around Antwerp:
> 
> [diff:"2018-01-01T00:00:00Z"];
> way[highway]({{bbox}});
> out geom;
> 
> I suggest the "out geom" mode over recursing to the nodes. Overpass
> Turbo can handle both, but the "out geom" means that there is exactly
> one item per object in question. No unchanged nodes get involved.
> 
> The above result is bloated by objects like
> https://www.openstreetmap.org/way/469659128/history
> It has no change to its highway value but just lost the unrelated tag
> "horse=no".
> 
> Here comes a feature in the staging area for the next version into play.
> We do not ask for all changes but just for changes that affect the tag
> "highway": https://overpass-turbo.eu/s/uF2
> 
> [diff:"2018-01-01T00:00:00Z"];
> way[highway]({{bbox}});
> compare(delta:t[highway]);
> out geom;
> {{data:overpass,server=https://dev.overpass-api.de/api_new_feat/}}
> 
> The line "compare(delta:t[highway]);" reads as: keep only objects that
> have changed in the value "t[highway]". The last line is a directive to
> execute the query on the development server.
> 
> We could even drill down further and retrieve only objects that have
> been created or deleted: https://overpass-turbo.eu/s/uF4
> 
> [diff:"2018-01-01T00:00:00Z"];
> way[highway]({{bbox}});
> compare(delta:0);
> out geom;
> {{data:overpass,server=https://dev.overpass-api.de/api_new_feat/}}
> 
> This is admittedly hacky and the final implementation might have a more
> straightforward term. The condition for "compare" always evaluates to
> the empty string for non-existing objects. And for existing objects to
> "0" as we just have specified, hence it can tell apart existing from
> non-existing objects.
> 
> Can we separate the deleted from the created objects? Yes,
> https://overpass-turbo.eu/s/uF7 delivers only created objects:
> 
> [diff:"2018-01-01T00:00:00Z"];
> way[highway]({{bbox}});
> compare(delta:0)
> (
>   way._(newer:"2018-01-01T00:00:01Z");
>   out geom;
> );
> {{data:overpass,server=https://dev.overpass-api.de/api_new_feat/}}
> 
> And https://overpass-turbo.eu/s/uFa delivers only deleted objects:
> 
> [diff:"2018-01-01T00:00:00Z"];
> way[highway]({{bbox}});
> compare(delta:0)
> (
>   ( ._; - way._(newer:"2018-01-01T00:00:01Z"); );
>   out geom;
> );
> {{data:overpass,server=https://dev.overpass-api.de/api_new_feat/}}
> 
> Please note that these are not yet in a published release because there
> may come up a reason to change the syntax. If that happens, I will write
> a mail here again. For example, it might be more concise to do these
> tasks with a three argument "changed" condition. But I have not
> evaluated yet whether this leads to a logically sound syntax.
> 
> Best regards,
> Roland
> 
> 
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Tool for tag tracking

2018-01-11 Thread Roland Olbricht 

Hi,

for the sake of completeness, I would like to give a preview what is in 
the development for Overpass API:


Similar to this one


https://help.openstreetmap.org/questions/54268/search-for-objects-created-after-a-certain-date-with-overpass


you could nowadays search with https://overpass-turbo.eu/s/uF0
for all highways that have changed since the beginning of the year in 
and around Antwerp:


[diff:"2018-01-01T00:00:00Z"];
way[highway]({{bbox}});
out geom;

I suggest the "out geom" mode over recursing to the nodes. Overpass 
Turbo can handle both, but the "out geom" means that there is exactly 
one item per object in question. No unchanged nodes get involved.


The above result is bloated by objects like
https://www.openstreetmap.org/way/469659128/history
It has no change to its highway value but just lost the unrelated tag 
"horse=no".


Here comes a feature in the staging area for the next version into play. 
We do not ask for all changes but just for changes that affect the tag 
"highway": https://overpass-turbo.eu/s/uF2


[diff:"2018-01-01T00:00:00Z"];
way[highway]({{bbox}});
compare(delta:t[highway]);
out geom;
{{data:overpass,server=https://dev.overpass-api.de/api_new_feat/}}

The line "compare(delta:t[highway]);" reads as: keep only objects that 
have changed in the value "t[highway]". The last line is a directive to 
execute the query on the development server.


We could even drill down further and retrieve only objects that have 
been created or deleted: https://overpass-turbo.eu/s/uF4


[diff:"2018-01-01T00:00:00Z"];
way[highway]({{bbox}});
compare(delta:0);
out geom;
{{data:overpass,server=https://dev.overpass-api.de/api_new_feat/}}

This is admittedly hacky and the final implementation might have a more 
straightforward term. The condition for "compare" always evaluates to 
the empty string for non-existing objects. And for existing objects to 
"0" as we just have specified, hence it can tell apart existing from 
non-existing objects.


Can we separate the deleted from the created objects? Yes,
https://overpass-turbo.eu/s/uF7 delivers only created objects:

[diff:"2018-01-01T00:00:00Z"];
way[highway]({{bbox}});
compare(delta:0)
(
  way._(newer:"2018-01-01T00:00:01Z");
  out geom;
);
{{data:overpass,server=https://dev.overpass-api.de/api_new_feat/}}

And https://overpass-turbo.eu/s/uFa delivers only deleted objects:

[diff:"2018-01-01T00:00:00Z"];
way[highway]({{bbox}});
compare(delta:0)
(
  ( ._; - way._(newer:"2018-01-01T00:00:01Z"); );
  out geom;
);
{{data:overpass,server=https://dev.overpass-api.de/api_new_feat/}}

Please note that these are not yet in a published release because there 
may come up a reason to change the syntax. If that happens, I will write 
a mail here again. For example, it might be more concise to do these 
tasks with a three argument "changed" condition. But I have not 
evaluated yet whether this leads to a logically sound syntax.


Best regards,
Roland


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Tool for tag tracking

2018-01-11 Thread Oleksiy Muzalyev 

Marc,

Not exactly. I wrote this tool http://ausleuchtung.ch/travel_pack/ 
primarily for my needs. I have to travel a lot, and before going to a 
city or a town, I would like to see visually on the map where are 
parking lots, car wash, hotels, supermarkets, police stations, 
pharmacies, hospitals, bus stations, etc.


And, for example, in German language "car wash" is Autowäsche, in French 
language "library" is bibliothèque, but "librarie" means a bookstore. I 
mean tag names do no coincide in different languages. But if one 
switches to a certain language one can see the objects' titles in 
his/her language in the searchable drop down list. Searchable in that 
selected language.


I plan to add more tags to the dynamic drop-down list with icons. I also 
plan to switch to the local database and tiles, but for this I have to 
move to self-hosting first.


With best regards,
O.
OSM: Alex-7

On 11.01.18 14:41, Marc Gemis wrote:

Oleksiy,

Is your planned tool similar to : http://tagfinder.herokuapp.com/ ?

m.

On Thu, Jan 11, 2018 at 1:46 PM, Oleksiy Muzalyev
 wrote:

I work on a tool to view a certain tag on the map for a non-programmer, for
those who do not speak English (a language could be selected in the upper
write part of the page), and do not know the OSM tags by heart:
http://ausleuchtung.ch/travel_pack/

It is based on Overpass API.

Best regards,
O.
OSM: Alex-7

On 11.01.18 09:53, Javier Sánchez Portero wrote:

Hello

I can't find a Quality Assurace tool to track additions of objects with a
specific tag in an area.

I know I can do it with a local updated instance of the database, but I'm
looking for a accesible way for a non programer.

Does anyone know any?

Thank you in advance,
Javier



___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk



___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk




___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Tool for tag tracking

2018-01-11 Thread Marc Gemis 
Oleksiy,

Is your planned tool similar to : http://tagfinder.herokuapp.com/ ?

m.

On Thu, Jan 11, 2018 at 1:46 PM, Oleksiy Muzalyev
 wrote:
> I work on a tool to view a certain tag on the map for a non-programmer, for
> those who do not speak English (a language could be selected in the upper
> write part of the page), and do not know the OSM tags by heart:
> http://ausleuchtung.ch/travel_pack/
>
> It is based on Overpass API.
>
> Best regards,
> O.
> OSM: Alex-7
>
> On 11.01.18 09:53, Javier Sánchez Portero wrote:
>
> Hello
>
> I can't find a Quality Assurace tool to track additions of objects with a
> specific tag in an area.
>
> I know I can do it with a local updated instance of the database, but I'm
> looking for a accesible way for a non programer.
>
> Does anyone know any?
>
> Thank you in advance,
> Javier
>
>
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Tool for tag tracking

2018-01-11 Thread Oleksiy Muzalyev 
I work on a tool to view a certain tag on the map for a non-programmer, 
for those who do not speak English (a language could be selected in the 
upper write part of the page), and do not know the OSM tags by heart:

http://ausleuchtung.ch/travel_pack/

It is based on Overpass API.

Best regards,
O.
OSM: Alex-7

On 11.01.18 09:53, Javier Sánchez Portero wrote:

Hello

I can't find a Quality Assurace tool to track additions of objects 
with a specific tag in an area.


I know I can do it with a local updated instance of the database, but 
I'm looking for a accesible way for a non programer.


Does anyone know any?

Thank you in advance,
Javier



___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk



___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Tool for tag tracking

2018-01-11 Thread pbnoxious 

Hi,

you can surely do that with overpass, just add 
(newer:"-mm-ddThh:mm:ssZ") after the thing you're searching for. 
Alternatively you could also use "adiff" to search for a specific time 
frame.


Example query: http://overpass-turbo.eu/s/uz9

Greetings
pbnoxious


On 2018-01-11 10:34, Javier Sánchez Portero wrote:

Maybe there exists a feature in overpass to filter by creation date and I
have missed it?

El 11 ene. 2018 9:10, "Michał Brzozowski"  escribió:


I second the question. A marriage of Google Alerts and overpass turbo
would be great for tracking tags that e.g. shouldn't exist in given country
(or are suspicious). Or just plain QA in which overpass is quite powerful.

Michał

11.01.2018 9:57 AM "Javier Sánchez Portero" 
napisał(a):


Hello

I can't find a Quality Assurace tool to track additions of objects with a
specific tag in an area.

I know I can do it with a local updated instance of the database, but I'm
looking for a accesible way for a non programer.

Does anyone know any?

Thank you in advance,
Javier


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk






___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk



___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Tool for tag tracking

2018-01-11 Thread Marco 
Hi, last year I was searching pretty much the same thing and ended up 
with this one:


https://help.openstreetmap.org/questions/54268/search-for-objects-created-after-a-certain-date-with-overpass

You could easily use that same code after tweaking it a little; I'm far 
from being a programmer but I can easily use it.


See this:

/|[out:xml][timeout:250][adiff:"2015-01-01T00:00:00Z","2016-01-01T00:00:00Z"]; 
( node["highway"="crossing"]({{bbox}}); ); out body; out meta; >; out 
skel qt;|/


This code returns all the created/edited nodes tagged as 
highway=crossing in between 1-1-2015 and 1-1-2016, if you want to search 
for the amenity=drinking_water created in between two dates you just 
have to replace "highway" with "amenity" and "crossing" with 
"drinking_water", in case you need to search those added/edited in 
another time span, you just need to update the data in the first row.
Keep in mind that "node" on the third row, if you're searching fo the 
highway=path tag, you'll have to replace the "node" with "way", because 
no one uses the highway=path tag on a node (hopefully :D)
When you're done editing your code you just paste it here 
http://overpass-turbo.eu/ , move the map on the area where you want to 
search in, and click the start button.


Hopefully it works for you as well.
Cheers
Marco

Il 11/01/2018 09:53, Javier Sánchez Portero ha scritto:

Hello

I can't find a Quality Assurace tool to track additions of objects 
with a specific tag in an area.


I know I can do it with a local updated instance of the database, but 
I'm looking for a accesible way for a non programer.


Does anyone know any?

Thank you in advance,
Javier



___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Tool for tag tracking

2018-01-11 Thread Javier Sánchez Portero 
Maybe there exists a feature in overpass to filter by creation date and I
have missed it?

El 11 ene. 2018 9:10, "Michał Brzozowski"  escribió:

> I second the question. A marriage of Google Alerts and overpass turbo
> would be great for tracking tags that e.g. shouldn't exist in given country
> (or are suspicious). Or just plain QA in which overpass is quite powerful.
>
> Michał
>
> 11.01.2018 9:57 AM "Javier Sánchez Portero" 
> napisał(a):
>
>> Hello
>>
>> I can't find a Quality Assurace tool to track additions of objects with a
>> specific tag in an area.
>>
>> I know I can do it with a local updated instance of the database, but I'm
>> looking for a accesible way for a non programer.
>>
>> Does anyone know any?
>>
>> Thank you in advance,
>> Javier
>>
>>
>> ___
>> talk mailing list
>> talk@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk
>>
>>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Tool for tag tracking

2018-01-11 Thread Michał Brzozowski 
I second the question. A marriage of Google Alerts and overpass turbo would
be great for tracking tags that e.g. shouldn't exist in given country (or
are suspicious). Or just plain QA in which overpass is quite powerful.

Michał

11.01.2018 9:57 AM "Javier Sánchez Portero" 
napisał(a):

> Hello
>
> I can't find a Quality Assurace tool to track additions of objects with a
> specific tag in an area.
>
> I know I can do it with a local updated instance of the database, but I'm
> looking for a accesible way for a non programer.
>
> Does anyone know any?
>
> Thank you in advance,
> Javier
>
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

[OSM-talk] Tool for tag tracking

2018-01-11 Thread Javier Sánchez Portero 
Hello

I can't find a Quality Assurace tool to track additions of objects with a
specific tag in an area.

I know I can do it with a local updated instance of the database, but I'm
looking for a accesible way for a non programer.

Does anyone know any?

Thank you in advance,
Javier
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk