NoPublic, bureaucrat, administrator
4,913
edits
Changes
no edit summary
</ol>
{{Note |To import geospatial data from an Excel spreadsheet, the file must:
* contain the columns in the table below
* UTM
* UTM with distance and bearing
[[Image:SampleSpreadsheetForGeospatialData.jpg|600px|center]]
</div>
<ol start="1">
<li>The selected coordinate reference system at the geospatial widget is the coordinate system for the coordinate data in the Excel input file. Please note that the ProjName column in the Excel input file is purely for manual reference and not used in the Point Editor Excel Import function.</li>
<li>When a '''Poly ID''' is provided, the coordinate data is a polygon/polyline point. Otherwise, the coordinate data is considered a '''single point'''.</li>
<li>If you would like to import geospatial data for multiple polygons/polylines, use different PolyIDs, keep the points for each shape together in the spreadsheet and begin each new shape with point number 1. The example shown below illustrates a spreadsheet which defines two polylines.</li></ol>
[[Image:SampleSpreadsheetWithDataForTwoPolylines.png|550px|center]]
<div align="center">
'' Sample Spreadsheet with Data For Two Polylines ''
</div> <ol start="3"/li>
<li>The PointNo cannot be NULL for any polygon/polyline points. If the PointNo is NULL and the coordinate is a single point, the PointNo will be set to 1.</li>
<li>The Point ID cannot be NULL, and must be unique across all points in the Excel spreadsheet and existing points in the Points table and Polygon/Polyline points table at the geospatial widget of the target object.</li>
