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

Where data is picked view for Matlab geoserver/WMS request #16

Closed
jpaden opened this issue May 7, 2014 · 9 comments
Closed

Where data is picked view for Matlab geoserver/WMS request #16

jpaden opened this issue May 7, 2014 · 9 comments

Comments

@jpaden
Copy link
Member

jpaden commented May 7, 2014

No description provided.

@jpaden
Copy link
Member Author

jpaden commented May 7, 2014

imb.prefwin.okPB_callback

imb.mapwin.get_map

imb.mapwin.query_redraw_map
probably don't need this one

@kpurdon kpurdon added this to the OPS2 RELEASE 2 milestone May 7, 2014
@kpurdon
Copy link
Contributor

kpurdon commented May 14, 2014

the styling would be best to show un-picked as a muted (grey) color and picked as the standard blue. This would be valuable soon I think... changing to OPS2 RELEASE 1

@treystaff
Copy link
Contributor

A muted grey color for un-picked areas does not stand out very well. If we want to highlight areas that are not yet picked, a color that stands out might be more appropriate.

An example with grey areas representing unpicked bed:
coverage_flightlines

@kpurdon
Copy link
Contributor

kpurdon commented May 26, 2014

I was thinking more of a charcoal (almost black). However if we need to go
red or something like that it would probably be fine.
On May 26, 2014 12:27 PM, "Trey Stafford" notifications@github.com wrote:

A muted grey color for un-picked areas does not stand out very well. If we
want to highlight areas that are not yet picked, a color that stands out
might be more appropriate.

An example with grey areas representing unpicked bed:
[image: coverage_flightlines]https://cloud.githubusercontent.com/assets/6741257/3084579/e85ac97e-e4fa-11e3-8f2c-003b10a2e651.png


Reply to this email directly or view it on GitHubhttps://github.com//issues/16#issuecomment-44206132
.

@jpaden
Copy link
Member Author

jpaden commented May 26, 2014

Is the color configurable from the client? Although I think charcoal would be good too.

John Paden
Center for Remote Sensing of Ice Sheets (CReSIS)
Nichols Hall, Room 325
2335 Irving Hill Rd
Lawrence, KS 66045
USA
Cell Phone: (303) 818-6406
Work Phone: (785) 864-1692

From: Trey Stafford [mailto:notifications@github.com]
Sent: May 26, 2014 12:27 PM
To: CReSIS/OPS
Cc: Paden, John D.
Subject: Re: [OPS] Where data is picked view for Matlab geoserver/WMS request (#16)

A muted grey color for un-picked areas does not stand out very well. If we want to highlight areas that are not yet picked, a color that stands out might be more appropriate.

An example with grey areas representing unpicked bed:
[coverage_flightlines]https://cloud.githubusercontent.com/assets/6741257/3084579/e85ac97e-e4fa-11e3-8f2c-003b10a2e651.png


Reply to this email directly or view it on GitHubhttps://github.com//issues/16#issuecomment-44206132.

@treystaff
Copy link
Contributor

@jpaden
Color can be configured from the client, but we will have to set up a predefined set of colors first. Not difficult to do.

Here are some example colors:
Grey:
coverage_flightlines_grey

Black:
coverage_flightlines_black

Orange!:
coverage_flightlines_colorful

Go with black or dark grey for the default?

@treystaff
Copy link
Contributor

Data quality and coverage layers added to geoserver. (54cb1c0). Speed improvement necessary to make feasible in OPS2 (possibly improved w/ issue #62)

@wliu58i5ki wliu58i5ki assigned wliu58i5ki and unassigned treystaff and wliu58i5ki Jun 27, 2014
@treystaff
Copy link
Contributor

I think the only way to go forward with this is to limit this layer to zoomed-in areas. This functionality can be added to the Data Coverage SLD.

@treystaff
Copy link
Contributor

A MaxScaleDenominator around 1000000 seems like the right area to start showing layers like data coverage and data quality flight lines:

<MaxScaleDenominator>1000000</MaxScaleDenominator>

Nevertheless, loading these layers is still slow (6-7 seconds). Further optimizations will likely be necessary.

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

4 participants