Long-term Geographic Features planning

[jywarren]

This is not a regular issue, but is a long-term tracking issue for all Geographic features. It's related to work on this repository (formerly #1070) and to publiclab/leaflet-blurred-location#1

---

Release v0.1 - bare bones minimal useful release

• inline maps: [map:content:lat:lon] or [map:nodes:lat:lon] (just nodes)
• load half a degree box around map center - started with snipping the last digit (i.e. 71.0 for "lat:71.05") to show the next zoom level up from specified center
• Leaflet map
• maps of multiple things, like [map:all:lat:lon] https://publiclab.org/wiki/inline-maps (Combined people/content inline maps #3090)
• maps PER TAG: [map:tag:______:lat:lon]
• default display on each tag page, like https://publiclab.org/tag/stormwater or https://publiclab.org/tag/air-quality - under a tab?
• zoom (ability to specify custom initial zoom level)
• initial "location entry" interface without privacy, via first release of Planning overview leaflet-blurred-location#1

---

Release v0.2 - "people and privacy"

v0.2a - Location entry

(mostly via publiclab/leaflet-blurred-location#1)

• standardize for use in nodes or profiles via separate module for BlurredLocation
• creates tags "lat:____", "lon:_____", "blurred:true", "place:buffalo-ny"
• parameterize location as you type, so you see buffalo-ny appear as you type "Buffalo, NY", and this is submitted as place:buffalo-ny with description "Buffalo, New York, ZIPCODE, USA"
• display tag desc on tag hover (made into FTO at Display a description field for tags, if it exists #1406)
• use tag description field for full placename? So "place:buffalo-ny" would have description; "Buffalo, New York, ZIPCODE, USA" ?
• display tag desc on tag page
• manual entry "place:buffalo-ny" auto-generates lat:xxx + lon:xxx - at what zoom level? "City"? Check google geocoder precision field?
• Offer recent locations used so you can quickly reuse ones you've already entered? Last 3? And the location you've entered on your profile if that exists?

v0.2b - Map displays

• Upgrade: bounding box request on drag or zoom (ability to refresh displayed inline maps' displayed data when you pan/zoom #1934)
• Search box with geolocation and map refresh (follow-up to ability to refresh displayed inline maps' displayed data when you pan/zoom #1934)
• Advanced short codes for inline maps:
  • (v0.2) [map:people:lat:lon] (just people: requires privacy blurring)
  • (v0.2 or v0.3) variations like [map:question:_____], [map:activity:_____]
  • (abandoned) [map:content:Buffalo, NY] (can this work?) or [map:content]Buffalo, NY[/map]? -- no, let's just do this via the UI
• Map display on additional standard pages: /people or /questions (in second half of Add map of people to publiclab.org/people #1940)
• display of blurred locations:
  • show blurred locations for only a range of zoom levels. When you zoom in too far on a blurred location, stop displaying it. Calculate this based on number of decimals and the zoom level.
  • For the highest zoom levels of display, begin showing a region instead of a point (think this through)
  • when does it stop being a point? when you zoom in far enough?
  • no longer display an anything for 41.03,71.04 if you zoom past xx.xx resolution?

v0.2c - Map API

• way to request located nodes or profiles (ability to refresh displayed inline maps' displayed data when you pan/zoom #1934)
• JSON content at URL: tag/tagname.json?geo=true&lat1=__&lat2=__&lon1=__&lon2=__ (bounding box) -- or just within 1 precision digit of /api/geo/41.0/51.8 (ability to refresh displayed inline maps' displayed data when you pan/zoom #1934) - coordinate w API team
• in GeoJSON - coordinate w API team
• eventually allow for natural language queries like /geo/q=Buffalo, NY ? - coordinate w API team
• relying on calls of this type will also make pulling in JusticeMap content easier

Geo Subscriptions

• area-based tag-based subscriptions? Perhaps via wildcard subscriptions?
• "near me" or "near X" vía user tag like follow:near:lat:lon? Coordination w subscriptions team + UI design for this (default to your own location?)

[mridulnagpal]

@jywarren Shall we start with the integration?

[jywarren]

Sure, how's the display library going? For interface, I'd like to suggest you try to get the basic input to display in a partial template, as you originally did, but this time using the new library!

…

On Aug 25, 2017 3:08 PM, "Mridul Nagpal" ***@***.***> wrote: @jywarren <https://github.com/jywarren> Shall we start with the integration? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1416 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABfJxpV8v2CSZT_ib1ZzRxk_E-Mw7YFks5sbxuRgaJpZM4NYYC9> .

[mridulnagpal]

The display library is at a prototype stage now, it builds fine and has some basic methods.

[mridulnagpal]

We need to add the leaflet-blurred-location library to npm first, or we just link it from github itself?

[mridulnagpal]

The version is 1.1.0 and the name is leaflet-blurred-location
Should I change anything?

[jywarren]

I trust your call -- should i grab the latest master and publish it? :-)

[jywarren]

added integration steps from #1655 !!