GEOMAP, Bing Image Extents

[Anonymous]

So here's my issue:

I have an AutoCAD file that was "built" by others consisting of property boundaries and some hatching and nothing more.  I'm pretty sure it was setup as a non-Map file to begin with.  When I originally received it, I had to do a bunch of cleanup and get it aligned to a standard coordinate system (Kentucky State Plane 1983, South Zone).  I have coordinate system assigned and I'm trying to bring in live Bing imagery using the GEOMAP command.  The issue is that it's not covering the entirety of the properties (see screen shot).  I need to re-center the imagery around the properties so that I can show main transportation routes and infrastructure around the various parcels.  Please help!

[georg.grebenyuk]

Hi, Richard

I think - you need to copy system's definition [if you assign to drawing CS form System Library] and change it parameters on second tab of Properties of Coordinate system (change to smaller value of longitude). After that save it system and assign it to your drawing

[Anonymous]

Egor,

I misspoke partially in my original email.  I stated that the file was in Kentucky 83 South Zone.  In fact, I misread the coordinate system and it is in Kentucky 83 Single Zone.  The limits of the Single Zone are shown in the screen shot.  These limits (minimum, maximum) are well outside of what I need and what is showing up on screen.   

[Pointdump]

Richard,
My 2018 C3D shows a Minimum Longitude of 87 Degrees in the KY83F Coordinate System, which is obviously not enough to cover the entire state. The limits you show should cover the entire state, so I'm not sure what's happening.
How are you assigning the KY83F Coordinate System? What version of Civil 3D or Map 3D do you have? Do you have all updates? Can you post your drawing? I've attached a shapefile of Kentucky. Drag-n-Drop it into your drawing to check the extents of Bing Live Maps.

Dave

[ChicagoLooper]

Contrary to popular belief and what's already been said, the Bing imagery, when turned on in Map 3D, of a State Plane Zone, does NOT get cut off the the edges of that zone. The image will extend beyond the perimeter of the State Plane Zone, in your case Kentucky NAD83 South Zone.

There are two (possibly more) reasons you are not seeing Bing imagery in the background: 

1. You are using the wrong coordinate system.
2. The coordinate system is a 'custom' coordinate system and the creator has not properly set it up to capture a wide enough area for Bing maps to appear. It doesn't necessarily mean the x,y coordinates are wrong, it may or may not be wrong, but it definitely isn't 'capturing' a wide enough area.

Shown below is the Bing imagery  for KY83-SF.

If you are using a 'custom' coordinate system, it needs to be either re-created or adjusted to capture your site because obviously it not working for you.

[Anonymous]

The coordinate system I'm in is KY83F (this is the single plane zone for Kentucky).  I am using AutoCAD's coordinate system, not a custom range.  See screen shot in previous post that shows the limits of the zone.  Additionally, the coordinate system appears to be correct.  The imagery that is being pulled in is coming in where it should (e.g. property lines that border public roads follow the DOT ROW exactly).  

[ChicagoLooper]

---

@Anonymous wrote:

The coordinate system I'm in is KY83F (this is the single plane zone for Kentucky).  I am using AutoCAD's coordinate system, not a custom range. 

OK, I understand. If you have properly assigned KY83-SF then your modelspace and have turned on Bing imagery, then your map should look like the image in Post 5 of this thread. (Post 5 shows the  proper 'coverage' area of Bing Maps when using KY83-SF.) If your Bing Map doesn't look like that, then someone, maybe you, maybe not you, has adjusted, either intentionally or unintentionally, the longitude values of KY83-SF so it focuses only on the eastern portion of the Kentucky State Plane South Zone.

You'll need return the longitude back to its original 'default' value so the KY83-SF covers like it supposed to because right now your KY83-SF zone is too narrow.  

---

[Pointdump]

ChicagoLooper,
"...Bing imagery, when turned on in Map 3D, of a State Plane Zone, does NOT get cut off the the edges of that zone."
It sure does if the extents are wrong in the definition. It's rare but I've seen it a few times. That Kentucky System, KY83F, is one of them. Several Forum Members are from Kentucky, and they have howled about it. I prefer using C3D 2018. I haven't checked 2020 to see if Autodesk has corrected it. That's why I was trying to get Richard to cough up information on Version, Updates, method of assigning Coordinate System, etc.
Dave

[ChicagoLooper]

@Pointdump 

OK, I see. When I look at both zones, KY83-NF and KY83-SF, refer to your earlier post where you have posted an image, it appears as though the south zone is using the longitude extents of south zone, since the north is narrower in the east/west direction than the south. At any rate, Bing is correct in v2019.

[Anonymous]

@Pointdump @ChicagoLooper  I apologize for the delayed reply.  As y'all were posting yesterday, I was expecting a call from AutoDesk to help resolve which never happened.  Let me clear up some confusion:

Program - AutoCAD Map 3D with Carlson Software installed jointly 

Problem File - DWG built by an unknown CAD Tech.  Datum is KY83F (NAD 1983, Single Zone for Kentucky). File contains surface property boundaries in basic PL linework with some hatching.  Base file size is very small (under 6 MB)

This file came with several other similar files that depict property boundaries for the mineral (sub-surface) estates.  The other files are in KY83-SF (NAD 1983, South Zone for Kentucky).  There are valid reasons for the mineral files to be in this datum.  I really don't care which datum the surface properties are in as long as it's a common, translatable datum.  

[Anonymous]

I will also note that for the mineral files in KY83-SF, I have no issue bringing all of the correct imagery in with it properly georeferenced.  The imagery that the file brings in right now is correctly georeferenced but just not all of it.

[Anonymous · Accepted solution]

Gentlemen,

While I can't identify the actual culprit to cutting off the imagery, I did find a solution.  I was able to create a new Map 2D file, assign KY83F to the new file, COPYBASE the pertinent objects from the original file and paste into the new.  Base for copy and insert was 0,0,0.  As soon as I did this, GEOMAP returns imagery with extents similar, if not the same, as @ChicagoLooper post earlier.  Thanks again!