Opened 15 years ago
Closed 9 years ago
#2367 closed defect (wontfix)
GDAL VB6 Bindings - ImportFromEPSG
| Reported by: | twdotson | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | default | Version: | 1.5.1 |
| Severity: | minor | Keywords: | |
| Cc: |
Description
Original Problem: I can't seem to get ImportFromEPSG to work. I have set the appropriate paths and gdaltransform.exe seems to work correctly using EPSG numbers.
The response in an email from Frank Warmerdam was:
Could you change this definition in OGRSpatialReference.cls:
Public Declare Function OSRImportFromEPSG _
Lib "gdal12.dll" _ Alias "_OSRImportFromEPSG@8" _ (ByVal Handle As Long, EPSGCode As Long) As Long
to:
Public Declare Function OSRImportFromEPSG _
Lib "gdal12.dll" _ Alias "_OSRImportFromEPSG@8" _ (ByVal Handle As Long, ByVal EPSGCode As Long) As Long
If this fixes the problem, please file a ticket on the issue in the GDAL/OGR Trac and I'll apply the fix in the main code base.
This appears to have fixed the problem and should be added to the VB6 Bindings code.
Extended support for Visual Basic 6.0 ended in March 2008. The latest commit to VB6 binding in /gdal/browser/trunk/gdal/vb6 is from 8 years ago. There is a good reason to believe that this issue won't fix.