Greenstand / Greenstand/treetracker-web-map-core

New implementation to jump the initial map view for planter/orgs

Open
#75 0 comments 0 reactions 0 assignees View on GitHub
challenge GIS leaflet
Dominant language
JavaScript
Stars
4
Forks
33
PR merge metrics
No merged PRs in 30d

Description

When we open the map for a single planter or org, we need to calculate the initial bounds/map view for the first jump, the previous algorithm is fetching the cluster from API and calculate the view at client side, now we are trying to use a new API to do it: prerequisite: https://github.com/Greenstand/treetracker-query-api/issues/79

So with this API, we simply request the bounds by filter, then manipulate the leaflet to jump to the bounds.

---

Some hints:

- Please read our [readme](https://github.com/Greenstand/treetracker-web-map-core#treetracker-web-map-core) for more information/guide/tutorial.
- Here is [an engineering book](https://greenstand.gitbook.io/engineering/) in Greenstand.
- To know more about our organization, visit our [website](https://greenstand.org).
- If you want to join the slack community (some resources need the community member's permission), please leave your email address.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the repository README and the prerequisite query-api issue #79 to understand the bounds endpoint and its filters. Then trace the single-planter or organization map-opening flow and the existing Leaflet initial-view calculation. Done means requesting bounds by filter and using the response to jump Leaflet to the initial bounds.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.