Magnetic Deviation

#1
Magnetic Deviation .

Is there a way inside of SU 2019 to correct for magnetic deviation when grabbing a Google map image without having to rotate the object.

Thanks

Randy
 
#2
Hi Randy:

I posted a rudimentary work-around for the discontinuation of Geo-location features in older and freeware versions of Sketchup in the first few threads of this query:

https://www.google.com/search?source=hp&ei=JKr7XM-aF5CitQXtg5aoAg&q=site:www.fsdeveloper.com+GaryGB+Sketchup+Geo-location+work-around&oq=site:www.fsdeveloper.com+GaryGB+Sketchup+Geo-location+work-around&gs_l=psy-ab.12...1743.24745..27145...0.0..0.299.4861.36j10j1......0....1j2..gws-wiz.....0..0j0i131.-QFJPohrsYY

The issue that you are likely seeing in images exported (not screen captures) is that Google Earth outputs in a 'warped' EPSG:4326 GIS projection format rather than in a 'non-warped' EPSG:3857 GIS projection format.

Although my Sketchup Geo-location work-around cited in the query results above is useful for some purposes, a more comprehensive method would include re-projection in a GIS application or utility, of the ex: Path objects in KML format output by Google Earth in a 'warped' EPSG:4326 GIS projection format, into a 'non-warped' EPSG:3857 GIS projection format, before they are imported into Sketchup version-8 by the KML Tools plugin Ruby script ...as described in the threads cited above.

In most cases, one can just use the Rotated Rectangle plugin Ruby script to create a ex: building base 'Face' to be extruded ...as described in the threads cited above.


Terrain-type objects compiled by SDK Resample or SDK SHP2VEC require a 'warped' EPSG:4326 GIS projection format for background imagery

3D model objects (including SCASM / ASM or MDL G-Polys) require a 'non-warped' EPSG:3857 GIS projection format for background imagery.

[EDITED]

CAVEAT: 3D model objects intended to be converted into a "sloped flatten" (a terrain-type object) by Arnos' ModelConverterX (aka "MCX") require a 'warped' EPSG:4326 GIS projection format for background imagery, since, AFAIK, MCX does not peform an internal conversion of the imported 3D model from a 'non-warped' EPSG:3857 GIS projection format to a 'warped' EPSG:4326 GIS projection format for background imagery.

NOTE: Although SDK Resample and SDK SHP2VEC both require a 'warped' EPSG:4326 GIS projection format for Terrain-type source data, such objects are ultimately "un-warped" when draped onto FS terrain grid quad tile vertices / Area points when placed by the FS run time rendering engine ...to fit onto the 'curved' Earth of the FS 3D world. :pushpin:

[END_EDIT]

Hope this helps with what, IIUC, you may be endeavoring to achieve. :)

GaryGB
 
Last edited:
Top