[mapguide-users] MapGuide MVT Tiles with view as source

[Martin Herich]

Hi Jackie,
Thank you for you answer.
Yes that would be the solution that we need and would help us.
Now we have solved the problem using new database tables where we copy the data from view. It was possible as the data are mostly static and doesn’t change often.
Martin

From: mapguide-users <mapguide-users-bounces at lists.osgeo.org> On Behalf Of Jackie Ng
Sent: Friday, May 5, 2023 12:15 PM
To: mapguide-users at lists.osgeo.org
Subject: Re: [mapguide-users] MapGuide MVT Tiles with view as source

Hi Martin,

I am pretty sure the PostgreSQL provider supports configuration as it is based on the same shared codebase used by ODBC, SQL Server and MySQL providers, which all support configuration.

By supporting configuration, we can specify a XML configuration document that provides a customised logical feature schema representation of your PostGIS db that says that <some other column> in that view is the identity property, instead of what the provider thinks (by default) is your identity property.

However, making such a configuration document is a PITA right now because the easiest way to do this with FDO Toolbox (ref: https://themapguyde.blogspot.com/2010/08/using-fdo-schema-overrides.html) doesn't work for PostgreSQL because of the I'm checking for configuration support is completely dumb and needs to be fixed.

That issue is referenced here: https://github.com/jumpinjackie/fdotoolbox/issues/82

Once I've fixed that issue and release a new FDO Toolbox with that fix included shortly after, you can follow the referenced blog post link to customise the identity property of that view.

- Jackie

You wrote:

Hi,

We are using TileSetDefinition with TileProvider set to XYZ and TileFormat set to MVT.

The problem we have is that all features inside the vector tiles have attribute "id" set to 0.

We have found out that the problem is that we are using view as the source data for layer. When we change the source data to table, then the features have the attribute "id" set to primary key value. The source data are stored in PostgreSQL database.

Is there some possibility to configure which column from the view should be used as the attribute "id" for the vector tile features?

Thank you for any hint,

Martin

--
Please Note: I no longer create new posts or post replies to any OSGeo mailing list through nabble. As a result, you most likely won't see this message appear on nabble's view of any OSGeo mailing list and may only see this message through mailing list archives or depending on your mailing list subscription settings, through daily message digests or automated notifications from the mailing lists.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapguide-users/attachments/20230509/f8f45124/attachment.htm>