Talk:Key:panoramax

Viewer link

The sole UUID of a picture does not allow to focus on an object in the picture itself or provide a direct link to view the picture.

Currently, we see some contributor putting links instead of UUID or adding additional view parameter ti the UUID. This creates a lot of complexity to re-use the panoramax=* tag values.

I propose to have a separate tag to provide an URL to directly view the object, maybe panoramax:view Cquest (talk) 17:15, 25 January 2025 (UTC)

@Cquest: If people are going to put just an URL which displays (among other things) some picture, than isn't that a job of existing image=*? What would be gained by having an additional different tag with same syntax and meaning (but limited to only one website)? --mnalis (talk) 17:58, 25 January 2025 (UTC)

I'll also note here that panoramax:view=* in particular is bad choice for key, as it seems to already be used for another purpose. --mnalis (talk) 02:10, 4 December 2025 (UTC)

The UUID does allow to provide a direct link to view the picture. Overpass Turbo does this for example. It's just that openstreetmap-website doesn't. There are user scripts that convince the OpenStreetMap website to turn them into a link anyway: [1], [2]. —M!dgard (talk) 20:44, 25 January 2025 (UTC)

As I said on the forum -- given that the web view link form allows specifying the additional parameters, why not just standardize on that? JesseFW (talk) 02:00, 26 January 2025 (UTC)

For those wondering, the forum discussion that is being referenced is here: https://community.openstreetmap.org/t/panoramax-tags-in-osm/124812 --mnalis (talk) 22:30, 27 January 2025 (UTC)

I suggest to use a simplest way: add the camera view parameters &xyz after te UUID.

panoramax=4bcfb95a-d584-4eae-8893-66dd47c47ecf&xyz=180.93/-3.87/89 documented in the FR wiki.

• Pro:
  • UUID give access to metadatas (unlike image=* with a full URL).
  • UUID don't select a specific instance of Panoramax (unlike image=* with a full URL).
  • Keep picture and camera view parameters in the same value.
  • Already work with JOSM tag2link and other softwares that simply construct an URL to open the picture in a web browser.
  • Already work with mapillary=* (and probably others) with camera view parameters.
    mapillary=125143396285066&x=0.8906538416111135&y=0.41258305625493996&zoom=3.
  • This respect the KISS principle.

• Cons:
  • Tag values are limited to 255 characters, so we could only add 6 UUID, and lesser with camera parameters.
  • Less "cleaner" or at least softwares must parse values.

--Pyrog (talk) 11:32, 28 January 2025 (UTC)

I agree. Multiple images are often encoded with numbered suffixes anyway (panoramax:1=*). MapComplete does this when adding images, for instance. —M!dgard 🇧🇪 (talk) 17:30, 20 February 2025 (UTC)

I'am against panoramax_1=* or panoramax:1=* numbered suffixes. iD did that in the past.

Well known solution is multiple values.

I hope that one day the OSM API support real multi-values (for example 0, 1 or more identical key with a single value), but this is another discussion.

--Pyrog (talk) 13:05, 5 April 2025 (UTC)

I'd also like if semicolon-separated values were feasible, but that requires (at the very least) tag2link support (so its downstreams like www.openstreetmap.org, iD, Vespucci etc. can use it) --mnalis (talk) 02:19, 4 December 2025 (UTC)

Number suffix is somewhat conflicting with year suffix, requiring the latter to be formatted as a range or 4-digit year to differentiate. Semicolon is enough.

Can Panoramax group views, similar to wikimedia_commons=Category:* ? But best to use the tracks themselves, the "Sequence" / collection , which you have a problem with defining panoramax=* for pic only.

Ideally, they can be specified eg entrance:panoramax=71297cbc-8f63-491f-a4cb-1a59c2591f5a

—— Kovposch (talk) 09:42, 28 April 2025 (UTC)

Just as a heads up - the link in mapillary with x/y/zoom do not work in iD - most likely for value validation. It works in josm though. I opened issues with josm/mapillary plugin to set x/y/zoom when viewing an 360° image, and against iD to provide a mapillary link when there is more than a numerical id. I love the idea of providing an exact viewport for objects the link is on.

Flohoff (talk) 12:48, 10 April 2025 (UTC)

Thanks. It seems that using &xyz in panoramax=* in fact:

• was never officially recommended nor supported by Panoramax team (panoramax=* should contain just the UUID)
• is not well supported (as noted by @Flohoff:) (as opposed to just using image=* with full URL which works fine everywhere where any images are supported)
• is not recommended and is likely to break in the future when there will be multiple different viewers available (see this community post)
• is (as of December 2025) order of magnitude less popular than the alternative: 485 for &xyz in panoramax=* uses vs. 2876 uses for just using image=* with full URL to panoramax server.

Thus I would advise against using it and just use image=* to point to full URL --mnalis (talk) 02:28, 5 December 2025 (UTC)

Is this not Key:ref:panoramax ?

This being a reference link to another system. Or has the ship sailed already? Jnicho02 (talk) 16:07, 27 April 2025 (UTC)

It's mapillary=* , flickr=*

If they are to be organized, it should be image:*=* similar to contact:*=* and payment:*=*

—— Kovposch (talk) 09:09, 28 April 2025 (UTC)

Multiple pictures

The english wiki page describe after the french page a wrong tagging scheme to add multiples values. See diff :

• FR 2024-06
• EN 2025-01

Adding a numbered suffix to the key create new keys. The (un perfect) current scheme is to use only one tag with values separated with a semicolon.

--Pyrog (talk) 22:29, 13 August 2025 (UTC)

The numbered suffix is in widespread use and is notably supported by MapComplete. Current usage numbers: semicolon: ~300; number suffix: ~7000. The French article should be updated. —M!dgard 🇧🇪 (talk) 18:19, 14 August 2025 (UTC)

Preserving orientation and zoom

It's a bad idea to use image=* because urls are too long and could change.

See Paramètres de la caméra to "simply" add camera parameters (orientation and zoom).

--Pyrog (talk) 22:44, 13 August 2025 (UTC)

Here I would favour the scheme described on the French page, yes. The URL being long is less an issue if we use numbered suffix keys (see above) ;) —M!dgard 🇧🇪 (talk) 18:22, 14 August 2025 (UTC)

Main talk about this subject is at #Viewer link, please read there! I would additionally note the concerns raised here:

• URLs fit just fine, and are not too long (limit is 255 chars)
• if URLs change, both schemes would break so there is no clear preference there
• the usage at Paramètres de la caméra is explicitly denounced by Panoramax team member as never intended. Would someone speaking French please update that page too? Thanks! --mnalis (talk) 02:39, 5 December 2025 (UTC)