IPT

Download

ipt@lists.gbif.org

June 2009

3 participants
2 discussions

How to define request with more that one filtering criteria in gbif density data service
by riihi tonttu 26 Jun '09

26 Jun '09

Hi, Sorry if this question is misplaced in this mailing list. If there is a mailing list that is more specifically focussed on the gbif webservices API, I’d be very grateful that you would give me the address of the list ( I’ve looked but haven’t been able to find one). I’d like to know how to define a request with more that one filtering criteria in the gbif density data service. For instance, the following request extracts a kml density file of all occurrences in Canada http://data.gbif.org/ws/rest/density/list?originisocountrycode=CA&format=kml However if I add the constraint that the occurrences come from the OBIS network: http://data.gbif.org/ws/rest/density/list?resourcenetworkkey=3&originisocou… only one constraint is taken into account (resourcenetworkkey), the originisocountrycode is disregarded. Is there any way of combining several filters in a density request? Thanks very much. saikari

1 0

requesting a feature for posting elements written in regional language
by Burke Chih-Jen Ko 22 Jun '09

22 Jun '09

Hi Tim, Following what I briefly mentioned in the e-Biosphere, here I describe it to hopefully make it more comprehensive. Now we TaiBIF are doing data cleaning against our specimen data, one of the tasks is to separate information written in different languages. Take 'Locality' as an example, if an attribute is 'Taipei 台北', we move '台北' to a separate column named 'LocalityInChinese'. (Considering easiness for data providers, we decided to use 'InChinese' instead of 'zh_TW'.) Then you see several descriptive elements in Darwin Core could have their counterparts in Chinese, like Collector, Identifier, and many others. To be used by regional data providers, IPT will be even better if it can handle multiple languages. Actually we had thought about just keep all languages in one place, but I am afraid that it might create problems when information is exchanging worldwide. As I am aware that language issues could lead to further discussions of the standard, I, therefore, propose a neutral mechanism that users can add their own elements, so that once an element is created, it can automatically map to the column with the same name, when a SQL source is connected or a csv sheet is uploaded. There should also be statistics based on the new element, or users can decide they don't want it calculated. In this case, I would add 'LocalityInChinese' as the new element. Hope this make sense. Cheers, Chih-Jen(Burke)

2 1