Thanks Gordon,
We are aware that migration will take months !
Unfortunately with the previous points, we're somewhat forced to migrate.
Our action plan is the following :
1. Keep our aims web viewer (our licenses are permanent) and provide
some improvements.
2. Provide some Map/Feature services based on our oracle database
(sdo_geometry) to SAP.
3. Slowly reinvent our web viewer, to have something younger, the
current viewer has almost 10 years.
Data is very important for us. Therefore we take the choice to continue
with Oracle Database and sdo_geometry.
To provide data via mapservices, itâs very easy ! Unfortunately, youâve
right, for crud, itâs more complicated.
We have enable sde on the database and created some working tables (with
st_geometry), when data is created/updated/deleted, triggers are processing
data and put it into our sdo schema.
Layers are the biggest problem for us.
Mapguide manages layer as an object, with a lot of properties, the power of
this object is the collection of scale range.
In Arcgis, a layer has just one scale range.
In Mapguide, if I want a layer âMilepostâ be shown as a point from 5000- 500
then with a symbol from 499 â 0, no problem, itâs just a layer âmilepostâ.
In Argis, we need two layers L
For the viewer, I think that for the future, openlayers will be the best
choice. With openlayers, we have weak coupling with the map server.
So Iâm practically sur that a migration to a new Gis Server will take less
time.
Arcgis API/ Geocortex are more specific for esri, and not flexible for a
potential future migration.
On the other hand, I found :
https://knowledge.autodesk.com/support/infrastructure-map-server/learn-explore/caas/simplecontent/content/autodesk-infrastructure-map-server-end-life-faq.html
*Special Offer from Esri*
Another consideration is this offer from Esri. With the recently announced
collaboration <http://www.infrastructure-reimagined.com/autodesk-esri> between
Autodesk and Esir, Esri is making a special offer available to AIMS
customers: Between January 7, 2018 through December 31, 2018, each seat of
AIMS, regardless of contract plan (maintenance or subscription), will be
eligible to receive a seat of Esri ArcGIS Enterprise Standard
<http://www.esri.com/en/arcgis/products/arcgis-enterprise/overview> plus
one additional license of the Esri ArcGIS Desktop Standard
<http://www.esri.com/en/arcgis/products/arcgis-pro/overview>. This is a
free one-time offer for the license and the license will fall under Esriâs
standard maintenance program the following year.
We have 8 seats ! So Esri must provide us : 8 ArcGIS Enterprise
Standard, right
?
Thank you all for your good advice.
JérÎme.
Post by GordonLAbsolutely, most I.T. departments in North America are extremely risk averse.
They see Open Source as a risky proposition, even if it is not so.
If you have to move to ArcGIS Server, you are going to find that you have a
bit of work.
First, the data. You have to figure how the data is created/collected.
If the data is gathered by GPS or Survey, and then imported into the system,
you will have to make sure the storage mechanism still can hold it. Oracle
can store the Spatial data and ArcMap can "view" the data but not edit
spatial data not in the SDE Enterprise schema within Oracle.
So, if you want to edit your existing data ArcMap or ArcGIS Pro, you have
1. Move all the data into ESRI Schema
2. Use a 3rd party tool plugin for ArcMap such as GISquirrel
(https://www.gisquirrel.com/home)
Or not with ESRI (i.e. QGIS)
Next, the layers and Maps. MapGuide/AIMS creates layers within the XML on
the server. Layers in ArcGIS Server are created as separate services (i.e.
Feature or Map Services). You have to publish them from ArcCatelog, ArcMap
or ArcGIS Pro. That is how you style, from the client and then publish.
Once inside the ArcGIS Server, they are published but to put together a good
1. ArcGIS online that points to your publicly available ArcGIS Server
2. ArcGIS Portal (a subset of ArcGIS online) that can be installed on your
internet or public.
3. ArcGIS API for Javascript - fairly easy to get going, much like the
Google Maps API
4. 3rd Party such as GeoCortex - a great wrapper to publish maps as a web
interface (I have even tried this with MapGuide WMS/WFS layers)
5. Open Source wrapper such as Leaflet or Open Layers - which can consume
the ArcGIS Server Rest api. (This is how I often do MapGuide/ArcGIS mashups)
So that is a bit of a migration in a nutshell.
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-
f4182607.html
_______________________________________________
mapguide-users mailing list
https://lists.osgeo.org/mailman/listinfo/mapguide-users