Greenstand / Greenstand/treetracker-web-map-core

A option/method to support: valid area feature.

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

Description

On the web map client, for example, when open this page: http://localhost:3000/planters/940

image

The map area is trying to focus on the given planter, (there is a function in the core to calculate the initial area for this), but, the problem is, as shown in the picture, the map is partially covered by a drawer/panel, so, the map eventually in the end user's eys is not focused perfectly on the current planter.

We need to consider an option or function to make the map core aware of the 'valid' area of the current map, so it would take this in consideration when calculate the initial map view.

For example:
```
new Map({
validVisualArea: {top: ?px, left: ?px, bottom: ?px, right: ?px}
})
```
Here the for properties expresses the rectangle of the area on the current map screen.

---

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, then locate the core function that calculates the initial map area and the Map constructor or options handling. Define how the validVisualArea rectangle affects the initial view, and verify that a planter is centered within the unobscured map area when a drawer or panel covers part of the screen.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.