Definitely spatial index, and coordinate system can effect this. Using views instead of tables can do this. I found an odd ball outlier that if you make fields displayable in maestro and any have a null value for the checked fields it will fail. I documented this in git. I just unchecked all fields and selections worked again (I don't use the built in viewer)
On Thu, Jul 9, 2026, 9:44 AM Gordon Luckett via mapguide-users < [email protected]> wrote: > The other issue is that the underlying spatial table or view does not have > a primary key. > > On Thu, Jul 9, 2026 at 10:29 AM David Bowen via mapguide-users < > [email protected]> wrote: > >> We're experiencing an issue where random items on the map won't select, >> even though the layer is set to be selectable. I've been unable to identify >> a common setting between the various layers that are experiencing this >> issue. >> >> In the below image, the outermost lines are selectable (labelled as “S”), >> however the inner ones are not selectable (labelled as “NS”), unless you >> also select one of the outer lines. We're getting similar behaviour in >> other layers that correspond to different tables. >> >> Has anyone else encountered this issue? We're using MGOS 4 Final Release. >> We don’t encounter this issue in an environment that’s set up with MGOS 4 >> Beta 2, reading from the same database. Additionally, I'm not noticing any >> entries in the error logs that would point to the issue. >> >> Thanks, >> >> David >> >> [image: image.png] >> >> _______________________________________________ >> mapguide-users mailing list >> [email protected] >> https://lists.osgeo.org/mailman/listinfo/mapguide-users >> > _______________________________________________ > mapguide-users mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/mapguide-users >
_______________________________________________ mapguide-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapguide-users
