search

gbif / portal-feedback

User feedback for the GBIF API, website and published data. You can ask questions here. 🗨❓
30 stars 16 forks source link

Queries with polygon #5210

Open gbif-portal opened 7 months ago

gbif-portal commented 7 months ago

Queries with polygon

I perform queries on Europe in a fragmented way, using the two polygons below in a CRS "4326". However, I get hits on the second polygon in a smaller bouding box, which doesn't match my polygon. polygon_eu_0 = 'POLYGON((-31.565747 32.097476, 2.479608666666667 32.097476, 2.479608666666667 49.184106666666665, -31.565747 49.184106666666665, -31.565747 32.097476))' polygon_eu_1 = 'POLYGON((1.8796086666666671 32.097476, 35.924964333333335 32.097476, 35.924964333333335 49.184106666666665, 1.8796086666666671 49.184106666666665, 1.8796086666666671 32.097476))'

User: See in registry - Send email System: Chrome 121.0.0 / Windows 10.0.0 Referer: https://www.gbif.org/user/download Window size: width 1553 - height 711 API log&_a=(columns:!(_source),filters:!(),index:'3390a910-fcda-11ea-a9ab-4375f2a9d11c',interval:auto,query:(language:kuery,query:''),sort:!())) Site log&_a=(columns:!(_source),filters:!(),index:'5c73f360-fce3-11ea-a9ab-4375f2a9d11c',interval:auto,query:(language:kuery,query:''),sort:!())) System health at time of feedback: OPERATIONAL

MortenHofft commented 7 months ago

It looks like you are doing this through pygbif

I'm not sure I understand what you are seeing. Perhaps you could link to an actual API query that is causing you issues? Or a UI state.

in WKT clockwise winding is a hole. counter clockwise is an enclosed area. We do not support outer polygons that is holes. Perhaps that is the reason?

notified by email

CecSve commented 7 months ago

@jhnwllr