July 26, 2012
NPMap is two separate, but complementary, things:
To make it as easy as possible for the National Park Service to build and deploy simple and beautiful web maps.
|
David Warren Data Manager |
Mamata Akella Cartographer |
Nate Irwin Developer & Lead |
We work like a contract shop, helping our NPS partners create and deploy web maps. All of the code we write is open and available* for others to use. You can find all kinds of information about what we do on our website: http://www.nps.gov/npmap.
* Nothing is publicly-available on our GitHub account yet, but we are working on open sourcing our code. If you work for the NPS and want the code now, shoot us an email.
This example is only available when you're connected to the NPS network.
Abstracts commonly-used functionality away from various web mapping APIs and wraps it with an API and a look-and-feel that is specific to the National Park Service.
<!DOCTYPE html>
<html>
<head>
</head>
<body>
<div id="example-map">
</div>
<script>
var NPMap = NPMap || {};
NPMap.config = {
api: 'leaflet',
div: 'example-map'
};
(function() {
var s = document.createElement('script');
s.src = 'http://www.nps.gov/npmap/0.8.0/bootstrap.js';
s.type = 'text/javascript';
document.body.appendChild(s);
})();
</script>
</body>
</html>
Why did we decide to build our own library?
Enterprise license agreements we work on:
We are working with a design firm to develop a custom set of tools and components for the NPMap library. These components have been designed to fit into the graphic identity of the National Park Service.
The upcoming 0.8.0 release of NPMap will include these new components.
Other things to look out for: