search

AmericanRedCross / disaster-asset-manager

node app to make building the mapfolio a lot easier
0 stars 1 forks source link

fine tune geo data / extent(s) for v0.1 #20

Open danbjoseph opened 9 years ago

danbjoseph commented 9 years ago

ideas:

  1. Single, upper level admin level for extent(s). No geo data section.
    • per disaster you choose an upper level admin level. (e.g Districts for Nepal, although at 75 the list is a bit long. at only 14 the zones are a more manageable list but you lose a lot of detail)
    • in config provide the admin level being used and then instead of "Extent(s)" it asks you to select all applicable {{admin level}}
    • in the array of extents in config the first two options are always World, {{country}}
  2. Some sort of cascading select with the levels provided in config or through a csv file or something.
  3. Linking to GeoWebServices (see #5)
  4. Having the user select the centroid (or approx bbox) via a leaflet map (see #18)
kevinlustig commented 9 years ago

Going to clean up some of the other related tickets and use this as the master ticket for now.

The GeoWebServices documentation seems like it may be out of date. I followed the documentation I found via #5, but all requests to that IP are being rejected. They're acknowledged, so it looks like Express is running there, but all routes from the documentation return a "Cannot GET" or "Cannot POST" response. Should I expect this application to be up and running at the dev IP provided in the documentation, or do I need to set up my own version of this parallel to the Asset Manager?

For now, I'm going to pursue the basic map concept, letting users identify a point for the centroid. We'll leave the vanilla "Extents" select list intact because this doesn't seem to fully replace that functionality without also having some kind of GeoWebServices tie-in.

kevinlustig commented 9 years ago

I think we have a reasonable minimum solution in place at this point with the addition of a basic interactive map and a geolocation search. However, I would like to tap into the GeoWebServices when we can, both for letting users pick a centroid and also for defining the applicable regions/admin levels for a given response. So, I'll put this on hold for now and assign it to a future milestone.

If you think this is critical before we shrinkwrap v0.1, just let me know and assign it back to that milestone.