Placesearch Custom POI ECOS Integration

[hallahan]

It looks like the place search feature essentially redirects the browser to the right ECOS URL, which in turn inputs a new location into the Salesforce API. I'm seeing this happen here in our code:

https://github.com/AmericanRedCross/GeoForce/blob/33bf1e5add505ba1d61f0e8b07c3a0076a6b1f6e/Chubbs/public/placesearch/search.html#L543

We provide two possible sets of query params:

1. A feature id if it is a GADM boundary.
2. A place name and x,y coordinates if it is a Geonames point.

https://geo.redcross.org/placesearch/search.html

The following are screenshots from Enzigma showing how ECOS interacts with the Placesearch feature found in GeoForce.

When looking around in ECOS, however, we've got much more info about a location, such as the applicable administrative levels something is in, etc.

We probably will have to send other information from the place search feature to properly describe a new custom POI location.

A Project Location

Because the GET request via a browser window.location redirect doesn't send that much information, ECOS does indeed query GeoForce for more data. We will update this issue with the specific endpoints.

This code is done within the ECOS developer console.

The logic is within the LocationController.

The global settings contain a "GIS URL", which is the hostname of GeoForce.

[hallahan]

Requirements from @dalekunce in https://github.com/AmericanRedCross/GeoWebServices/issues/13

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.