ProfessionalWiki / ProfessionalWiki/Maps
Help adding an interactive map to my wiki
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 78
- Forks
- 65
- Avg merge
- 9h 17m
- Merged PRs (30d)
- 6
Description
Hey, I have just started trying to get a mediawiki map up and running for our shadowrun community and im hitting a bit of a hickup. I am trying to pull in this map as a baseline to use https://www.google.com/maps/d/u/0/viewer?mid=1Pz-JoC3YhnnrmTy-mfCAWZxZrCyisVIJ&ll=47.813105219177764%2C-77.93084394999997&z=3 . To do this I have download the kmz file after clicking keep data up to date and uploaded the file to my server.
I am using this to generate the map on the wiki page.
{{#ask: [[Coordinates::+]]
| ?Coordinates
| ?Archetype
| ?Faction
| ?BackgroundCount
| ?Noise
| format=leaflet
| kml={{filepath:Shadowrun_Map_Unification_Project.kmz}}
| width=90%
| height=800px
| center=Seattle, WA
| zoom=9
}}
the map does appear, and does add in our custom marks that get discovered with the query but I don't see it including any of the data from the kmz file. I've tried a few iterations like downloading without the keep updated box, and gkml instead of kml but still no luck. any ideas why this might not be working?
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
Reproduce the wiki page's #ask query with the uploaded Shadowrun_Map_Unification_Project.kmz file, comparing the kml and gkml parameters mentioned in the report. Verify whether the map renders the KMZ data as well as the custom query marks; done means identifying why the KMZ layer is absent or documenting the supported configuration.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-visualization, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100