Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

order of variables in URL command #44

Open
falkamelung opened this issue Jan 4, 2021 · 2 comments
Open

order of variables in URL command #44

falkamelung opened this issue Jan 4, 2021 · 2 comments

Comments

@falkamelung
Copy link
Member

falkamelung commented Jan 4, 2021

Is there flexibility with the order of variable in the URL? If there is I would suggest the following which is more logical (minScale is only needed if colorscale is given and colorscale is more important than pointLat)

startDataset
colorscale
minScale, maxScale
pointLat, pointLon

https://insarmaps.miami.edu/start/19.4287/-155.2043/11.2361?flyToDatasetCenter=false&startDataset=S1_IW12_087_0527_0531_20141116_20191226&pointLat=19.41179&pointLon=-155.27178&minScale=-200&maxScale=200&startDate=20180423&endDate=20180505&colorscale=velocity

@stackTom
Copy link
Contributor

stackTom commented Jan 4, 2021

The variables are added in the order in which things happen. So it depends on the order things are clicked or changed. I could add logic so that the variables are always in the order you specify regardless of the order in which things are done. What priority should we give this issue?

@falkamelung
Copy link
Member Author

Low priority. Depends on the the risk of complications. If there is little risk you can give it higher priority.

In the example above minScale and maxScale is separates from colorscale, which does look weired as they belong together.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants