7 DIFFERENT PROJECTS All solved with FME Desktop and / or FME Server
1. Buffering the coastline of Norway FME Desktop
QUESTION: How many houses are within 100m from the 103 000 km (64 000 mile) (2,5 times around the earth) long Norwegian coast?
Without 100m buffer With 100m buffer (red)
OVERVIEW OF FME WORKSPACE 4 6 1 2 3 7 8 5 1. 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)
Buffering the coastline of Norway
2. «Zoning-maps» FME Desktop
Bruk av FKB-data for å gi alle ADRESSER en FAKTOR som sier noe om kvaliteten på beliggenheten
HOVEDDATASET: BYGG - SENTERPUNKT
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
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
Input - Bygg: Bolig Input Bygg: Skoler Output: Bygg med faktor for bolig
VORONOI-POLYGON
OUTPUT DATASET I KART (GOOGLE EARTH, KML) Huspunkt med metadata og beregnede faktorer
3. Participants on Norkart usermeeting 2013 FME Server
4. Orkdal Travbane 3DPDF FME Desktop
5. Doing laundry with FME FME Desktop / FME Server
CASE: LAUNDRY LISTS AGAINST VALID LISTS Valid values in one field: My manually punched DB: - Harrrass - Hearrth - Hygieene - Hiena - Hourrible - hyginci
CASE: LAUNDRY LISTS AGAINST VALID LISTS Valid value: - Hearth All of these should match Hearth: - Eahrth - Hreath - Hearth - Hrt - 234hea3krt - 23 43 hearh f33dd
LAUNDRY V1
LAUNDRY V1 MANY CUSTOM TRANSFORMERS
LAUNDRY V2
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: www.rubular.com -> Sonja Henies plass 3, 0185 Oslo - (\D*)(\d*)(, )(\d*)(.*)
6. Import and validation of SOSI data to ESRI Geodatabase FME Desktop and FME Server
INPUTDATA EXAMPLE OF ONE SMALL AREA
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
OVERVIEW OF THE LOGIC SOSIfile 1 2 3 4 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
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.
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 e-mails back and forth between supplier and client to «fix errors» FME Server handles this without any interaction from the client.
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.
7. Maps showing amount of mussels in the ocean FME Server
vcard: Sigbjørn Tillerli Herstad E-mail: sigher@norkart.no Twitter: @SigTill
www.norkart.no/27