The general URL pattern is:
GET http://localhost/mapguide/rest/library/.FeatureSource/data/
On a side-note, I would recommend you to have a look at the repository
through its HTML representation:
http://localhost/mapguide/rest/library/list.html
The HTML representation of the repository really maps out all the possible
URLs you can access for any particular resource. It's a simple way to
"explore" what the mapguide-rest API offers, as it's all there as links.
Failing that, there's also an interactive swagger API runner at:
http://localhost/mapguide/rest/doc/index.html
This lists all the APIs available with auto-generated forms for you to test
the various APIs.
Now back to the topic at hand, a SHP file throws a spanner in the works
because it is not one physical file. It has various components (.shx, .dbf,
and a whole bunch of other files) that you also have to download and
mapguide-rest does not provide any SHP-specific access path where you can
download the whole SHP "file", so your application has to be aware of a SHP
feature source and have some custom code that downloads all the components
of the SHP "file" and serve out a zip file of all the component parts.
- Jackie
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/mapguide-rest-tp5296412p5296470.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
