1 Signing in
Open the upload page in a browser. If you are not signed in you are sent to the login page automatically.
- Enter your username and password. Both are supplied by your administrator; there is no self-registration.
- Press Sign In, or just press Enter.
If the details are wrong the page says so and clears the password box. Three or four failed attempts is usually a caps-lock problem rather than a wrong account.
After that you are asked to sign in again. Signing out from one browser does not affect another.
The bar across the top
| Control | What it does |
|---|---|
| Your username | Shown with a diamond marker. Confirms which account you are working as, which matters because imagery is owned per user. |
| Sign out | Ends the session and returns you to the login page. Anything already uploaded keeps working; only your browser session ends. |
| GIS Solved logo | Opens the GIS Solved website in a new tab. It never navigates away from a part-finished upload. |
2 Choosing what to upload
The drop zone
The large dashed panel is where imagery goes in. You can either drag files onto it, or click it to open a file browser.
Accepted imagery: TIFF (.tif, .tiff),
JPEG (.jpg, .jpeg) and PNG (.png).
Accepted sidecars: .tfw, .jgw, .pgw,
.wld and .prj.
The file browser allows multiple selection — hold Ctrl and click both. You can also drag them on one at a time; the page pairs them up as they arrive.
Why a world file is needed
A world file is a small text file of six numbers telling GIS software where the image sits on the ground and how big each pixel is. It shares the image's name with a different extension:
| Image | World file |
|---|---|
photo.tif | photo.tfw |
photo.jpg | photo.jgw |
photo.png | photo.pgw |
JPEG and PNG cannot store georeferencing inside the file, so for those the world file is compulsory — the upload button stays greyed out until you add one.
TIFF can carry georeferencing internally. If yours does, a world file is optional. If you supply one anyway, it takes priority over what is embedded in the file.
What the page shows once files are chosen
| Element | What it means |
|---|---|
| File name and size | The image you selected. The size shown is the original file, before processing. |
| Cross button | Removes everything selected and returns the page to its starting state. |
| world file | The image and its world file were matched successfully. |
| .jgw required | This format needs a world file and none was found. Add the matching one. |
| no world file | A TIFF was supplied on its own. The georeferencing inside the file will be used. |
| projection | A .prj file was included. It overrides the projection choice below. |
| too large | The file exceeds the size limit. See Limits and rules. |
Selecting ortho.jpg together with survey.jgw is rejected, because a
world file only belongs to the image sharing its name. Rename one to match the other.
3 Source Projection
This tells the system which coordinate system the imagery is currently in. It is the single most important setting on the page.
The imagery simply appears in the wrong place on the map — possibly in another country. If you are unsure which projection your imagery uses, ask whoever supplied it before uploading.
| Option | When to use it |
|---|---|
| Auto-detect | The default. Reads the coordinate system from inside the image. Works for TIFFs that carry their own georeferencing. If the image has none, the upload is rejected with an explanation rather than a guess. |
| BNG | Forces EPSG:27700, British National Grid. Use for the usual UK survey and Ordnance Survey based imagery. |
| Custom EPSG | Reveals a box for any EPSG code, for example 32630 for UTM zone 30N. Use when you know the code and it is neither BNG nor already embedded. |
| Already 3857 | Skips reprojection entirely. Only for imagery already in Web Mercator, EPSG:3857 — typically something exported from a web mapping tool. Choosing this by mistake places the imagery incorrectly. |
The EPSG code box
Appears only when Custom EPSG is selected. Enter the numeric code alone, without
the prefix — 27700, not EPSG:27700.
A world file carries position and scale but not projection, which is why this setting
exists at all. If you included a .prj file, that always wins and this setting is ignored.
4 Compression and Optimisation
This controls how the converted copy is stored. It affects file size, visual quality and how much of your storage allowance is used.
| Option | What it does |
|---|---|
| DEFLATE | The default, and the right choice for most work. Lossless — no pixel is altered. Typically 30–50% smaller than the original. |
| JPEG | Lossy compression, 60–80% smaller. Suitable for aerial and drone photography. Not suitable for anything where exact pixel values matter, such as classified or elevation data. |
| None | No compression. Fastest to process, largest on disk. Rarely the right choice unless processing speed matters more than storage. |
The JPEG Quality slider
Appears only when JPEG is selected. It runs from 50 to 95 in steps of 5, and defaults to 85.
- 50 — smallest file, most visible artefacts.
- 85 — a good balance, suits most aerial photography.
- 95 — close to lossless but noticeably larger.
If your imagery is not a perfect rectangle — an angled flight line, or a survey area with a ragged edge — JPEG gives it hard black edges. Choose DEFLATE to keep those areas transparent.
Overview pyramids
The note at the foot of this section is a statement, not a setting. Overview pyramids are smaller copies of the image built automatically at several scales, so the map draws quickly when zoomed out. They are always built and cannot be turned off. They add roughly a third to the stored size, and they are the reason tiles appear instantly rather than after a pause.
5 Uploading and processing
The upload button
Labelled Process & Generate Endpoint. It stays greyed out until the page has everything it needs — an image, its world file where one is required, and a file within the size limit. Original uploaded files, together with their world files and any projection files, are deleted automatically approximately seven days after upload. Published imagery is unaffected. You are responsible for retaining your own copies of source files.
The progress bar
Progress runs in two distinct phases, which is why it does not move at a steady pace.
| Stage | What is happening |
|---|---|
| Uploading, 0–50% | The file is transferring from your computer to the server. Time depends on file size and your connection. |
| Queued for conversion | The file has arrived safely. It is waiting for a conversion slot — two run at a time across all users. |
| Reprojecting | Reprojection to Web Mercator and pyramid building. If others are ahead of you, the label shows how many. |
| Done | Conversion finished. The result panel appears below. |
The browser is not holding the connection open — it checks for progress every few seconds. A large image may take several minutes, and that is normal.
If something goes wrong
A red box appears with the reason. The common ones are a missing world file, no coordinate system that could be determined, or a file above the size limit. The message names the problem; correcting it and uploading again is usually all that is needed.
6 The result panel
Appears when conversion finishes and contains everything needed to use the imagery elsewhere.
Size summary
| Figure | Meaning |
|---|---|
| Original | The file as you uploaded it. |
| Processed | The converted copy, including its overview pyramids. |
| Saving | The difference as a percentage. A green negative figure means smaller. An increase is normal for a small or already-compressed source, because the pyramids are added. |
The two URLs
Each has a copy button at its right-hand end. Click it to put the address on the clipboard.
| URL | Where to use it |
|---|---|
| WMTS | Mapscape. The preferred option — it carries the tile size, scale set and extent, so the software configures itself. |
| XYZ Tiles | QGIS and Leaflet. A direct tile address. In QGIS set the tile resolution to 256 and the DPI to 96, since these are not carried in the URL. |
Open preview
Opens a simple map in a new tab showing your imagery over an OpenStreetMap background. Use it to confirm the imagery has landed in the right place before giving the URL to anyone else.
Pan to the edge of the imagery and compare it against the background map. Problems with position or scale are far more obvious at the edges than in the middle.
Upload another file
Clears the page and returns it to its starting state, ready for the next image. Nothing already published is affected.
7 Storage Usage panel
At the foot of the page. Shows what you are using and lets you remove imagery you no longer need.
| Column | Meaning |
|---|---|
| Uploads | The original files as you sent them. |
| Tiles | The converted copies that serve the map. Usually the larger figure of the two. |
| Total | Both together. This is what counts against your allowance. |
| Bar | Your usage shown against the largest user on the system. |
Administrators see every user here. Everyone else sees only their own figures.
The layer list
Beneath the figures, each published image is listed with its size and a Delete button.
It removes the file from the server, and the WMTS and XYZ addresses stop working immediately. Any ArcGIS Online map using that layer will show a blank space. Check nobody is relying on it first.
An entry marked re-upload to manage is a file left over from an earlier version of the system. It still occupies disk space but cannot be removed from this page — ask an administrator.
Refresh
Reloads the figures. Useful after deleting several items, or when someone else has been uploading.
8 Limits and rules
| Limit | Detail |
|---|---|
| Maximum file size | 4 GB per upload. This is a hard limit of the web server, not a setting. Larger imagery must be split into tiles before uploading. |
| Storage allowance | Set per user by an administrator. Both the original and the converted copy count towards it. An upload is refused before it starts if it would not fit. |
| Server disk reserve | Uploads are refused if the server as a whole is running short of space, whatever your personal allowance says. |
| Original file retention | Original uploads are removed automatically after a set period. The published imagery is unaffected and keeps working. |
| Concurrent conversions | Two run at a time across all users. Others queue and start automatically. |
9 Adding imagery to Mapscape
- Copy the WMTS URL from the result panel.
- In Mapscape use Add Data Widget.
- Paste the URL. Make sure WMTS OGC as the type is selected.
- Add the layer to the map
For ArcGIS Pro, the same WMTS URL is added through Insert → Connections → New WMTS Server.
ArcGIS Online cannot supply a password, so published imagery is reachable by anyone who has the address. The address contains a long random identifier and is not guessable, but treat it as you would an unlisted link rather than a secret.
10 If something is not working
| Symptom | Likely cause |
|---|---|
| Upload button stays greyed out | A JPEG or PNG without its world file, or a file over the size limit. Check the coloured status rows beneath the file name. |
| Imagery appears in the wrong place | The wrong Source Projection. Delete the layer and upload again with the correct setting. |
| Black edges around angled imagery | JPEG compression was chosen. Upload again with DEFLATE to keep those areas transparent. |
| Blurry when zoomed right in | The imagery is at its natural resolution. Zooming beyond it enlarges pixels; there is no more detail to show. |
| Layer will not add to ArcGIS Online | Check the URL was copied in full, and that the preview page displays correctly first. |
| Upload refused for space | Your allowance is full, or the server is low on disk. Delete imagery you no longer need, or speak to an administrator. |