Because geo-index updates are very time consuming, here is more detailed information:

If you made an update from V10 to V11 (major release) or an update of service pack (V11 SP0 to >=SP4), you should update the geo-index. For all other combinations you have to check the features if it’s important for a specific customer (see list below).

If you use geosearch / topo search also for PARTsolutions catalogs (not only native customer catalogs), you should update the geo index in PARTadmin for all catalogs. If you only install a new update of a catalog (new CIP), the fixes will not be active because CIPs are generated with an older PARTsolutions release and so your PARTsolutions installation doesn’t fit together with the installed geo index. Basically geosearch / toposearch will work, but not as good as it could be with updated geo index with all the improvements and the fixed topics.

-> So for native geosearch catalogs this is ok, because the geo index will be updated with the installed version at customer. So he will always get the correct index.

But if you update or install PARTsolutions catalogs from time to time you will get the old geo index again. So you have to update the index manually after the updates again.

Listing of V11 features where updating of geo-index is relevant:

For SP0 and SP4 generation of indexes is recommended, for SP3 only if respective features shall really be used.