americanredcross / geowebservices Goto Github PK

Let the client side handle sorting out the results of a given query, maybe with a parameter attached to the query like

?sources=0 //Returns GeoDB results
?sources=1 //Returns Geonames results
?sources=2 //Returns both

Everything else (including source ID at the object level) seems to be in place for this to work already.

Most of the parts for this already exist.

• We just need to add support for a hit test on the map and then send the x/y to the existing API endpoint to return and present the stack.
• User could then name the location and it would be added in to a “red cross locations” table of x/y places and a GUID would be created.
• When a place is created the GIS team could then research it and add the place to OSM if appropriate.

When user clicks on a GAUL multipart polygon the zoom to bounds zooms to the wrong extent. It will zoom to one of the features instead of the overall multipart boundary.

To help address the above situation we could pass bounding box as part of the query to the database with an intersect or contains option to limit the results to only the bounding box of the map.

Enable user to page through all responses when result list is greater than 10.

We've now encountered multiple projects/grants where it is managed at a regional or global level and entering all country-level activities as child projects may not make sense.

These include:
-Measles Initiative
-GDPC first aid apps
-GDPC hazard app Asia
-hazard app/social media Caribbean
-Cash in emergencies LAC, Africa and Asia

I'd like to consider the possibility of allowing two new 'admin' levels so that these types of projects are not forced to create child projects considering all ARC management is centralized at regional or global levels rather than the country level.

give the user the option of requesting all of the siblings similar to GeoNames so that you can request all of the admin boundaries at a given admin level that fit within the next highest admin level.

When requesting a feature using NameSearch allow user to request a datasource: source=naturalearth and a limit: limit=1

• GADM is planning on releasing an up to date release in August 2015.
• We need to rerun our gadm cleanup process on the data and upload it
• Query needs to add a default year to 2015 with the user option to change the year