Autodesk Consulting France is working on a project for the Assemblée Nationale to migrate 164 facility management drawings into an Oracle database. vdPConsulting is involved in the project as sub-contractor because of their extended knowledge of AcClassify.
These drawings are interior maps of buildings, where the offices, meeting rooms, hallways, restrooms, etc. are displayed as closed polylines on a certain layer. Within such a space a block is drawn, in which attributes like for example roomnumbers are stored.
AcClassify identifies these areas and finds the containing blocks & attributes, then these areas are written to the database as polygon objects. The information from the attributes are stored as properties of these polygons. In addition, all other lines, blocks and texts are stored as lines and points to be used as background information in the new drawings. These new drawings will be displayed in a web viewer.
I’ve written a couple of posts about the BGT-project which I’m working on lately. A recurrent topic, when speaking about the BGT, is: “where should the border polygon be situated ?”
Frist suggestion is the cadastral border. This is also an authentic registration and a good solution for two municiplalities. I’m involved with a project at one of the provinces and they “slice” through municipalities with their provincial roads, that makes the cadastral border less useful.
Users of the provincial map are among others the departments of road- and greenmanagement. Besides surveying the topography, that is situated in a corridor along the road, the road- and greenobjects are important for these maintenance maps. Sometimes there is more green managed than is owned by the province – imagine a ditch that is mown completely, while the cadastral borderline is in the center of the ditch. Currently many road crossings are tranferred into roundabouts, and therefore the province needs to buy pieces of land from municipalities or private owners. The new cadastral situation will take some time to become established and therefore the cadastral border isn’t up-to-date.
In our project we’ve taken a pragmatic approach: we use the outside topographic lines in the corridor maps to build the polygons. In some cases we have to add supporting-lines to close the polygons. If the BGT border polygon has been defined than we will know which polygons needs to be splitted. The current maintenance and cadastral borders are left out of the proces for now. Also buildings, fences, roadlines that a partly on the map, but outside the provincial maintenance area are left out of polygon creation.
With this approach we can create the object oriented map and use the geometry of road- and greenobjects to connect to maintenance-data.
In the meantime still discussing with the GBKN Foundation, municipalities, waterboards, National Road Administration and the Ministry of Housing, Spatial Planning and the Environment about the BGT border polygon.
I’ve already blogged a couple of times about the BGT-project which I’m working on lately.
Structuring of the data goes very well, the first test-migrations with AcClassify into the Oracle Spatial database has been successful last week and the data can be viewed in ArcGIS-desktop and the webviewers.
That I was clumsy enough not to config the database limits properly and that the Oracle tables have to be registered into SDE, that’s peanuts 😉
They’re looking over our schoulders from the various local & regional discussion groups, because the BGT keeps ( almost ) everyone busy these days.
In two weeks there is a meeting where people from Geonovum – the brains behind the IMGeo-model – will attend as well, because they are very interested in feedback from the field.
At one of the migration projects where I am involved, the source data is managed in AutoCAD Map and there must be a regular update of the data posted into an Oracle Spatial database. From this Oracle database the large scale data is shared with the GIS-department and used for web-applications. To support this migration process I have developed an AcClassify Workflow utility.
The customer – a Dutch province – has stored their large scale basemaps in DWG-files into a very detailed folder structure on a fileserver. For each provincial road there is a sub-folder, with topografie but also other sub-folders with DWG’s for the theme’s like roadsigns and green management etc.
The Workflow utility – a C# application, that runs inside AutoCAD Map – gives in the UI the possibility to select the roadnumber, the option to delete old data from that roadnumber from Oracle and to upload the new data into Oracle using AcClassify.
If this is an update, than de utility will remove the old data from that roadnumber from their respective feature tables ( for roads, water, buildings etc. ) using SQL Delete statements. Next the utility creates the necessary AcClassify config XML-files ( adding roadnumber, Oracle schema-name etc. ). Than the AcClassify process is started using API-functionality.
With this the workprocess, with a lot of manual action, is reduced to a userfriendly AcClassify Workflow utility.
New : there is an update of this utility that starts the AcClassify process using API-functionality
In my previous post AutoCAD Map – Break, Trim and CleanUp I’ve blogged about the process to structure the drawings.
This blog is about classification and creation of the polygons.
First we’ve created the centroids, AutoCAD points with attribute information in conformity with the IMGeo-model.
Such a centroid for a Wegdeel contains for example attributes like IDentificatie, objectBeginTijd, status, relatieveHoogteligging, typeWeg etc.
Next to it there are centroids for Spoorbaandeel, Waterdeel, Terreindeel, Kunstwerkdeel and Pand. These Pand-objects come from the Basisregistratie Adressen Gebouwen ( BAG ) by the way.
Further a Polygon Topology has to be created. Herewith we also use a Wizzard interface, where the structured linework are the links which the centroids are joined.
If there are lines not properly closed, than the Topology process comes with an error. Likewise if centroides are missing or double.
The Topology model is converted into MPolygons, with the IMGeo classification from the centroids copied to them. These MPolygons are migrated as polygons into the Oracle database using AcClassify.
more about that in the next post