1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250
|
/*=========================================================================
Program: ORFEO Toolbox
Language: C++
Date: $Date$
Version: $Revision$
Copyright (c) Centre National d'Etudes Spatiales. All rights reserved.
See OTBCopyright.txt for details.
This software is distributed WITHOUT ANY WARRANTY; without even
the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE. See the above copyright notices for more information.
=========================================================================*/
// Software Guide : BeginLatex
//
// Unfortunately, many vector data formats do not
// share the models for the data they represent. However, in some
// cases, when simple data is stored, it can be decomposed in simple
// objects as for instance polylines, polygons and points. This is
// the case for the Shapefile and the KML (Keyhole Markup Language) formats,
// for instance.
//
// Even though specific reader/writer for Shapefile and the Google KML
// are available in OTB, we designed a generic approach for the IO of
// this kind of data.
// The reader/writer for VectorData in OTB is able to access a variety of
// vector file formats (all OGR supported formats)
//
// In section \ref{sec:VectorDataProjection}, you will find more information on
// how projections work for the vector data and how you can export
// the results obtained with OTB to the real world.
//
// This example illustrates the use of OTB's vector data IO
// framework.
//
// We will start by including the header files for the classes
// describing the vector data and the corresponding reader and writer.
//
// Software Guide : EndLatex
// Software Guide : BeginCodeSnippet
#include "otbVectorData.h"
#include "otbVectorDataFileReader.h"
#include "otbVectorDataFileWriter.h"
// Software Guide : EndCodeSnippet
// Software Guide : BeginLatex
//
// We will also need to include the header files for the classes
// which model the individual objects that we get from the vector
// data structure.
//
// Software Guide : EndLatex
// Software Guide : BeginCodeSnippet
#include "itkPreOrderTreeIterator.h"
#include "otbObjectList.h"
#include "otbPolygon.h"
// Software Guide : EndCodeSnippet
int main(int argc, char * argv[])
{
if (argc != 3)
{
std::cerr << "Usage: " << argv[0];
std::cerr << "inputFile outputFile" << std::endl;
return EXIT_FAILURE;
}
typedef unsigned short int PixelType;
// Software Guide : BeginLatex
//
// We define the types for the vector data structure and the
// corresponding file reader.
//
// Software Guide : EndLatex
// Software Guide : BeginCodeSnippet
typedef otb::VectorData<PixelType, 2> VectorDataType;
typedef otb::VectorDataFileReader<VectorDataType>
VectorDataFileReaderType;
// Software Guide : EndCodeSnippet
// Software Guide : BeginLatex
//
// We can now instantiate the reader and read the data.
//
// Software Guide : EndLatex
// Software Guide : BeginCodeSnippet
VectorDataFileReaderType::Pointer reader = VectorDataFileReaderType::New();
reader->SetFileName(argv[1]);
reader->Update();
// Software Guide : EndCodeSnippet
// Software Guide : BeginLatex
//
// The vector data obtained from the reader will provide a tree of
// nodes containing the actual objects of the scene. This tree will
// be accessed using an \doxygen{itk}{PreOrderTreeIterator}.
//
// Software Guide : EndLatex
// Software Guide : BeginCodeSnippet
typedef VectorDataType::DataTreeType DataTreeType;
typedef itk::PreOrderTreeIterator<DataTreeType> TreeIteratorType;
// Software Guide : EndCodeSnippet
// Software Guide : BeginLatex
//
// In this example we will only read polygon objects from the input
// file before writing them to the output file. We define the type
// for the polygon object as well as an iterator to the vertices. The
// polygons obtained will be stored in an \doxygen{otb}{ObjectList}.
//
// Software Guide : EndLatex
// Software Guide : BeginCodeSnippet
typedef otb::Polygon<double> PolygonType;
typedef otb::ObjectList<PolygonType> PolygonListType;
PolygonListType::Pointer polygonList = PolygonListType::New();
// Software Guide : EndCodeSnippet
// Software Guide : BeginLatex
//
// We get the data tree and instantiate an iterator to walk through it.
//
// Software Guide : EndLatex
// Software Guide : BeginCodeSnippet
TreeIteratorType it(reader->GetOutput()->GetDataTree());
it.GoToBegin();
// Software Guide : EndCodeSnippet
// Software Guide : BeginLatex
//
// We check that the current object is a polygon using the
// \code{IsPolygonFeature()} method and get its exterior ring in
// order to store it into the list.
//
// Software Guide : EndLatex
// Software Guide : BeginCodeSnippet
while (!it.IsAtEnd())
{
if (it.Get()->IsPolygonFeature())
{
polygonList->PushBack(it.Get()->GetPolygonExteriorRing());
}
++it;
}
// Software Guide : EndCodeSnippet
polygonList->PushBack(PolygonType::New());
// Software Guide : BeginLatex
//
// Before writing the polygons to the output file, we have to build
// the vector data structure. This structure will be built up of
// nodes. We define the types needed for that.
//
// Software Guide : EndLatex
// Software Guide : BeginCodeSnippet
VectorDataType::Pointer outVectorData = VectorDataType::New();
typedef VectorDataType::DataNodeType DataNodeType;
// Software Guide : EndCodeSnippet
// Software Guide : BeginLatex
//
// We fill the data structure with the nodes. The root node is a
// document which is composed of folders. A list of polygons can be
// seen as a multi polygon object.
//
// Software Guide : EndLatex
// Software Guide : BeginCodeSnippet
DataNodeType::Pointer document = DataNodeType::New();
document->SetNodeType(otb::DOCUMENT);
document->SetNodeId("polygon");
DataNodeType::Pointer folder = DataNodeType::New();
folder->SetNodeType(otb::FOLDER);
DataNodeType::Pointer multiPolygon = DataNodeType::New();
multiPolygon->SetNodeType(otb::FEATURE_MULTIPOLYGON);
// Software Guide : EndCodeSnippet
// Software Guide : BeginLatex
//
// We assign these objects to the data tree stored by the vector data object.
//
// Software Guide : EndLatex
// Software Guide : BeginCodeSnippet
DataTreeType::Pointer tree = outVectorData->GetDataTree();
DataNodeType::Pointer root = tree->GetRoot()->Get();
tree->Add(document, root);
tree->Add(folder, document);
tree->Add(multiPolygon, folder);
// Software Guide : EndCodeSnippet
// Software Guide : BeginLatex
//
// We can now iterate through the polygon list and fill the vector
// data structure.
//
// Software Guide : EndLatex
// Software Guide : BeginCodeSnippet
for (PolygonListType::Iterator pit = polygonList->Begin();
pit != polygonList->End(); ++pit)
{
DataNodeType::Pointer newPolygon = DataNodeType::New();
newPolygon->SetPolygonExteriorRing(pit.Get());
tree->Add(newPolygon, multiPolygon);
}
// Software Guide : EndCodeSnippet
// Software Guide : BeginLatex
//
// And finally we write the vector data to a file using a generic
// \doxygen{otb}{VectorDataFileWriter}.
//
// Software Guide : EndLatex
// Software Guide : BeginCodeSnippet
typedef otb::VectorDataFileWriter<VectorDataType> WriterType;
WriterType::Pointer writer = WriterType::New();
writer->SetInput(outVectorData);
writer->SetFileName(argv[2]);
writer->Update();
// Software Guide : EndCodeSnippet
return EXIT_SUCCESS;
// Software Guide : BeginLatex
//
// This example can convert an ESRI Shapefile to
// a MapInfo File but you can also access with the same OTB source code
// to a PostgreSQL datasource, using a connection string as :
// PG:"dbname='databasename' host='addr' port='5432' user='x' password='y'"
// Starting with GDAL 1.6.0, the set of tables to be scanned can be overridden
// by specifying tables=schema.table.
// Software Guide : EndLatex
}
|