aws / aws/amazon-sagemaker-examples
[Content Improvement]: add more precision to the lat lon values in the example data file
- Dominant language
- Jupyter Notebook
- Stars
- 11k
- Forks
- 7k
- Avg merge
- 8h 29m
- Merged PRs (30d)
- 8
Description
**Link to the notebook**
[Add the link to the notebook.](https://github.com/aws/amazon-sagemaker-examples/blob/main/sagemaker-geospatial/vector-enrichment-reverse-geocoding/vector-enrichment-reverse-geocoding.ipynb)
**What aspects of the notebook can be improved?**
the example dataset used for this notebook has lat and lon values with only 2 numbers to the right of the decimal. lat and lon value should typically have 4-6 numbers to the right of the decimal. the notebook still works, but the result is that if you zoom in on the map, you can see that the points are clearly on a grid instead of being a true representation of where the locations were intended to be. This does not invalidate the usefulness of the notebook itself but if the example data file could be replaced with one that has more precision for lat and lon it would improve the look for the resulting visualization.
**What are your suggestions?**
replace the example data file with a file that has lat and lon defined with more numbers to the right of the decimal.
Contributor guide
Research direction
Start with the linked vector-enrichment-reverse-geocoding notebook and inspect which example data file supplies the latitude and longitude values. Replace that referenced file with data using more decimal precision, then run the notebook and verify that the mapped points no longer form a visible grid when zoomed in.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, jupyter-notebook
- Domain
- data-visualization
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100