GIScience / GIScience/mapswipe-processing
import workflow need to be adjusted to new mapswipe api
Open
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
The mapswipe api has changed.
We need to ensure that all requests etc. point to the correct ip address and that results are tranfered to the right format.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the import workflow and its API request and result-conversion code. Compare the current endpoints and result format with the new MapSwipe API specification; done means requests use the correct IP address and imported results are transferred in the required format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100