New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EPSG 6512 is labeled US Feet but returns meters #160
Comments
Definitely looks like PROJ.4 & EPSG thinks it should be meters.
According to https://epsg.io/6512, it says meters as well. If you want it to be feet, replace "units=m" with "units=us-ft".
This would be the solution:
But, not necessarily the one you want. It would require some code logic on your end to handle edge cases. |
Thanks! Is there anywhere in my downloaded package code that I can edit that. I'm not finding it in a text search. |
In the EPSG database table "coordinatereferencesystem" 6511, 6512 & 6513 are the only Missouri zones using NAD83(2011) but there is no notation for units. That must have then triggered using a default setting of meters, but our contract specifies US survey feet. Specifications |
I would recommend just handling it in the code in your package. Have a special case for the EPSG codes of interest. The units |
I am going to mark this as resolved. Feel free to reopen if needed. |
I'm working on an airport in Missouri East NAD83(2011) Us Ft [6512]
state plane should be East = 969167.470 North = 278826.850 as calculated by CorpsCon
but with pyproj & at EPSG website I get {'East': 295430.2841388423, 'North': 85247.59598697856}
Going from state plane to geo puts me in West Virginia instead of southeast Missouri, preventing me from doing a Lat/Lon search for nearby points in a reference table
I am using "preserve_units" My code has given accurate results in other projection zones.
def sp2geo(epsg_id,easting,northing):
inProj = Proj(init='epsg:%s' % epsg_id, preserve_units=True)
outProj = Proj(init='epsg:%s' % latlon_id)
rec = {}
rec['Lon'],rec['Lat'] = transform(inProj,outProj,easting,northing)
return rec
The text was updated successfully, but these errors were encountered: