[Thread Prev][Thread Next][Index]

High-resolution data set issues



I have had several successes, but have also run into a few stumbling blocks in trying to serve high-resolution data sets, and am wondering if anyone has manged to work around the following two issues...

A) The server side map yields only integer values of latitude and longitude.  Some of my datasets are less than half a degree wide, so the rounding causes the server-side map to select a zero-width region, or a too-wide region (see B, below). I have just started digging into the code to find the source of this issue, but would appreciate if anyone can point out where the rounding occurs.

B) Independent of the constrain method used, selecting outside of the longitude range of a dataset winds up selecting a very wide dataset, approaching a width of 180 degrees or so.  Interestingly, this does not occur if a small dataset is overlayed on top of a larger dataset -- but does occur to the smaller dataset if the same two datasets are plotted side-by-side.  Once again, I would be willing to dig in to the code if someone has a good idea where to look.

Unfortunately, the server is behind a pretty heavy firewall, but a dedicated, public server is on its way.  Along those lines, I'd also appreciate recommendations regarding the hardware for a dedicated LAS server running large gridded (up to 1GB each) and relational databases (up to 300K records each).

Thanks!


[Thread Prev][Thread Next][Index]

Dept of Commerce / NOAA / OAR / PMEL / TMAP
Contact Us | Privacy Policy | Disclaimer | Accessibility Statement