I'm trying to use the NCAT tool to convert a bunch of lat/long positions to SPC, but I keep getting an "invalid content" error. I'm using the Multipoint Conversion tab, and uploading the records as a .csv file.?ÿ Anyone care to check my format??ÿ
Here's the content of a small subset of the records that generate the error:
ID,lat,lon,eht,inDatum,outDatum,spcZone,utmZone
18,38.3784824,-121.6916048,N/A,NAD83(2011),NAD83(2011),auto,auto
74,38.4757034,-121.6466429,N/A,NAD83(2011),NAD83(2011),auto,auto
Thanks!
Have you tried Corpscon?
Jim,
I have the same problem (error) every time I use NCAT. I always figure it out (some innocuous and/or semi-invisible formatting issue), but it drives me nuts. I never use NCAT for "simple" LL to SPC/UTM conversions (same datum/realization) because I have other FAR LESS troublesome software options.
Good Luck, and let us know what you figure out (so I can print it out and use it next time I'm forced to use NCAT).
Loyal?ÿ?ÿ
@jim-frame Are you using the released or beta version? Your coordinates just worked for me using the beta version. I did get a warning/error about 1 untransformed point which may have been the "header" line.
I had a problem with an earlier version of NCAT--probably it was GEOCON actually. I couldn't get any of the sample coordinate formats from the help to work. I sent off a sample and there was a bug.?ÿ
I tried the beta version, but get a similar (maybe the same) error message.?ÿ I can convert individual coordinates on the interactive page, but I haven't figured out how to get the file conversion to work.?ÿ 🙁
Assuming that an NGS sample file should work in an NGS program, I copied and pasted the NCAT sample input into a Google Docs file, downloaded it as a text file, and submitted it to NCAT.?ÿ
It worked fine, so I appended Jim's data to it and submitted it again. Again, it worked fine.
What my file didn't have was Jim's heading and Jim's format (.csv), so perhaps the problem is in one of those two items. The NCAT output is attached.
?ÿ
Following Math Teacher's lead, I took the NGS sample data -- including the header line -- put it in a text file and ran it successfully through NCAT.?ÿ Then I appended my data (all 96 lines), and ran the file again, and it worked again.?ÿ I can't offer an explanation for the fact that my data won't run by itself.
I just pasted the three lines, including heading into a text file and uploaded it to NCAT. The file did not include the NGS sample data.
It processed without a hitch. Perhaps there's something about a .CSV file that NCAT doesn't like.
I also found that if the lats & longs were expressed to 8 decimal places, NCAT choked at the upload stage.?ÿ 7 decimal places worked okay.
The first latitude in the sample file, for Id TU2083, has 10 decimal places while the longitude in the last example, EFGH, has only one decimal place, so there may be some other issue somewhere.
NCAT may take some getting used to, but it may be nice to have so much capability in one place.
?ÿ
Hopefully humorous related topic xkcd cartoon (xkcd.com) Enjoy.?ÿ
Now if only everyone could think like an NGS-er...
I ran into what I think is another problem:?ÿ file size.?ÿ I get a file size error on uploading anything bigger than about 260k.?ÿ (As I recall, 256k worked, but 500k didn't.)?ÿ And I still can't get a file recognized unless I prepend the sample data, which continues to mystify me.