I bring in the shapefile with the FDO connections and place a label using the attributes from one of the fields. These attributes are set to a constant map space size. Before I export to a dwg, text in the center vanishes when I zoom to certain levels. Surrounding text still appears. I zoom in until all the text appears. (BTW These are PLSS section numbers so they are quite consistent and order in their physical placemnet). Then I export to dwg and find that text is missing in the dwg. What is odd is that I am missing section numbers for a township and range in the "middle" of the data set. It is like a square was removed, because all surrounding sections are there. This is getting quite annoynig and I know from what water cooler talk that many in the office are quickly losing patience with autocad and the faith in its abilities is quickly crumbling when it comes to gis data. everything just seems so counter productive.
Using Acad Map2010
and someday when I click to open the style editor, I hope my properties bar won't disappear. And then again someday, Autocad may actually fix some of these glitches and provide you with software that is of the value that was paid for it.
You might also take a look here: http://beingcivil.typepad.com/my_weblog/2012/02/fine-tuning-fdo-labels.html , especially as you are exporting to DWG anyway.
@NateMoore wrote:You might also take a look here: http://beingcivil.typepad.com/my_weblog/2012/02/fine-tuning-fdo-labels.html , especially as you are exporting to DWG anyway.
Nate,
You missed this "Using Acad Map2010" in the first post. 🙂
thanks for that catch Murph. BTW do you know why opening the shapefile style editor forces the properties tab to close? I have been emailing autocad about this for almost a year now and no one responds. I have seen it occur in 2010 thru 2012
@Anonymous wrote:thanks for that catch Murph. BTW do you know why opening the shapefile style editor forces the properties tab to close? I have been emailing autocad about this for almost a year now and no one responds. I have seen it occur in 2010 thru 2012
No idea on why it does that with the property palette,in fact I didn't notice it did that until you posted about it the other day. It may be a dotnet issue.
Can't find what you're looking for? Ask the community or share your knowledge.