I know this is a few weeks old but as I tried to add two new layers to a map
I have struggled with Spatial Contexts again.
I have captured some images from my data source and layer definition in
order to show that the layer seems to choose the wrong Spatial Context. I
have created and recreated
Thanks for all the answers. I have a much clearer picture of what I should
be doing. I see my database has no f_scinfo table but I do understand that
this is optional. Needed only if I want a more clearly named spatial
context as opposed to sc_1, sc_2 etc.
--
View this message in context:
I am using PostgreSQL 9.6.2 with PostGIS 2.3.2 and AIMS 2017.
As Jackie has mentioned before, I can confirm that the PostgreSQL Provider
uses the f_scinfo table to obtain the name of the spatial context.
However this table has no data and it is not necessary to create it as it
only provides the
I'll try this.
Thanks
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Help-with-Spatial-Contexts-tp5310988p5311753.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
___
mapguide-users mailing list
Since the PostgreSQL provider is built on the same GenericRdbms core as the
other relational providers, you should still be able to activate tracing via
the FDO_TRACE_FILE environment variable and have a look at the SQL
statements the provider is executing to get its spatial contexts
Maestro does no auto-numbering. Definitely comes from the FDO provider.
- Jackie
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Help-with-Spatial-Contexts-tp5310988p5311692.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
Where do the sc_1, sc_2, etc come from when you list Coordinate Systems
Overrides for SQL server in Maestro? Is this just an autonumber internally
to Maestro or is this stored somewhere in SQL?
--
View this message in context:
I know for SQL Server, the provider may create a f_scinfo table to store
intermediate data for spatial contexts. Since the PostgreSQL provider is
built on the same core, it may be creating a f_scinfo table for this purpose
as well.
Does your database have this table?
- Jackie
--
View this
Thanks for the thorough answer. That does match what my understanding has
been. My question arose because I added a data table to PostGIS recently.
In the Maestro Preview of that data source, the table showed sc_3 as the
spatial context of the table. The layer showed sc_2 as its selected
The logical model goes like this:
A Feature Source
- Has 1..n spatial contexts
- Each spatial context is uniquely named
- Has 1..n feature classes
- Each feature class has a designated logical geometry property
- That geometry property has a spatial context association (to an
10 matches
Mail list logo
