Where data is picked view for Matlab geoserver/WMS request

[cresis]

Where data is picked view for Matlab geoserver/WMS request

[jpaden]

imb.prefwin.okPB_callback

imb.mapwin.get_map

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

[kpurdon]

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]

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:

[kpurdon]

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" [email protected] 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]

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: [phone]
Work Phone: [phone]

From: Trey Stafford [mailto:[email protected]]
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]

@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:

Black:

Orange!:

Go with black or dark grey for the default?

[treystaff]

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

[treystaff]

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]

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.