Feature/new filters

docs/osmstats.md

@@ -57,7 +57,7 @@ buildings_modified | This value is updated by counting the existing buildings mo
 pois_added | This value is updated by counting the POIs added by the user in the change file
 pois_modified | This value is updated by counting the existing POIs modified by the user in the change file
 editor | The editor used, and comes from the changeset
-user_id | The user ID, comes from the changeset
+uid | The user ID, comes from the changeset
 created_at | The timestamp this changeset was created, comes from the changeset
 closed_at | The timestamp this changeset was closed, comes from the changeset
 verified | Whether this data has been validated
@@ -128,7 +128,7 @@ level | The badge level
 
 Keyword | Description
 --------|------------
-user_id | The OSM user ID
+uid | The OSM user ID
 badge_id | The badge ID
 updated_at | The timestamp of the user receiving this badge
 

docs/statistics.md

@@ -211,7 +211,7 @@ backend and the frontend, without having modify the database schema.
 An example query to count the total number of buildings added by the
 user **4321** for a Tasking Manager project **1234** would be this:
 > SELECT SUM(CAST(added::hstore->'building' AS DOUBLE precision)) FROM
-changesets WHERE 'hotosm-project-1234' = ANY(hashtags) AND user_id=4321;
+changesets WHERE 'hotosm-project-1234' = ANY(hashtags) AND uid=4321;
 
 The source is the satellite imagery used for remote mapping.
 
@@ -221,7 +221,7 @@ Keyword | Description
 --------|------------
 id | The ID of this changeset
 editor | The editor used for this changeset
-user_id | The OSM User ID of the mapper
+uid | The OSM User ID of the mapper
 created_at | The timestamp when this changes was uploaded
 closed_at | The timestamp when this uploaded change completed processing
 updated_at | The timestamp when this last had data updated