Grid viewer now has servers which are only selectable if the regions selected are chosen. Drop downs are now more based on metadata and not old quicksilver facets.
The next steps will be expanding the conditional handling, futhering the migration from a single-pane to two-panes with the top focusing on metadata and selections and the bottom focusing on the map and repeated queries.... and dealing with new servers and services and making sure all the metadata performs as expected (and probably a few paradigm shifts to allow changes in what 'expected' is).
Showing posts with label metadata. Show all posts
Showing posts with label metadata. Show all posts
Thursday, May 21, 2009
Tuesday, May 19, 2009
A few things...
I have been busy with a few things over the past couple of days:
I upgraded GridViewer and Quicksilver so that they used timers (so that one can see which proportion of waiting lies in service calls or data rendering) and had an option for plotting pinpoints instead of polygons (pinpoints being that much faster and clear-cut, polygons looking neater and showing better spatial orientation). Quicksilver also has a link to metadata for servers so you can see what data is avialable from a particular server.
Right now I am working on making grid viewer behave based on what the servers can provide, this means tailoring the lists (states, zip3s, zip5s, conditions) so that one can only select regions that a server can provide data-for, and not everything in the region-relations table or conditions properties. I am hoping to have all the regions and the conditions selecting appropriately tomorrow, that way it will become much less confusing which regions have been asked-for.
After that, more User Interface niftiness is planned. Including hover-over for metadata stats, and a server list that changes based on the selected regions and conditions, but first I want to get the service pulling back data more reliably.
Cheers!
I upgraded GridViewer and Quicksilver so that they used timers (so that one can see which proportion of waiting lies in service calls or data rendering) and had an option for plotting pinpoints instead of polygons (pinpoints being that much faster and clear-cut, polygons looking neater and showing better spatial orientation). Quicksilver also has a link to metadata for servers so you can see what data is avialable from a particular server.
Right now I am working on making grid viewer behave based on what the servers can provide, this means tailoring the lists (states, zip3s, zip5s, conditions) so that one can only select regions that a server can provide data-for, and not everything in the region-relations table or conditions properties. I am hoping to have all the regions and the conditions selecting appropriately tomorrow, that way it will become much less confusing which regions have been asked-for.
After that, more User Interface niftiness is planned. Including hover-over for metadata stats, and a server list that changes based on the selected regions and conditions, but first I want to get the service pulling back data more reliably.
Cheers!
Tuesday, April 28, 2009
Metadata Madness Continued
Today, I got the code for the metadata capture executing through tests. I also re-learned a few things.
- Quick little stubs for imitating real services are neither quick nor little, but are always necessary if data is to be provided and you want to test your structures and plans.
- Use the types your given. Creating new types because they seem a bit clearer in your mind means you have to convert them.
- Draw things out. While what you code will rarely look like what you ended up drawing... it gets that tossable first attempt out of the way without having to do a lot of SVN adjustment.
Tomorrow, I try and show the metadata in the grid-viewer pane, and then I try and replicate data.
- Quick little stubs for imitating real services are neither quick nor little, but are always necessary if data is to be provided and you want to test your structures and plans.
- Use the types your given. Creating new types because they seem a bit clearer in your mind means you have to convert them.
- Draw things out. While what you code will rarely look like what you ended up drawing... it gets that tossable first attempt out of the way without having to do a lot of SVN adjustment.
Tomorrow, I try and show the metadata in the grid-viewer pane, and then I try and replicate data.
Monday, April 27, 2009
Metadata madness.
Today, I took the first step in getting to Rodsadai-with-grid-viewer settings, setting up how all the metadata would be stored, and discussing it with other people.
For now, we have settled on storing the server names and URL's in a database, and then populating the metadata from the service(s) dynamically. Thus, most of today has been spent filling out the infrastructure for a one-time database load in gridviewer.
Brian and I also discussed how the app would behave. Instead of the Quicksilver-esque selection and then map... there will be an intro page that will probably need the real-estate formerly taken by the map to show a server-list. The given list will change depending on what date ranges, regions, and conditions are picked (based on whether or not the servers support said items) and then, after the ranges and servers are chosen, the map will be loaded and viewed. Another nifty discussed was to have metadata popups over the available servers, so people would get an idea of which limitations each server had.
Otherwise, the big next step will be integrating with the client app Vaughn is developing. It will be needed to pull the metadata for given services and set up the loading pane.
For now, we have settled on storing the server names and URL's in a database, and then populating the metadata from the service(s) dynamically. Thus, most of today has been spent filling out the infrastructure for a one-time database load in gridviewer.
Brian and I also discussed how the app would behave. Instead of the Quicksilver-esque selection and then map... there will be an intro page that will probably need the real-estate formerly taken by the map to show a server-list. The given list will change depending on what date ranges, regions, and conditions are picked (based on whether or not the servers support said items) and then, after the ranges and servers are chosen, the map will be loaded and viewed. Another nifty discussed was to have metadata popups over the available servers, so people would get an idea of which limitations each server had.
Otherwise, the big next step will be integrating with the client app Vaughn is developing. It will be needed to pull the metadata for given services and set up the loading pane.
Subscribe to:
Posts (Atom)
Posts
