Code-for-America-Projects-Hub
Code-for-America-Projects-Hub copied to clipboard
Retrieve brigade location latitude/longitude info from API
http://spatialconsortium.com/demo/cfaindex.html - pulling the brigades from the API is too slow. Downloaded the Organization.geojson file local to get initial map to render quicker, I will look at this more later...
Do we need the Brigades location or the Project's location? If a Brigade has a 100 projects, then there would be a 100 pins at the same lat/lng. @tangospring @rlh-aagis
Both locations are needed/used, I think.
Display
- two kinds of pins on the map:
- origin pin (brigade HQ) -- source: Code for America API;
- application pin (where the project is applied [this can be center of city, if no location is specified]) -- source: Google spreadsheet
- the location with multiple projects (origin pin (brigade HQ) would be one example), might use pin with number attached to it ( @rih-aagis is this good approach for multiple pins with the same geolocation?).
- there could potentially be a third kind of pin for projects with multiple application locations (one project--multiple application pins; Community map, for example), or this kind of pins could be combined with general "application location" pin type. -- source: project repo.
All, I'd like to recommend we start first with brigade location only at first, then incorporate project locations during a later phase. On Apr 7, 2015 12:56 AM, "Paul D Barham" [email protected] wrote:
Do we need the Brigades location or the Project's location? If a Brigade has a 100 projects, then there would be a 100 pins at the same lat/lng. @tangospring https://github.com/tangospring @rlh-aagis https://github.com/rlh-aagis
— Reply to this email directly or view it on GitHub https://github.com/codeforkansascity/Code-for-America-Projects-Hub/issues/60#issuecomment-90375210 .
Sounds good (unless you can pull in another guy from GIS meetup to do project location pins in parallel, Ron ;-) That map with brigade locations looks fantastic, btw.