Geographic Location Bug?
-
I have a site model that I would like to place in Google Earth, but am having a hard time establishing the Lat/Long resolution needed to accurately place the model. It appears that when I click on "Set custom location" [under WINDOW, MODEL INFO, LOCATION], I am unable to set the location beyond the third decimal place. For example, I want to use a Latitude of 44.5418N, but SketchUp will only allow 44.5410N or 44.5420N. The same happens for Longitude.
Any ideas as to why there is this limitation. To me, this type of resolution seems pretty important, especially for design professionals.
I'm using SU-Pro version 7.0.10247 and Google Earth 5.0.11337.1968 (beta)
Thanks in advance.
-
Hm. I get the 6 decimal precision Lat/Long data from GE and paste it into the Model info dialogue. SU allows 4 decimal precision but it rounds up/down my (6 decimal) input to those 4 decimals.
See the screenshots:
![GE "output"](/uploads/imported_attachments/B5T1_ScreenShot003_cr.png "GE "output"")
![SU "input"](/uploads/imported_attachments/Jk0Z_ScreenShot004_cr.png "SU "input"")I wouldn't say that it couldn't be more precise but rounding to this 4th digit is at least better than to the 3rd (that you seem to have since if the 4th is zero, it doesn't count).
-
Thanks for responding. Being able to input to the 4th decimal place would be helpful, but in my case, I'm only getting resolution to the third. I've tried entering in 44.5418, but it will only take 44.5410 or 44.5420. I'm not sure what's going on with that. Any thoughts?
What about reversing the process so I can bring the SU model into Goggle Earth (pull vs a push from SU i.e. "place in model")? How would one go about that process?
Thanks again
-
For a quick solution, you can copy and paste these lines in the Ruby console replacing the values with your own.
Sketchup.active_model.shadow_info["Latitude"] = 1111.11111Sketchup.active_model.shadow_info["Longitude"] = 1111.11111Or try this Model Location plugin.
http://sketchuptips.blogspot.com/2008/01/plugin-model-location.html
-
Practically speaking, it should be all the same where exactly your SU origin is as you don't have to place your model right into the origin. I'm still baffled about this. I can manually input anything up to 4 digits. I even tried to change units and their precision (maybe it has some effect on the LatLong precision) but no.
Well, if you wish, I can make you a (template) file with your custom location although I know it's not THE solution.
-
Maybe it is platform dependent? Are you on a Mac AVD?
-
@avd said:
I have a site model that I would like to place in Google Earth, but am having a hard time establishing the Lat/Long resolution needed to accurately place the model. It appears that when I click on "Set custom location" [under WINDOW, MODEL INFO, LOCATION], I am unable to set the location beyond the third decimal place.
.......
I'm using SU-Pro version 7.0.10247 and Google Earth 5.0.11337.1968 (beta)It may seem to be only 4 digits but as far as I see you can enter 6 digits.
I'm able to place a (transparant) box on a corner of a building at position:
51.828187N / 4.706535E , checked by placing a (corrected) place mark!!!
Next I'm able to reposition that box on:
51.828188N / 4.706536E , checked again by placing a new (corrected) place mark!!!Between first and second location I had to place the box at an other location not too nearby, to get the second location reloaded correctly.
Wo3Dan
-
@wo3dan said:
I'm able to place a (transparant) box on a corner of a building at position:
51.828187N / 4.706535E , checked by placing a (corrected) place mark!!!
Next I'm able to reposition that box on:
51.828188N / 4.706536E , checked again by placing a new (corrected) place mark!!!Hi Wo3Dan and other fellow SU designers. In our environment we would need the same level of precision (5 or more decimals) and unfortunately the SU designers don't want to support our (and Google Earth's) needs. You seem to have been able to create a work-around, but unfortunately I cannot quite catch the idea. Can you give a more detailed account of the procedure that you use.
It seems to me that you are creating precisely aligned placemarks in Google Earth and that you import (Tools > Google Earth > Get Current View) them into SU to get better precision. Is that correct?
I still have a feeling that the easiest way to settle the problem would be that the SU designers would offer us the same level of precision that is being required in the Google 3D Warehouse - Acceptance Criteria. Correct alignment won't be achieved as long as rounding errors produce deviations of a magnitude around 5 meters (as they do in our area).
Advertisement