Fred,
You may need to use -f with the Code from this page:
http://gdal.org/ogr/ogr_formats.html (-f MSSQLSpatial)
HTH, Eli
On Wed, Nov 16, 2011 at 4:21 PM, Fred Jones wrote:
> Hi Sig,
>
> This is the command I have so far. When I execute it, I just get the help
> returned, no error and n
On 16 November 2011 15:52, mrym wrote:
> Thanks, i've done all of the things you wrote,but i'm still can't debug..
My palantír has broken, I can't help.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Member of ACCU, http://accu.org
_
Hi Sig,
This is the command I have so far. When I execute it, I just get the help
returned, no error and no table created:
ogr2ogr -overwrite -s_srs EPSG:32100 -t_srs EPSG:4326 -f
"MSSQL:server=ELMER;database=CENSUS_2010;trusted_connection=yes"
"MSSQL:server=ELMER;database=HT_2010_10;tables=temp_
Etienne,
>
> It seems that setting source srs is needed when using shapefiles, as
> you said. This should be documented somewhere (probably on the
> ogr2ogr page and/or shapefile driver page).
Feel free to add a warning. Logically, this should be more in the shapefile
driver page. But this ass
> > Since FwTools is not maintained, I think the FwTools paragraph on the
> > page http://trac.osgeo.org/gdal/wiki/DownloadingGdalBinaries should be
> > removed, or at least put at the bottom of the page. Presently, it is
> > misleading.
>
> If a reader hangs on reading until the second paragraph,
OK I think I've solved this -
I've managed to find the code that does the search and I need to call
my dll ogr_xxx.dll not gdal_xxx.dll. OGR_DRIVER_PATH and
GDAL_DRIVER_PATH are searched in that order.
Ian
--
Ian Turton
___
gdal-dev mailing list
gdal-d
On 16 November 2011 15:44, Howard Butler wrote:
>
> On Nov 16, 2011, at 9:42 AM, Ian Turton wrote:
>
>> I've been developing an OGR format to read in my employers' file
>> format. All works fine when I build the new format in directly but it
>> would probably make sense to provide the code as a pl
Thanks, i've done all of the things you wrote,but i'm still can't debug..
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/can-not-debug-gdal1-8-1-at-visual-studio-2008-tp7000116p7000821.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.
_
On Nov 16, 2011, at 9:42 AM, Ian Turton wrote:
> I've been developing an OGR format to read in my employers' file
> format. All works fine when I build the new format in directly but it
> would probably make sense to provide the code as a plugin rather than
> having to build and link our own dll'
I've been developing an OGR format to read in my employers' file
format. All works fine when I build the new format in directly but it
would probably make sense to provide the code as a plugin rather than
having to build and link our own dll's for the whole library. So I
followed the instructions a
2011/11/16 Mateusz Łoskot :
> 4) Check if GDAL links against Debug C/C++ Run-Tim
>
> dumpbin /ALL python32_d.dll | find /i "msvcr"
Obviously, I made mistake when copying this from my .bat script.
It should read:
dumpbin /ALL gdal18.dll | find /i "msvcr"
--
Mateusz Loskot, http://mateusz.loskot.
On 16 November 2011 15:02, mrym wrote:
> Ok. i see this message too "gdal18.dll, Binary was not built with debug
> information." i've replaced /MD with /MDd in flags for debug and build gdal
> again, but i still cannot debug gdal functions.
1) Not build but rebuild GDAL with correct flags
OPTFLA
Ok. i see this message too "gdal18.dll, Binary was not built with debug
information." i've replaced /MD with /MDd in flags for debug and build gdal
again, but i still cannot debug gdal functions. and i don't know what to
do..:(
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.c
Sorry, that should really be, "If you can't step into gdal functions
at all, then the cause is something besides that message."
What happens when you try to step into a gdal function?
Are you statically linking (gdal.lib) or dynamically linking
(gdal_i.lib + gdal18.dll)?
If you're using the gdal
The message you're seeing is because Microsoft doesn't include debug
information for their ODBC driver. This should not prevent you from
debugging entirely, it should just mean that you can't step into ODBC
function calls. If you can't debug at all, then the cause is almost
certainly something besi
Hi,
i've downloaded gdal1.8.1 and builded it with
nmake /f makefile.vc DEBUG=1
nmake /f makefile.vc install
nmake /f makefile.vc devinstall
everything was fine till trying to debug gdal functions. i can't debug any
gdal function. i tried lots of thing(in fact everything in google) to fix
it, but
On 16 November 2011 08:31, Jean-Claude Repetto wrote:
> Le 16/11/2011 04:48, Chaitanya kumar CH a écrit :
>>
>> Chris,
>>
>> FWTools for Windows had not been maintained for quite a while. But the
>> Intersection() function should work with the latest. It uses gdal1.5
>
> Hi,
>
> Since FwTools is n
Hi Fred,
first of all check if there is an EPSG entry for your coordinate system.
Googlin' "Montana State Plane NAD 27 EPSG" pointed me to the several
pages, among with, for example:
http://www.eye4software.com/resources/stateplane/
which states:
2500 NAD83 / Montana 32100
So the EPSG code you
Le 16/11/2011 04:48, Chaitanya kumar CH a écrit :
Chris,
FWTools for Windows had not been maintained for quite a while. But the
Intersection() function should work with the latest. It uses gdal1.5
Hi,
Since FwTools is not maintained, I think the FwTools paragraph on the
page http://trac.osge
19 matches
Mail list logo
