Opened 11 months ago

Last modified 10 months ago

#19141 new enhancement

wms parameter maxcc

Reported by: pch14@… Owned by: team
Priority: normal Milestone:
Component: Core imagery Version:
Keywords: Sentinel Cc:


Toying around with Sentinel data, which is not only good for planning ski-tours (how far to walk from the bus-stop or parking lot to where the snow starts) but also for coarse landuse questions, i.e. real work, I would like to add at source to Maps/Worldwide, c.f. 14921#comment:47

Unlike the ones already there, I'd propose to specify the "max allowed percentage of cloudiness" for server side selection of imagery to send. In the specific WMS this is called "maxcc" - yet, JOSM bails out, when set as a placeholder in the address.

Do you deem that a desireable enhancement? May I use some other percentage, that is already known?

PS: I have yet to research the permissions of the source there; the URL contains a kind of customer ID - now I used the one from sentinel-hub…

Attachments (0)

Change History (5)

comment:1 Changed 11 months ago by anonymous

PS: lists lots of stuff, but nothing about access permissions. So to me, this looks free for the general public.

PPS: cc in maxcc stands for cloud coverage

comment:2 Changed 11 months ago by anonymous

Nah, too early, there is which offers - What do you think are the chances, JOSM gets a lifetime "private" customer-uuid?

comment:3 Changed 11 months ago by anonymous

Perhaps, another WMS argument "api-key" is due? If you are the officer in Lienz, that will tell the farmers in Defereggen, whether they met their obligations to receiving EU-funding or if you are the OSM mapper, that wants to have recent satellite intelligence on landuse eg. should not matter, as the data per se is free, only the WMS preparation is bound by the sentinel-hub TOS?

comment:4 Changed 10 months ago by simon04

Component: External imagery sourceCore imagery

comment:5 Changed 10 months ago by anonymous

The other thread #85269744 had a game changing post by @imagico - I (the reporter) do no see much anymore in this issue here: Perhaps, my 2 cent only, the most flexible was, to let the config (taken from the WIKI, beware security!) define the parameters that JOSM will prompt the user for?

PS: What I wanted to say in previous post - no matter how the data came to OSM, as OpenData, the work done to convey it, should not matter to OSM, shouldn't it?

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.