tibiamaps / tibiamaps/tibia-map-data
Making it easier to contribute marker data
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 91
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Update: The spreadsheet is here!
In https://github.com/tibiamaps/tibia-map/issues/32, @LeeKunTibia brings up how much of a hassle it is to add markers by exploring in-game. There must be a better way!
I’ve just simplified the structure of the JSON data. For each floor, it’s now an array of objects, and each object represents a marker. See https://github.com/tibiamaps/tibia-map-data/blob/master/data/floor-07-markers.json for an example. Adding markers by editing the JSON is now easier than ever — however, submitting pull requests on GitHub for each change can still be painful.
Idea: set up a Google Docs spreadsheet where trusted contributors like @LeeKunTibia and @Hunter-of-Dragoes can enter the following:
-
a
tibiamaps.io/mapURL (the idea is that you could just find the right pixel on the map, and then copy-paste what’s in your address bar)example:
https://tibiamaps.io/map#32359,32126,7:3 -
the icon type (see the “short name” column on https://tibiamaps.io/guides/map-file-format#map-marker-data)
example:
star -
optionally, a description
example:
Levitate spot
I could then “sync” the spreadsheet every two weeks or so with this repository, adding the new markers.
This would make it significantly easier to suggest new markers, without having to necessarily open the game client and upload any files.
@LeeKunTibia, @Hunter-of-Dragoes, what do you think?
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
Review the linked spreadsheet, the example data/floor-07-markers.json file, and the map marker format guide. Determine how marker rows should map to the repository’s JSON structure and what synchronization process is expected. Done should mean that agreed spreadsheet entries can be reliably incorporated into the marker data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- data, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100