OSM and Microsoft building footprints

Is any of the inaccuracy due to not taking into account the earths curvature?

I'm going to do something with this data for AeroScenery at some point, sadly not enough hours in the day at the moment.

My plan was to write something to split it into lots of 0.1 x 0.1 degree files while converting the data format to OSM.

From there they can be brought in to scenProc easily.

When you say

Quote

But next, we have to mass modify the attributes of these buildings.

can you let me now what needs to be done there?

If there are attributes it MS buildings, then it's cool and I would reckon they don't need to be modified, just used.

If there is no attribute in MS buildings, then it's just like most buildings in OSM...

Nick, if you can translate these files into shapefiles instead of OSM, I think it's more powerful and better suited for opening/checking/editing attributes in QGIS or similar and work with ScenProc.

I see some tools already exist for GeoJSON to SHP convertion, maybe you can pick some existing code without having to reinvent the wheel...

https://mygeodata.cloud/converter/geojson-to-shp

Cheers

Antoine

Quote from Rodeo

there are no attributes with the MS buildings. I can imagine to add attributes as we use in aerofly.

Housetypes residential, industrial,

rooftypes gable or flat,

number of levels.

I see. I haven't really looked at the MS data yet.

Someone has written a Python script to get a chunk of OSM data and conflate MS footprint data with it.

https://github.com/maxerickson/osm_ms_buildings

This could be useful for getting the data down to a manageable size, with the result being one OSM file with OSM buildings, and one OSM file with MS only buildings.

I guess some attributes can be worked out by scenProc from the height?

Is it possible to add osm height and type data (where available) to the Ms Buildings? I know in some programs (Outerra comes to mind) blending disparate datasets is well on its way to becoming a high art.

EDIT: Looks like I cross posted with Nickhod.

Quote from HiFlyer

Is it possible to add osm height and type data (where available) to the Ms Buildings? I know in some programs (Outerra comes to mind) blending disparate datasets is well on its way to becoming a high art.

As far as I can tell, the MS data already has height information for each building.

(At least the small North and South Dakota data sets I tried did).

I think the challenge was the overlap with OSM data, and the size of the MS data files, which that Python script should solve.

I started using SQLite + SQLiteStudio and dumping all the data in tables.

Then I add all the attributes for High Rise, Residential, Roads and so forth (real fast)

I use select statements to extract (break city down into pieces) import into QGIS and export then as a shapefile.

Then I open the shapefile in JOSM, check it for inconsistencies, save it as a OSM file and run through sceneProc.

Its a long process, but it's fast.

Quote from Rodeo

Really? That would be fantastic. Perhaps the datasets I used lost their attributes during previous splitting processes.

Yep, you're right. I followed a link to the previous version of this data which only had 9.8 million buildings. It did seem to have height data though. The newer, large dataset version doesn't.

https://wiki.openstreetmap.org/wiki/Microsoft…_Footprint_Data

That is correct, one is footprints only and the other contains height data but is older.

Quote from Kloot

I started using SQLite + SQLiteStudio and dumping all the data in tables.

Then I add all the attributes for High Rise, Residential, Roads and so forth (real fast)

I use select statements to extract (break city down into pieces) import into QGIS and export then as a shapefile.

Then I open the shapefile in JOSM, check it for inconsistencies, save it as a OSM file and run through sceneProc.

Its a long process, but it's fast.

Nice workflow.

Why the JOSM and OSM step ? Why not simply checking the shapefile in QGIS and process it directly with ScenProc ? It would save you some steps...

Cheers

Antoine

Quote from Trespassers

Nice workflow.

Why the JOSM and OSM step ? Why not simply checking the shapefile in QGIS and process it directly with ScenProc ? It would save you some steps...

Cheers

Antoine

It allows me to edit the file & save it.

I would need to add an exporter plugin to re-save as a shapefile.

I think either way, it's the same amount of steps

Quote from Kloot

It allows me to edit the file & save it.

I would need to add an exporter plugin to re-save as a shapefile.

I think either way, it's the same amount of steps

I don't quite get it : with the preceding step you saved it as a shapefile... in QGIS you can edit your shapefile

Quote from Trespassers

I don't quite get it : with the preceding step you saved it as a shapefile... in QGIS you can edit your shapefile

I like editing in JOSM

QGIS is good for import - convert - export in most formats and converting centroids to polygons