• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Shp file too large?

Messages
26
Country
unitedstates
Hello, I've tried to run scenProc on this file but I'm wondering if it is too big for scenProc to process? I'm getting an unhandled exception relating to memory when I try to run it. Then again, it could just be my own misunderstanding about the program. The file contains various formatted GIS data for buildings in Austin, TX during 2003. I got the information from the city's website, located here. The download name is "2003 Building Footprints." I'm trying to use the building data to create autogen buildings for the city.
 
Hi,

Data for just one city should in general not be too big to handle.

Can you show the configuration file you used in scenproc? It would be mainly interesting to see if you set the right projection for the data. I'm not behind my FS pc now, but I suspect the data is not in geodetic coordinates, so then you need to tell scenproc the right projection to use.
 
Arno, funny you should say that. I just noticed that it is in a different protection. I adjusted that and now it the autogen was produced!
 
Glad to hear you have it working.
 
Hmm, I was able to generate the autogen files but they aren't showing up in the annotator. Below are the prompt I used and here is a link to the .shp file. Can you spot what I've done wrong?

IMPORTOGR|buildp-2003.shp|*|*|+proj=lcc +lat_1=49 +lat_2=77 +lat_0=0 +lon_0=-95 +x_0=0 +y_0=0 +ellps=GRS80 +datum=NAD83 +units=m +no_defs no_defs <>
#
SPLITGRID|AGN|FROMFILE=buildp-2003.shp
#
SETAGNBUILDINGHEIGHT|*|1.0;0.0;0.0;0.0
CREATEAGNGENBUILD|FTYPE=POLYGON;FROMFILE=buildp-2003.shp;FWIDTH<20|{5ae04eb6-934c-4f63-bb48-5e7dee601212}|MAXRATIO=2
CREATEAGNGENBUILD|FTYPE=POLYGON;FROMFILE=buildp-2003.shp;FWIDTH>20|{6089A0BD-CED1-4c47-9A9E-64CDD0E16983}
#
WRITEAGNFILES|FSX|C:\Users\FSX\Desktop\build_p\texture
 
I'll try it here. In the log you see that autogen objects are made?
 
Another idea:Could the autogen failing to show in annotator or fsx be because the .shp is building footrpints?

Also, any luck replicating the issue?
 
Hi,

Sorry, I missed your reply earlier this week.

I can't look at the file, since you only provide the SHP, but I would also need the SHX and DBF to look at the data. And even than I can't fully test it of course, since I don't have your photo BGL.

Does the autogen show in FSX itself? Annotator sometimes doesn't shown autogen, while FSX does. This is usually caused by very small autogen objects. Did you use the recent development release of scenProc? Older versions can create such small objects, but in the new versions they are automatically filtered out.
 
No, nothing is showing in FSX except for the photoscenery.

I just updated to today's build with the same result. I guess it could be the small objects, but wouldn't at least the larger polygons show? I wonder again if it has something to do with the building footprints, but I'm not sure.

If you're interested and wouldn't mind helping, I can upload those other files for you to test. I'm trying to get the city setup as autogen to go with an upcoming airport (KAUS).
 
Hi,

If you can show your configuration file plus the data I'll have a quick look.
 
I've got it all zipped here.

Since the data isn't OSM ready, I've found that it can be broken into four classifications by "fea_code."
ValueDefinition
30BUILDING 100-4000 SQ FT
31LARGE BUILDING > 4000 SQ FT
32Not a Building (courtyard, etc.)

I'm beginning to think I don't have the prompt setup correctly. I've read your tutorial/wiki page but I need some time to watch the scenproc videos, especially the video about autogen workflow (tomorrow). The polygons themselves are footprints that are not perfect rectangles so I'm thinking I may need to change to a REPLACEPOLYGONBYBUILDINGRECTANGLES command, but that might result in rectangle polyons that are too small to be displayed. Maybe I should just convert it from polygon to points in QGIS?

I did, however, find more information on the projection. I never realized NAD83 or LCC had so many different derivations!



The map projection used is Lambert Conformal Conic.
Projection parameters:
Standard_Parallel: 30.116667
Standard_Parallel: 31.883333
Longitude_of_Central_Meridian: -100.333333
Latitude_of_Projection_Origin: 29.666667
False_Easting: 2296583.333333
False_Northing: 9842500.000000
Planar coordinates are encoded using coordinate pair
Abscissae (x-coordinates) are specified to the nearest 0.000512
Ordinates (y-coordinates) are specified to the nearest 0.000512
Planar coordinates are specified in survey feet

The horizontal datum used is TEXAS STATE PALNE CENTRAL NAD 83 SURVEY FEET.
The ellipsoid used is Geodetic Reference System 80.
The semi-major axis of the ellipsoid used is 6378137.000000.
The flattening of the ellipsoid used is 1/298.257222.

Code:
IMPORTOGR|C:\Users\FSX\Desktop\build_p\buildp-2003.shp|*|*|+proj=lcc +lat_1=27.41666666666667 +lat_2=34.91666666666666 +lat_0=31.16666666666667 +lon_0=-100 +x_0=1000000 +y_0=1000000 +datum=NAD83 +units=m +no_defs  <>
#
SPLITGRID|AGN
SETAGNBUILDINGHEIGHT|*|1.0;0.0;0.0;0.0
CREATEAGNGENBUILD|FTYPE=POLYGON;FROMFILE=buildp-2003.shp;FWIDTH<20|{5ae04eb6-934c-4f63-bb48-5e7dee601212}|MAXRATIO=2
CREATEAGNGENBUILD|FTYPE=POLYGON;FROMFILE=buildp-2003.shp;FWIDTH>20|{6089A0BD-CED1-4c47-9A9E-64CDD0E16983}
#
EXPORTAGN|FSX|C:\Users\FSX\Desktop\build_p\texture

Really appreciate your help! :)
 
Okay, Arno, I think I have an idea why it's not showing up. If you look at the datum information (above) from the datum I used in the IMPORTOGR step, each shows a different numbered projection. Do you think the variation in that could be causing my error: many .agn files made but nothing showing in a 10x10 sq/mi area?
 
Hi,

Let me check. I haven't had the time yet to look at your data.
 
Back
Top