search

planetfederal / registry

pycsw + elasticsearch + opensearch + swagger - Based on HHyperMap
MIT License
11 stars 9 forks source link

Non geospatial CSW records #134

Open ingenieroariel opened 7 years ago

ingenieroariel commented 7 years ago

pycsw supports CSW records with no geometry but registry currently blocks them.

We can create something like REGISTRY_ALLOW_NON_GEOSPATIAL as an environment variable, my thinking is that the default should be False and users should know what they are doing if they set it to false but it'd be great if someone with a different perspective can chime in. /cc @mrcnc

mrcnc commented 7 years ago

I like the idea of an environment variable for this. I don't think it's a good idea for registry to insert non-geospatial records in the CSW database but not also put them into the search index (b/c the point of registry is to mirror the catalog records into elasticsearch for faster searching). So maybe the default should be True? I'd like to prevent divergence between the 2 data stores as much as possible. The other option would be to reject any non-geospatial records from entering either data store.

Also, my observation has been that requiring people to define an extent will cause them to enter null island or the entire world extent if they don't know the actual extent. This incorrect metadata can negatively affect the relevancy of search results.