tyrasd / taghistory Goto Github PK

It seems that tags with less than about 1000 uses contain history only to about mid-2018, not after that.
After 2018, only dashed line to current value is shown.

Is that intentional? If so, it should be documented.

e.g. https://taghistory.raifer.tech/#***/shop/fishmonger&***/amenity/gambling&***/amenity/crematorium&***/amenity/exhibition_centre&***/amenity/emergency_service&***/amenity/vehicle_ramp&***/shop/hobby&***/shop/vacuum_cleaner produces:

I found related only this diary comment, but it seems to talk about taginfo history being limited to more popular values, not taghistory.

• There are related strangeness in taghistory database in that mid-2018 timeframe too, e.g. #33

Is the source code of the API also published?

is this #20 ?

Let's integrate the backend&api into taginfo.

• adapt backend preprocessing to fit into taginfo project structure
• produce sqlite files directly (instead of via intermediate csv files)
• (?) slimmer sqlite db by having a simpler db schema: (type, key, [value,] timestamps/days, deltas) with only 1 entry per tag
• re-implemt taghistory api in as taginfo api endpoints
• make sure taginfo pages are accessible (e.g. found in search results) also for tags which currently have 0 occurences in the db (e.g. foo=no)
• add history tab with simple graph in taginfo
• (?) implement history graph in tag comparison page in taginfo
• switch this repo to use taginfo's api
• document downloading/processing of .osh.pbf files in taginfo (for regional instances -> refer to geofabrik extracts)

Add links to taginfo for individual tag/key pages and/or comparison page of multiple tags.

There are those regional taginfo instances at https://taginfo.geofabrik.de/europe/ which allow to analyse tags per country.

It would be great if we could change the taginfo instance that is used to generate the chart, so we can analyse data per country.

Ideally those instance is preserved in a URL so we can share the view and easily compare tabs …

Looking at some graph like building:use it produces very strange results, where graph goes backwards in time (timewarping from 2019 back to middle of 2018), and then becomes dotted line for years?

See here: https://taghistory.raifer.tech/#***//building:use

Is it some database corruption or?

Would be great to activate a logarithmic scaling

Currently, 'node' is the default object type in the GUI at http://taghistory.raifer.tech/. I think it would be slightly more intuitive to make 'any' the default (perhaps it could be added to the top of the list too).

This tool is really great, by the way!

This is a wishlist item - perhaps you can see value in it: (I cannot assess, if it is in scope of taghistory at all…)

When considering taghistory a popularity contest, that shows the count of votes (i.e. objects carrying a specific tag), where every voter has unlimited votes, it would be nice to also have a count of voters (the people that applied a tag to an object).

For little or medium used tags, one could immediately see, if it was applied (voted on, in contest speak) by a single, a few or by many. For tags with many occurences, the distribution will be quite flat, but it might still be reasonable to have the number, when comparing tags that are close in meaning, e.g.

Hope it is clear :)

To compare different tags relative scaling would be cool

It'd be nice to have stats for keys without specifying value.

http://taghistory.raifer.tech/
"page not found"

It is really hard to zoom in a predictable manner at the moment. This is especially true with a touch device. Adding some kind of touchable indicator would help a lot.

would love to see the tag history within a specific area

Just to fix spelling errors (boundary=adminstative -> boundary=administrative) or remove unneeded data rows

From https://github.com/tyrasd/taghistory#todos: for linear and polygonal objects: use length or area as a metric instead of object count

Allow to set parameters via the URL. So links could be shared. Alternatively create a hash for a given configuration which could be shared.

Very minor issue

Hide the (reset zoom) in upper left corner of the saved images. See the attached image for an example

Can you add any option to your project to let people add a specific region for their tags?
For example I would like to see nodes with tag "shop=tobacco" only in Italy.

Do you think is it possibile to implement?

I hope you can help me. Keep up the good work.

Hi, it looks like the test installation is not updated since mid December?

In order to compare i.e. emergency=defibrillator (main tag) and i.e. ref:FR:GeoDAE (sub tag), it would be nice to select i.e. left or right Y axis (each one having it's own scale).

http://taghistory.raifer.tech/#***/ref:FR:GeoDAE/&***/emergency/defibrillator

Allow the export of the raw data, e.g. as csv would be awesome. Even better: API for it

I copied tags to the input field which had whitespaces. So I did not see anything … and started debugging if the service is down.

https://taghistory.raifer.tech/#***/orchard/meadow_orchard%20&***/meadow/meadow_orchard%20

I suggest to strip whitespaces before submitting the data to the URL/API/Application.

It would be great if the automatic zoom after adding a tag would include the dashed line too. Currently it ends often way outside the graph. See e.g. https://taghistory.raifer.tech/#***/marker/ or https://taghistory.raifer.tech/#***/playground/

• a way to remove unwanted tags/traces #14
• make checkable items more obvious (reset zoom)
• permalinks via url-hash
• better UI for any-value selection

Make key/value fields autocomplete via taginfo suggestions api.
(idea by Oleksiy Muzalyev via osm-talk)

Sometimes I would like to see comparison, but in taghistory tool: http://taginfo.openstreetmap.org/compare/amenity=shelter/shelter=yes

taghistory should have something ?compare=amenity=shelter/shelter=yes

Thanks for implementing #27 (enable permalinks)

It works very well so far.
Only for this link/page https://taghistory.raifer.tech/#***/amenity/vacuum_cleaner the url switches to https://taghistory.raifer.tech/#***/amenity/ after a short while and then of course doesn't shows the graph for tag amenity=vacuum_cleaner but for key amenity.

Is this reproducible on your machine, if so what is the reason for this behavior?

see gravitystorm/openstreetmap-carto#1630 (comment)

from https://github.com/tyrasd/taghistory#todos: implement regular (e.g. daily/weekly) data updates. Possible solutions:

• reprocess the weekly full history dumps (maybe only all keys as a limited subset of tags to limit memory requirements?)
• use Overpass augmented diffs to calculate daily diffs (currently not feasible because of performance issues, see drolbr/Overpass-API#322, possibly fixed by drolbr/Overpass-API#342)
• use Overpass augmented diffs by aggregating standard minutely diffs (currently not feasible because of drolbr/Overpass-API#346)
• download daily planet dumps and calculate tag usage deltas
• maybe someone out there already runs a global, daily (or quicker) updated osm database which could generate daily tag count diffs as a side product of their update process. see also https://www.openstreetmap.org/user/tyr_asd/diary/39402#comment39983
• compare daily results from taginfo

In default zoom the x-axis labels are showing years like "2015 2016". Counter-intuitively the label "2016" signifies the value 2016-01-01 - I would expect 2016-07-01 as the middle of the year. I already spent half an hour looking for the wrong dates on features ;) The "axis tick marks" should be changed to an interval representation like the first picture here: http://www.jqwidgets.com/jquery-widgets-documentation/documentation/jqxchart/jquery-chart-axes.htm

the backend code here is still buggy, incomplete and missing documentation. todos:

• add dev readme w/ install instructions
  • add instructions for how to import csv data into sqlite db (.mode csv, .import …)
• fix missing escaping of " characters in tag strigns of csv output
• add server script that implement the taghistory api

related(?):

• cut output from last processed day (which is typically incomplete)