Closed ericsun95 closed 4 years ago
Hmm, interesting question. When I designed initially the parquetizer, I had in mind converting only the latest version of entities (considering that everything in the PBF is visible and there are no multiple versions of the same entity). If we can get the information somehow in osmosis while reading the files, I see no problem to extend the existing schemas with an extra field.
Hmm, interesting question. When I designed initially the parquetizer, I had in mind converting only the latest version of entities (considering that everything in the PBF is visible and there are no multiple versions of the same entity). If we can get the information somehow in osmosis while reading the files, I see no problem to extend the existing schemas with an extra field.
I do find this https://github.com/openstreetmap/osmosis/blob/2219470cef1f73f5d1319c57149c84b398e767ce/osmosis-apidb/src/main/java/org/openstreetmap/osmosis/apidb/v0_6/impl/EntityHistory.java. when searching visible
in osmosis. But not sure if the correct spot, as it has a very, very long history. Not so sure if osmosis will ignore it itself when directly reading pbf.
I guess it needs to be tested. Let me know if you have time to dig into this.
Though the parquetizer follows the v0_6 schema (which seems not containing the
visible
) from osmosis, it will cause the output files ignore the visible info if orignial PBF file contains.Are there any fast ways for us to also include it in the output?