Presentation is loading. Please wait.

Presentation is loading. Please wait.

Spatial Allocation  Philosophy  Tools  Design  Standard reports  Questions.

Similar presentations

Presentation on theme: "Spatial Allocation  Philosophy  Tools  Design  Standard reports  Questions."— Presentation transcript:

1 Spatial Allocation  Philosophy  Tools  Design  Standard reports  Questions

2 Spatial Allocation (Philosophy)  Design for only the necessary functions  Perform a computational intersection of point, arc, or polygon structures within a polygon structure  Create arbitrary emissions modeling grid structures  Manage and display underlying maps and spatial attributes  Covert among various, common map projections.  Use off-the-shelf shareware/freeware tools  Do not reinvent  Provide hooks for future enhancements  Scope creep will kill this aspect of the project  Bottom-line: take the minimalist approach

3 Spatial Allocation (Tools)  PostgreSQL --  GNU make –  GNU readline –  Ant –  JAVA –  Perl –  PostGIS --  shp2pgsql – ARC shape files to SQL insert constructs  e00ps – ARC export files to SQL insert constructs –  special converters to import BELD3 data will be constructed  MIMS Spatial Allocator --  Java-enabled Unified Mapping Platform (JUMP) --  PostGIS JUMP driver –

4 Spatial Allocation (Design)

5 Spatial Allocation (JUMP)

6 Spatial Allocation (Standard Reports)  Map of domain with grid structure overlay  Maps of individual coverages in native and projected coordinates  Gridded maps of BELD3 by species  Gridded maps of individual surrogate fractions  Gridded map of point source locations

7 Spatial Allocation (Questions)  ARC shape and export files  Shape converter is stable  Export converter may not be so stable (ESRI considers the export format to be proprietary; hence, the converter is based on a reverse engineering approach – the web gossip seems to indicate that it works fine)  Datum in conjunction with non-datum coverages – very difficult to implement (i.e., easiest to use either all datum-based coverages or nondatum-based coverages)  MIMS Spatial Allocator  No need for special C-compiler (GNU C or host C should work fine)  No special license requirements  Noted problems with memory leaks; problems with large (<200 MB) coverages  Special map projections  Standard map projections definitely supported (Lambert Conformal, UTM, geographic, Polar Stereographic)  Special map projections not supported (stateplane [these are specialized projections of standard map projections] e.g. Lambert, transverse, oblique mercator)

8 Spatial Allocation (Questions – continued)  Geographic Resources Analysis Support System (GRASS)   Relatively large overhead (150 MB)  Robust GIS  Use will require new coding to build MIMS functionality  Other shareware/freeware GIS tools  PostGIS itself provides basic GIS functionality  Geometry Engine - Open Source (GEOS) –  Java Topology Suite (JTS) –  Will need to be coupled to map projection system like Cartographic Projections Library PROJ.4 (  These systems provide basic GIS functionality but will require coding to recreate MIMS Spatial Allocator functionality

9  What if any special processing needs to be considered for identifying data associated to tribal lands when the base data (e.g., BELD3) has no such information?  Any such pre- or in-line-processing of the data and the ability of the project team to incorporate such a capability in OPEM has resource implications (i.e., the project team believes that this is an enhancement we can live without at this time) Spatial Allocation (Questions – continued)

Download ppt "Spatial Allocation  Philosophy  Tools  Design  Standard reports  Questions."

Similar presentations

Ads by Google