Map is doggy

[Anonymous]

I've not used any version of Map after 2004 to any significant extent. I am
finding the later releases (2009, 2010) to be really doggy when using FDO to
shape files with themes. For example I have a TIGER line file for a county
with a theme that styles the streams, roads and railroads from the
shapefile. Any pan or zoom is laggy and edits to the theme cause frequent
processing of the graphics which again is doggy. The same is true for the
parcels and when viewing the tables. I can only imagine what it would be
like if I had to add more content on top of this.

I'm finding it aggravating to work like this. Is this what we have to live
with?

C3D 2010.
Dell Precision 490, Xeon Dual Core 1.6 GHZ
3 GB Ram (3GB Switch enabled)
Win XP Pro SP3

[Anonymous]

A couple of things to realize before you get to involved Neil. First your
system specs you posted are the minimum for Map3D 2009 or Standard AutoCAD
2010 not doing any 3D modeling let alone what is required for Civil3D or
Map3D using all there apps. Second the 3Gb switch doesn't work with Map3D
like we think it should, it does more harm than good with an XP OS. Third
the display of FDO bets really hits the graphic card and drivers, if they
are not set right expect it to act doggy.

--

Murph
http://map3d.wordpress.com/


"neilw" wrote in message
news:6299203@discussion.autodesk.com...
I've not used any version of Map after 2004 to any significant extent. I am
finding the later releases (2009, 2010) to be really doggy when using FDO to
shape files with themes. For example I have a TIGER line file for a county
with a theme that styles the streams, roads and railroads from the
shapefile. Any pan or zoom is laggy and edits to the theme cause frequent
processing of the graphics which again is doggy. The same is true for the
parcels and when viewing the tables. I can only imagine what it would be
like if I had to add more content on top of this.

I'm finding it aggravating to work like this. Is this what we have to live
with?

C3D 2010.
Dell Precision 490, Xeon Dual Core 1.6 GHZ
3 GB Ram (3GB Switch enabled)
Win XP Pro SP3

[Anonymous]

So what it boils down to is I need new hardware (and probably a 64 bit OS).
This machine is only 2 yrs old. Considering the hardware and software
requirements, the outlook for a full implementation of C3D is pretty bleak.



__________ Information from ESET NOD32 Antivirus, version of virus signature database 4659 (20091203) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

[Anonymous]

That and the fact that you re using Tiger data. IIRC the roads are all
broken into short segments. Meaning for the whole country you have too many
features that are being regenerated every time you pan. If you did a
mapimport of the same files you will probably notice the same performance
hit. You need to clean up that data esp. if you plan on using it in your
MGOS project otherwise your viewers connecting to it will see the same lag
time in their browsers.

--

Murph
http://map3d.wordpress.com/


"neilw" wrote in message
news:6299264@discussion.autodesk.com...
So what it boils down to is I need new hardware (and probably a 64 bit OS).
This machine is only 2 yrs old. Considering the hardware and software
requirements, the outlook for a full implementation of C3D is pretty bleak.



__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4659 (20091203) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

[Anonymous]

I wasn't aware of the small segments issue. I'll have a go at cleaning the
data up and see if it helps.

Yes I will defeintely be publishing the TIGER data to MGOS so I'll need to
address this. I'm still going to have issues with the parcel data though.

Thanks for the tip Murph.



__________ Information from ESET NOD32 Antivirus, version of virus signature database 4661 (20091204) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

[Anonymous]

As you are cleaning up the data delete any attributes also that you will not
be using. Example the age and sex fields, the married status etc. Even
though the values may be 0 or null they still bloat the files.Unless you
plan on searching for roads that have all single women between the ages of
20-40 that make over $50,000 per year that live in a $200,000 home. And if
you are, take into account that data is about 10 years old and make some
adjustments to your query. 🙂

--

Murph
http://map3d.wordpress.com/


"neilw" wrote in message
news:6299695@discussion.autodesk.com...
I wasn't aware of the small segments issue. I'll have a go at cleaning the
data up and see if it helps.

Yes I will defeintely be publishing the TIGER data to MGOS so I'll need to
address this. I'm still going to have issues with the parcel data though.

Thanks for the tip Murph.



__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4661 (20091204) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

[Anonymous]

Actually the TIGER line files were updated this year so it should be good
enough for our needs. The census data is still year 2000 of course but we
won't be using that anyway.

I looked at cleaning up the linework. It came in as joined polylines, not
individual segments. There isn't any census data associated with it. There
isn't much I can do to simplify it without compromising it's positional
accuracy.

It is looking like there is little that can be done to improve performance
aside from upgrading hardware and the operating system.



__________ Information from ESET NOD32 Antivirus, version of virus signature database 4662 (20091205) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com