Andrea, > The usual is not to use GML: it's an interchange format, powerful, > but text based, slow to parse, hard to index. > Better take the GML and turn it into some format that is meant to > be subset and indexed efficiently, at least if you have any significant > amount of data.
I see. is there any 'usual' way of doing this? or is everyone working with GML-based input data reinventing the wheel? > AIXM is afaik complex features, you might want to look into the app-schema > datastore. thanks - I'll take a look at it. > Alternatively I've seen approaches in other systems were the full XML of > a feature is stored as a blob in the database, and a few of the > attributes are > projected out of it as plain attributes, those are the ones that are used > the most (WMS and the like) and can be accessed fast, whilst the > rest is accessed only occasionally if the whole feature, or some > less used attribute, is required (at which point access becomes slow of > course). as you point out, this approach as quite a few drawbacks... Akos ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
