![]() And for mapping the surface of a sphere to a plane there are many alternatives, each of them having their specific advantages and disadvantages. What you are looking for is a so-called projection. I just read that the minutes and seconds are divided in 90 Units not in 60 as I was supposing. If you want to do it anyways, the only thing you have to do is to add the seconds to the formula. 360*2 = 720 and 720>640 so you are already not going to be able to accurately represent points in less than 35 or 40 Minutes scale. In 640x480 Resolution of display, you are not going to have any difference considering the seconds or not. The minus (-) in Y is because North coordinates are positive, but you need to decrease the pixels to go upwards because the Pixel (0,0) is in the upper-left corner. I consider the format of your 2nd comment (Positive to north and east). Since you mentioned that you want it in a sort of 3d cylinder then you can use the principle of solution 2 and apply part of my "thinking" to make the scales adapting it to your view-model. So that 179° and 89' = the border of the screen. If you consider the world as a 2d Map, the point of Latitude=0☀' and Longitude=0☀' is your X=0, Y=0, which is in the center of the display Pixel=(340,240) ![]() Your display is quite small (640,480) so the resolution is not going to be so accurated anyways. I am supposing that you don't need the Z-Axis Probably this is not going to be the best approach as well but. ![]() Note that if you have trouble all of these steps are covered at one question or another here, so you should be able to find more info on a particular step/process by searching on terms here.I had deleted the solution because I thought it was not "professional", but seeing your comments to other questions. ![]() Once that's done, you can export the attribute table back out to a csv and you'll have your coordinate values in both CRSs. Calc each of the two or four fields you need. To get the lat/long coordinates, you'd choose dataframe. If calculating the original TM65 coordinates, you'd choose the data. You'll be able to choose the X or Y coordinate of a point at the top as well as choose either the CRS of the data or the dataframe. With that done, to get the coordinate values, right-click a field heading in the attribute table and choose Calculate Geometry. Note there is some discussion at this question regarding transformations from TM65 that may influence your decision. You'll need to click the that button and select the appropriate transformation to go from TM65 to whichever CRS you chose. When you Ok out or hit apply, you should get a warning that your point layer doesn't match the dataframe with a button called Transformations on it. Set it to WGS84 (or whatever geographic datum/CRS you want to use to generate your lat/long values). Open the dataframe properties, either by double-clicking or right-clicking it in the ToC and go to the Coordinate System tab. While you're adding fields, add a lat field and a long field using at least float data type. If you move a point via editing, they will not update. Be aware that if they are there or if you calc them, those are now just attributes and have no relation to the point geometry. I think your original XY coordinate columns will be there, but if not you can add two new fields (I'd call them TM65X and TM65Y) to recalculate the values. Be sure to specify the coordinate system as TM65 with either tool to correctly define the coordinate values of the points.ĭepending on how you create them you may need to save the result to a feature class or shapefile for permanence. ![]() You can use Add XY Data or as faith_dur suggested in a comment the Make XY Event Layer tool. First add your coordinate data to ArcMap. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |