7 DIFFERENT PROJECTS. All solved with FME Desktop and / or FME Server

Transkript

1

2 7 DIFFERENT PROJECTS All solved with FME Desktop and / or FME Server

3 1. Buffering the coastline of Norway FME Desktop

4 QUESTION: How many houses are within 100m from the km ( mile) (2,5 times around the earth) long Norwegian coast?

5 Without 100m buffer With 100m buffer (red)

6 OVERVIEW OF FME WORKSPACE Inputdata (Municipality-borders (SOSI), Coastline-data (SOSI)) 2. Prepare data for processing 3. Make buffer (x meter outside chosen object (coastline) 4. Process «Islands completely covered by buffer (smaller than x meter)» 5. Process «Islands where some of the Island is covered by the buffer» (larger than x meter)» 6. Process «Coastlines as part of the mainland (not Islands)» 7. Simplify dataset (to reduce amount of data) 8. Output-data (KML, PDF, SOSI)

7 Buffering the coastline of Norway

8 2. «Zoning-maps» FME Desktop

9 Bruk av FKB-data for å gi alle ADRESSER en FAKTOR som sier noe om kvaliteten på beliggenheten

10 HOVEDDATASET: BYGG - SENTERPUNKT

11 INPUT DATA HOVEDDATASET: BYGG SENTERPUNKT Ett lite utvalg av DATASET som brukes til beregninger i forhold til Hoveddatasettet (BYGG ): OBJTYPE: Bygg av typen INDUSTRI OBJTYPE: Bygg av typen BARNEHAGE OBJTYPE: Bygg av typen SKOLE OBJTYPE: Bygg av typen JERNBANESTASJON Tettbebygde strøk N50 Støyberegninger Avstand til Sjø/Kystlinje

12 OVERSIKT I FME DESKTOP Grønn: Her gjøres en og en beregning mot forskjellige dataset Blå: Slår sammen verdier, skalerer og genererer statistikk Rød: Genererer Voronoi-polygoner og klipper Gul: Styling til de forskjellige datasett, tegneregler

13 Input - Bygg: Bolig Input Bygg: Skoler Output: Bygg med faktor for bolig

14 VORONOI-POLYGON

15 OUTPUT DATASET I KART (GOOGLE EARTH, KML) Huspunkt med metadata og beregnede faktorer

16 3. Participants on Norkart usermeeting 2013 FME Server

17

18 4. Orkdal Travbane 3DPDF FME Desktop

19

20 5. Doing laundry with FME FME Desktop / FME Server

21 CASE: LAUNDRY LISTS AGAINST VALID LISTS Valid values in one field: My manually punched DB: - Harrrass - Hearrth - Hygieene - Hiena - Hourrible - hyginci

22 CASE: LAUNDRY LISTS AGAINST VALID LISTS Valid value: - Hearth All of these should match Hearth: - Eahrth - Hreath - Hearth - Hrt - 234hea3krt hearh f33dd

23 LAUNDRY V1

24 LAUNDRY V1 MANY CUSTOM TRANSFORMERS

25 LAUNDRY V2

26 ADVANTAGES OF EVOLVING AV WORKSPACE OVER TIME Better organizations and commenting on v2 From many Custom transformers to fewer on v2 Smaller Custom transformers on v2 Changed DB approach: Bulk load instead of SQL each feature Removed many unneccessary attributes at load-time Much faster due to loading in bulk is OK due to low memory - usage Using regular expressions (with StringSearcher and StringReplacer) more efficiently can replace many Transformers. Very handy: -> Sonja Henies plass 3, 0185 Oslo - (\D*)(\d*)(, )(\d*)(.*)

27 6. Import and validation of SOSI data to ESRI Geodatabase FME Desktop and FME Server

28 INPUTDATA EXAMPLE OF ONE SMALL AREA

29 FME SERVER IMPORT FME SERVER Geometrisjekk SOSI-valideringssjekk ID-sjekk på eksisterende objekter SOSI PDF LOG SOSI PDF Sjekk avstand fra eksisterende obj. med nytt obj. FEILET OK SOSI SOSI-topologi!= Topologi i ArcSDE-DB Fyll logg-databasen med endringer som er gjort SOSI PDF LOG ArcSDE

30 OVERVIEW OF THE LOGIC SOSIfile ArcSDE Operational DB Generate paths/published params based on attributes in SOSIfile Do all checks: - Geometry - SOSI - Attributena me/values - Exisiting Ids Create logfiles (in SOSI, txt, 2D / 3D PDF) and add geometry to ArcSDE All data verified Do: - Database updates All data verified and all logs updated Do: - Wrap up files from previous FMW-files into one package and send by e- mail to supplier MSSQL Logging etc SOSI-file, PDFreport, textreport

31 WHY FME FOR THIS PROJECT? - FME supports plugins - Support for SOSI reading / writing and validation (with Norkarts plugin GDMMapper) is excellent Conclusion: Even though Safe Software is no domain expert of SOSI, FME is a SOSI expert through the quality in plugins like these.

32 WHY FME SERVER INSTEAD OF FME DESKTOP IN THIS PROJECT? Independent of «opening hours» of the company supplier can add data whenever they want right into the operational database. Saves manual labour, no s back and forth between supplier and client to «fix errors» FME Server handles this without any interaction from the client.

33 WHY 4 WORKSPACES INSTEAD OF 1? Try to avoid one large «sailing ship» Make sure that all geometry are validated and inside the database before running any other database updates Split between geometryhandling, attributehandling, databasehandling Easily add other procedures. Currently working on adding a new workspace between FMW-2 and FMW-3 that takes only attributes from the features and stores these in another database.

34 7. Maps showing amount of mussels in the ocean FME Server

35

36 vcard: Sigbjørn Tillerli Herstad

37