Collimatedflashlight

Thank you for this post Scott Drzyzga‌. This problem was brought to the development team a few weeks ago and has been fixed in ArcGIS Pro 2.6 (it will be in the early adopter snapshot of ArcGIS Pro 2.6, or the public beta available in a few months if you would want to participate). For the 2.5.x release you will need to perform the additional step you explained with the Project (management) tool.

Collimate telescope

Our 10x laser collimator is optimized specifically for low wavefront distortion and diffraction limited performance at infinity focus in the visible wavelength region. The Galilean optical system is antireflection coated with visible MgF2 for maximum transmission.

on pro 2.9 i have got some issues too with this tool. The parameter of the tool "coordinate system" goes suddendly wrong without any manual update on the stuff.

A flat mirror reflects the expanded beam back through the optical system, demagnifying it. Adjust the collimator until the reflected beam observed at A is a minimum diameter.

Laser collimatedbeam

Choose products to compare anywhere you see 'Add to Compare' or 'Compare' options displayed. Compare All Close

Thank you for this post Scott Drzyzga‌. This problem was brought to the development team a few weeks ago and has been fixed in ArcGIS Pro 2.6 (it will be in the early adopter snapshot of ArcGIS Pro 2.6, or the public beta available in a few months if you would want to participate). For the 2.5.x release you will need to perform the additional step you explained with the Project (management) tool.

Collimation radiology

I have three (3) CSV formatted files containing geographic coordinates (I attached one).  When I use XY Table to Point to create point features from any of them, I cannot get valid results if I set both the input SRS and the output SRS (via the Environment settings). In my case, the input SRS is WGS84; the desired output SRS is NAD83-2011 State Plane CA-II (0402).

Our 10x laser collimator is optimized specifically for low wavefront distortion and diffraction limited performance at infinity focus in the visible wavelength region. The Galilean optical system is antireflection coated with visible MgF2 for maximum transmission.

Yes, opt-in.  By checking this box, you agree to receive our newsletters, announcements, surveys and marketing offers in accordance with our privacy policy

The XY Table to Point tool does create points, but it misinterprets the desired output SRS as the defined input SRS and, so, plots all the points near the false origin of the CA-II coordinate system (i.e., out in the Pacific Ocean).

Collimating lens

The ULM-TILT adjustable cylindrical device mount is excellent for mounting and positioning the LC-075 in any laser beam. You can also use our M1-VG kinematic v-groove mount for mounting to an optical post or VB-1 fixed v-groove mount for mounting to an optical pedestal or directly on the optical table.

Strangely... I read that help topic that the default output coordinate system is WGS84, BUT if the "Input" coordinate is not that, then you need to specify it first.  It doesn't say anything about projecting the data to your desired coordinate system.

BUG-000129406: The resulting feature class is missing some of the a..   but a suggestion to make a table in a gdb makes other issues go away

Collimatedbeam

The help is incomplete then.  They appear to be relying on the supporting "Output coordinate system" as set in the Environments tab (my bad... forgot to check it too).

The ULM-TILT adjustable cylindrical device mount is excellent for mounting and positioning the LC-075 in any laser beam. You can also use our M1-VG kinematic v-groove mount for mounting to an optical post or VB-1 fixed v-groove mount for mounting to an optical pedestal or directly on the optical table.

I now have to use a two-step process to accomplish what used to be a one-step process: 1) use XY Table to Point to create point features tied to the input SRS; then 2) use the Project tool to handle the coordinate conversion.

Dan, this is a workflow I've been using for years that is now generating unexpected behavior.  I did specify both the input and the output SRS (see the figures in my post).  The error literally occurs when I specify both (as one should if the desired output is different from the input).  The reason I am posting is because this error did not occur in prior versions of ArcGIS Pro and is occurring now.