Consume OSM entity attributes.

[hallahan]

The attributes you find with an OSM entity are invaluable for analysis. For example, keeping track of the OSM user is useful if you are trying to track down a malicious user. Or, you might want to look at the timestamp to filter OSM entities edited in a specific time period.

<way id="479834982" visible="true" version="3" changeset="68316730" timestamp="2019-03-20T01:52:13Z" user="stevea" uid="123633">

It might be nice to add all of these to the ID archive and instead call it attributes instead?

[VeaaC]

This data is definitely useful, but only for a small subset of users. I am not sure it is the same subset that is using Ids, so it could make sense to put it into another optional resource/sub-archive.

Do you have a proposal for the schema?

[hallahan]

I would structure attributes the same as tags. Then at runtime, an arg could specify which attributes we want.

Also, you could pull in IDs to be a part of that. It would live nexts to tags in the main archive.