Support
A map that will not load, something broken, or a format we do not handle yet? Tell us. Every one of these opens a pre-filled issue — you only have to fill in what happened.
Something is broken
The app crashed, a button did nothing, the map went blank.
A map will not load
It failed to import, came in crooked, or draws nothing. Say which file.
Something else
A question, an idea, or something that just seems off.
These go to a public issue tracker, so do not put anything in one you would not want read — a coordinate you would rather keep to yourself included. There is no data of yours held on any server to ask about: see Privacy for why that is short.
Common things
The importers are still being built, so some of this describes the app being made rather than one you can install today — see Where this is.
Which map files can I load?
Esri tile packages (.tpkx), Garmin Custom Map and Google
Earth overlays (.kmz), and .mbtiles. Those are
the formats the maps people buy and the maps governments give away
generally arrive in.
Can I load a GeoTIFF or a GeoPDF?
Not yet. Both are planned and neither is built, and until they are the app will decline the file rather than half-open it. If a map you have comes only in one of those, say so on the issue tracker — it is useful to know which publishers that affects.
Where do I get maps?
Free government topography is listed in the app, and it is the same material as USGS topoView, Natural Resources Canada, and OpenTopoMap. Paid publishers are listed as a link to their own shop; you buy from them, and Blaze never sees the transaction or the file.
My map is in the wrong place
Tile packages and MBTiles carry their own placement and should land where the publisher put them. A KMZ can be coarser, because it was drawn to be shown on a handheld unit rather than measured against a basemap. Send the file name and who made it and we will look at that map specifically.
Part of my map is blank
A map covers what its publisher drew and no more, so an edge is a real edge. Underneath there is a Canada-wide basemap, which is what you are looking at when the detail stops but the ground carries on.
Does a big map take twice the space?
No. Blaze copies the file into its own storage on import and reads it there, unpacking nothing. On the same phone that copy is a clone — near instant, and no second 1.5 GB on disk. From iCloud Drive or a computer it is a real copy, and Blaze checks free space before it starts rather than finding out half-way through. A KMZ is redrawn into tiles once, and the KMZ itself is then removed, so it is not kept twice either. The file you picked is left alone: deleting it does not delete the map, and deleting the map in Blaze does not touch it.
Does any of this need a signal?
Not once the map is on the phone. Downloading a map needs a connection, and so does filling in basemap you have never looked at before. Reading what you already have does not.
Getting a recording off the phone
Export it as a GPX and send it wherever you like. That is the only way anything about a trip leaves — Blaze does not upload tracks. See Privacy.
Reporting a problem well
The most useful thing you can include is which map you were looking at and what you expected to see. For an import that failed, the file name, its size and who published it are usually enough to reproduce it.
If it is the basemap that is wrong — a lake in the wrong shape, a road that is not there — that comes from OpenStreetMap, and fixing it there fixes it for every app rather than just this one. Tell us anyway if you would rather not edit a map yourself.
No GitHub account? Say so in any public channel you like and it will find its way — this is a small project, not a support desk.