I've been using this with Ext 3.0, 3.0.1, and 3.0.2 just fine.
Yeah, it worked fine for me with 3.0+ at first, but when I started using Tooltips on a dataview that was nested in the east region of a viewport, I ran into some problems. See the screenshots below. The first one is without the override (the tooltip is positioned correctly). The second one is with the override.
It is a web mapping framework that I am working on for the National Park Service. It is called NPMap, and should be available for public consumption early next calendar year.
Well, to keep it simple, it is going to be the vehicle through which National Park Service parks, programs, etc. build and deliver maps to their users (including internal users and the general public).
It is an entire framework that allows NPS personnel to build and deploy maps and geospatial services, and it takes care of all of the heavy-lifting behind the scenes. Once an interactive map has been created within the framework, it (and the services that drive it) can be consumed in a number of different ways, including through the NPMap interface itself (which is what you see in the screenshots), through standalone and embedded maps in other web pages, and through proprietary and open source desktop GIS applications.
Not too much information. I'm always curious to see what other web apps are being developed and why.
So if I understand what you said, a park ranger or NPS employee, or just an avid hiker, could user your web app to build a map that included landmarks. Did I get that right? Does it include trails and that kind of stuff?
That is basically it, although there is a bit more going on than that. An application built in the framework can consume any type of geospatial service, including all of the OGC standards (GeoRSS, GML, KML, WFS, WMS, etc.), ArcGIS Server REST, ArcIMS, etc. So, yes, trails are definitely a part of this, as are internal management geospatial layers (for example: buildings, fuel tanks, wilderness boundaries, and culverts).
The framework is also extendable, so developers can easily write their own tools and deploy them to existing applications.
Originally Posted by charleshimmer
Reply With Quote