Hi, My use case is to do forward geocoding using on premise Nominatim/OSM API for US region. So far, we have discovered about 2600 post codes that OSM does not recognize, but the same set of post codes return a valid response from other commercial APIs like Bing, USPS etc. Post codes 10043, 36685, 99711 are such examples. Also, if I do reverse geocoding with lat/long obtained from other sources for the list of 2600+ post codes we have, Nominatim returns a different post code. Please let me know if : - this is an expected behavior? - there was a reason why these post codes were dropped - like they are not valid anymore; invalid codes etc.? - there is a process within OSM community to drop/update such data regularly based on any rules (and what those rules are, if any)? Thanks.

Hi, My use case is to do forward geocoding using on premise Nominatim/OSM API for US region. So far, we have discovered about 2600 post codes that OSM does not recognize, but the same set of post codes return a valid response from other commercial APIs like Bing, USPS etc. Post codes 10043, 36685, 99711 are such examples. Also, if I do reverse geocoding with lat/long obtained from other sources for the list of 2600+ post codes we have, Nominatim returns a different post code. Please let me know if : - this is an expected behavior? - there was a reason why these post codes were dropped - like they are not valid anymore; invalid codes etc.? - there is a process within OSM community to drop/update such data regularly based on any rules (and what those rules are, if any)? Thanks.