-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
UTM zone cleanup #6428
Comments
@dustymc I think that UTM conversions are working now that the code table has appropriate terms, so we need to help NMMNH clean up stuff that was assigned coordinates from the UTM that was entered in data entry. My first question is - can we find all localities that were entered with UTM coordinates (as entered coordinates) that Arctos converted to decimal degrees? |
I can't seem to get the converter to work on a record bulkload. What goes into the coodinate_datum column? |
Data? Example is probably easiest. You have to sync up https://arctos.database.museum/info/ctDocumentation.cfm?table=ctutm_zone and https://arctos.database.museum/info/ctDocumentation.cfm?table=ctdatum https://arctos.database.museum/info/ctDocumentation.cfm?table=ctutm_zone#13n will ONLY work with https://arctos.database.museum/info/ctDocumentation.cfm?table=ctdatum#world_geodetic_system_1984 for example. |
They are all UTM 12N and 13N. I started with World Geodetic System 1984 in coordinate_datum and it didn't like it. |
OK, Step One is to ignore everything I just wrote because it's wrong... coordinate_datum=North American Datum 1927 It's the slash in the value that matters, not documentation. From the first row of your CSV:
|
I'm not sure I did that right, but it still didn't pass: |
Wait - I got it! I had to remove the space from 'NAD 27' |
Thanks! |
I've never had to deal with UTMS previously, but now have a dataset with recently collected UTM data. Is this something we can now easily add to and map in Arctos? |
Issue Documentation is http://handbook.arctosdb.org/how_to/How-to-Use-Issues-in-Arctos.html
Is your feature request related to a problem? Please describe.
See #5910 (comment) - some UTM zones aren't functional, and UTM and datum have a really wonky intersection
Describe what you're trying to accomplish
Make it better
Describe the solution you'd like
??
Describe alternatives you've considered
I'm up for anything...
Additional context
Priority
The text was updated successfully, but these errors were encountered: