• 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.

Splitgrid

Horst18519

Horst18519

Moderator
Resource contributor
Messages
2,385
Country
germany
Hello Arno,

I found that the splitgrid feature does not take into account the size of the import file, which means you can't just use * as lat/lon values as the splitting will take forever because scenproc splits the whole planet, no matter how small the import area is. That means the user always has to define limits, which can be tricky if he doesn't really know the limits of the osm file.

Couldn't scenproc just read the limits from the file?
 
Hi Thorsten,

Splitgrid uses the extends of the currently loaded features. So if your OSM file only contains a part of the world, it will only process that part.

How big is the area you try to load? Splitting the features is still the most expensive step.
 
Weird, I tested it with limits and without, same files, no other changes in the spc file. With limits the splitting took 30 seconds, with * as limits it was still going on after 20 minutes. How exactly should I use the placeholders? Just * or *;*;*;*?
 
Hi Thorsten,

Just one star is enough.

And the bounds you specified are covering all objects in the OSM file or does the file contain objects outside of the bound as well?
 
No, the area was rather small. I used *, all features where within the limits.

Never mind though, now that I know it should work I'll try it again.
 
Hi,

It is still interesting, I'll take a look. I was doing some testing with OSM file today as well and the performance was worse than I expected as well. So maybe I should double check my code is something slipped in.
 
Too long to split

Hello all,

My name is Roberto, I am quite new on this, so please forgive me for the silly questions...

My issue, is that at first I included all the buildings in my small village (around 4500), I left the program run for a whole night but in the morning it was still working (splitting?) and i cancelled it... After that I delete all the buildings using quantum GIS, and left just my house... save it to a new shp file and run scenproc again with that shp... After 30 minutes, it is still running (splitting?)...

As i read this thread I thought that the limits could be a problem, but I don't know how to change them in scenproc... should i change them in the shp file?

Thanks and regards...

Roberto
 
Hi Roberto,

Is the shapefile you use in wgs84 projection? Else splitting might take very long.
 
Hello Arno!!

That was the issue!, anyway I found that the splitting command is necessary if I want to plant trees, right? but not buildings, right? what I want, is to place all the buildings in my region... At first I used the split command with a shp file that contained only my house... and it was divided in 90 polygons!! After that, I removed the command and my house was found and the AGN file created...

The problem now is that I don't know where to place the agn file... I placed it where my ortophotographic scenery is (in the texture folder) and my house is not there... I also tried in the "world" folder in the scenery folder of fsx, and nothing...

The name of the ang file is 1111...1111.agn (with 111 I mean lots of 1s) is that ok? or should I change the name?

Thank you very much!!!

Roberto
 
Sorry Arno, the issue about the 1111...111.agn was because i was using udm50 instead of wgs84... no I am doing the conversion but still is not placing anything...
 
The .agn files must be placed in the texture folder of you fotoreal scenery.
try to set the slider of the scenery configurator to max. anyways I never have seen this files with the same numbers, I mean it's strange.
 
Hi,

The split grid step should always be done, also for buildings. You can list certain files as option in the step, in that case polygons from that file are not divided into smaller polygons, but they are still assigned to the correct autogen cell.

The numbers of the autogen files code their location. So if you first had the wrong data, then the autogen probably ended up somewhere else on the earth.
 
You must log in or register to reply here.
Back
Top