-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gadm search #13
Gadm search #13
Conversation
…red as arrays split by | in the database as JSON arrays
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't check the queries. The rest seems ok. The formatting seems random in some places though.
geocode-api/src/main/java/org/gbif/geocode/api/service/GadmService.java
Outdated
Show resolved
Hide resolved
Yes, please. :-)
…On Wed, Sep 16, 2020 at 12:03 PM Matt Blissett ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In geocode-api/src/main/java/org/gbif/geocode/api/service/GadmService.java
<#13 (comment)>:
> +import javax.annotation.Nullable;
+import javax.validation.constraints.Max;
+import javax.validation.constraints.Min;
+
+public interface GadmService {
+
+ Collection<GadmRegion> ***@***.*** String query);
+
+ Collection<GadmRegion> ***@***.*** String query, String gid0);
+
+ Collection<GadmRegion> ***@***.*** String query, String gid0, String gid1);
+
+ Collection<GadmRegion> ***@***.*** String query, String gid0, String gid1, String gid2);
+
+ PagingResponse<GadmRegion> ***@***.*** String query,
+ @max(value = 2, message = "Only levels 0, 1 and 2 are supported")
Shouldn't level 3 be supported?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#13 (review)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADQ723VDAR7CXVEPKUJXJLSGDHTXANCNFSM4Q6JIOQQ>
.
|
|
…ot url as a lookup service with and "subdivisions" nested url
This PR supports the functionality described in issue #8