Well, you can still use the approach in my post.
In the overloaded method applyWayTags I extract the postal code from the ReaderWay way and store them in my custom Storage postCodeMapping, but nothing prevents you to inject whatever custom logic you want and store them in whatever custom storage you want.
In your case you may want to consider to build a HashMap containing the Long osmID as a key, and your custom attributes as a value, put them in applyWayTags and finally process them in overloaded method finishedReading() prior to flushing your storage.
Good luck!
1 Like