When processing data in OSM change files, is there a smart way to access node data? All other data are available (e.g. tags) but the files reference existing nodes.
Therefore to maintain a subset of OSM it’s therefore necessary to maintain a full node database, or perform API lookups to get the existing information. Unless I’m missing something? Does anyone have any bright ideas to get all the node data referenced in an OSM change file?
Any suggestions appreciated!