-
Notifications
You must be signed in to change notification settings - Fork 612
Problems parsing IFC
Ruben de Laat edited this page Jan 3, 2017
·
2 revisions
The STEP specification on Strings is not clear on the following. The order of parsing all the variants of alternative encodings is not defined. For example the following string could be parsed in 2 ways:
\S\X\S\r\S\s\S\j
\S\X
\S\r
\S\s
\S\j
OR
\S
\X\S\
r
\S\s
\S\j
Which will result in an error because the 2 characters following the \X\ are not numeric.
Get Started
- Quick Guide
- Requirements Version 1.2
- Requirements Version 1.3
- Requirements Version 1.4
- Requirements Version 1.4 > 2015-09-12
- Requirements Version 1.5
- Download
- JAR Starter
- Setup
Deployment
- Ubuntu installation 1.3
- Windows installation
- Security
- Memory Usage
- More memory
- Performance statistics
- Large databases
Developers
- Service Interfaces
- Common functions
- Data Model
- Low Level Calls
- Endpoints
Clients
BIMServer Developers
- Plugins in 1.5
- Plugin Development
- Eclipse
- Eclipse Modeling Framework
- Embedding
- Terminology
- Database/Versioning
- IFC STEP Encoding
- Communication
- Global changes in 1.5
- Writing a service
- Services/Notifications
- BIMserver 1.5 Developers
- Extended data
- Extended data schema
- Object IDM
New developments
- New remote service interface
- Plugins new
- Deprecated
- New query language
- Visual query language
- Reorganizing BIMserver JavaScript API
General