Re: [gdal-dev] Unable to find various object files for GEOS and ogrsqlitedatasource

I think the issue was enabling geos support in the configure process but not passing it the directory for geos_config. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Unable-to-find-various-object-files-for-GEOS-and-ogrsqlitedatasource-tp5196680p5200064.html Sent from the G

[gdal-dev] Unable to find various object files for GEOS and ogrsqlitedatasource

I've built gdal with geos, sqlite3 and spatialite support, however when I debug my program I am seeing various warnings such as: warning: Could not find object file ".../geos-3.4.2/src/.libs/libgeos.lax/liboperation.a/SubgraphDepthLocater.o" - no debug information available for "SubgraphDepthLo

Re: [gdal-dev] GDAL C++ Api, create new line segments from point layer

Jukka, I've not done anything useful with routing either, so I'm sure once I solve my issue, I'll immediately realize a simpler way to do it. Your segmenting the lines has given me an idea that is similar: Add the points into the linestrings. I think if I do this I can then more easily create line

Re: [gdal-dev] GDAL C++ Api, create new line segments from point layer

Jukka, THanks for the suggestions. THe green points are the decision points, so I need to use those in my pathing. For instance, I would choose one of those points and then choose another green point as the destination to get the route(s). -- View this message in context: http://osgeo-org.1560

Re: [gdal-dev] GDAL C++ Api, create new line segments from point layer

Jukka Rahkonen wrote > Hi, > > Could you make a drawing about what you have and what you want to get? > > If your aim is to cut long linestrings only where they intersect with > points > from the point layer I believe that it is not easy with plain GDAL. There > are some useful functions in the S

Re: [gdal-dev] GDAL C++ Api, create new line segments from point layer

Matt Hanson-2 wrote > So you've got a series of points in your point layer, and a series of > lines > in your line layer, and for each point on your points layer, you want to > find out which line this falls on. --I'm able to do this already. Matt Hanson-2 wrote > Is that right? It sounds like

Re: [gdal-dev] GDAL C++ Api, create new line segments from point layer

Matt, I've got a line layer and a points layer. The points layer fall on the line layer, however they are not end points on the line layer, for the most part. I'm not sure if that answers your question or not. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/GDAL-C-Api-cre

Re: [gdal-dev] GDAL C++ Api, create new line segments from point layer

Yes, I've experimented with that library and actually asked a follow up question here about it. To properly use it, I need to prepare the layer in the manner I am asking about. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/GDAL-C-Api-create-new-line-segments-from-point-la

Re: [gdal-dev] GDAL C++ Api, create new line segments from point layer

Would GEOS be a more appropriate library to use? GDAL was my goto due to familiarity. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/GDAL-C-Api-create-new-line-segments-from-point-layer-tp5195061p5195070.html Sent from the GDAL - Dev mailing list archive at Nabble.com. ___

[gdal-dev] GDAL C++ Api, create new line segments from point layer

I am trying to create a pathfinding graph from a shapefile with a line layer and point layer. Using the C++ API, for each point in the points layer, I need to find the next N points that are connected to that point along one or more OGRLineStrings. I've been able to determine which OGRLineString

Re: [gdal-dev] GNM Usage

Thanks for the response. The source data is in EPSG 900913, the network data according to ogrinfo: PROJCS["WGS_84_Pseudo_Mercator", GEOGCS["GCS_WGS_1984", DATUM["WGS_1984", SPHEROID["WGS_84",6378137,298.257223563]], PRIMEM["Greenwich",0], UNIT["Degree",0.0174

Re: [gdal-dev] GNM Usage

Looking at the _gnm_graph table, I think that is the issue. THere are some connections, but only 8 out of ~300 points. Is it required that the points layer be on the end of a line? The points layer I have are on top of the lines, however a single line may have multiple points along its length. Dan

Re: [gdal-dev] GNM Usage

Thanks for the info! -- View this message in context: http://osgeo-org.1560.x6.nabble.com/GNM-Usage-tp5192401p5192776.html Sent from the GDAL - Dev mailing list archive at Nabble.com. ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osg

Re: [gdal-dev] GNM Usage

One thing when building the network I did not do was use CreateRule to add costs to paths as this does not make sense in my use case. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/GNM-Usage-tp5192401p5192408.html Sent from the GDAL - Dev mailing list archive at Nabble.com

[gdal-dev] GNM Usage

I'm trying to use the GNM API to create a graph of a line layer and point layer. I assume I successfully build the network as I have the shapefiles output in the directory. When I try to find a path between 2 GFID's, I always get the void layer(no path found). I am not certain, but the GFIDs I am

[gdal-dev] Re: Compile error with --with-python

I grabbed the gdal-1.6.3.tar.gz release and ran through the make with no issues. Perhaps something has changed in the latest release make scripts somewhere? Dan -- View this message in context: http://n2.nabble.com/Compile-error-with-with-python-tp4669408p4674203.html Sent from the GDAL -

[gdal-dev] Re: Compile error with --with-python

Another odd thing I see is if I "make" a second time without making any changes, I don't get any errors. It basically runs through all the directories, when it gets to the swig area I see " `build' is up to date." Dan -- View this message in context: http://n2.nabble.com/Compile-error-with-with

[gdal-dev] Compile error with --with-python

I am seeing a very odd build error that seems to be happening in the swig/python area. For some reason on a "-L" options the directory name is getting spaces between every character: compile options: '-I../../port -I../../gcore -I../../alg -I../../ogr/ -I/usr/include/python2.5 -I/usr/lib/python2.