NetLogo / NetLogo/GIS-Extension
`gis:create-turtles-from-points`: Turtle placed outside of envelope when envelope set to `gis:envelope-of` the dataset in question
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 36
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Steps to Reproduce:
- Download https://data.cityofchicago.org/Public-Safety/Fire-Stations/28km-gtjn, the fire stations map from the city of chicago
- import it into the GIS extension
- run
gis:set-world-envelope gis:envelope-of <the_fire_stations_dataset> - run
gis:create-turtles-from-points fire_stations_dataset turtles [] - Observe the following error:
Tried to create turtle outside GIS envelope at: (-85.04320641132607, 41.60757853756865, NaN). Try setting your GIS world envelope with gis:set-world-envelope (gis:envelope-union-of (gis:envelope-of your-first-dataset) (gis:envelope-of your-second-dataset) etc.))
- Run
show gis:world-envelopeand observe the output[-85.35946191554375 -84.99406832484011 41.607578537568656 41.97297212827229]
The desired behavior should be for the turtle to be placed within the NetLogo world, even if it has to get nudged just a tiny bit to not be on the edge of the envelope
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the gis:create-turtles-from-points behavior and reproduce the case using the Chicago fire-stations dataset and an envelope from gis:envelope-of. Check how points on the gis:set-world-envelope boundary are handled; done means the turtle is created inside the NetLogo world without the outside-envelope error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100