![]() ![]() This would be more efficient than adding separate SQL queries for each layer if the queries are based on the same table or view. If you have a single data source that you want to split up into multiple Layers, you can set the Row Assignment column which will be used to differentiate the data for each layer. If you set it on the Region, each Layers may refer to the Region data source by setting the layer’s Location attribute to Region Source. if you want to get data from multiple data sources), or you can set the data source on the map Region. You can choose to set the data source directly on each Layer (e.g. Once you’re happy with the new map you can then delete the original plugin region. Instead, I recommend using the Duplicate feature to create a copy of your map region, change the attributes on the copy, using the original as a reference as you go. However, the danger with this approach is that you may lose some attributes and customisations that you had on the plugin region. If you already have a map based on the ReportMap plugin, you can if you wish convert it to a map by simply changing the region Type to Map – the SQL data source will be preserved and you can use the same query for the new Map region type. The Map region is free to use within your applications, just like any other built-in feature of APEX. no API key, and no APIs need to be enabled.no account on a 3rd party cloud service.To add a map to a page, I added a region of type “Map” and nominated a data source for the Layer to show on it.įirst thing you might notice is what I didn’t need: ![]() Let’s try the new Map region, and compare it to the jk64 ReportMap plugin. ![]() The APEX Map region renders the map using the MapBox API, with a number of tile backgrounds included based on OpenStreetMap and HERE map data. There will be more official blog posts coming directly from the APEX development team about this and other new features being introduced in APEX 21.1, so keep a look out for those! Note: this post is based solely on my first impressions of the new feature and is not intended to answer all questions about it. It also means that maps added to applications based on the core feature will be fully supported in future releases of APEX without needing to rely on a 3rd party. due to the lack of direct support from Oracle). This is a welcome move because it means maps will be easy for all APEX developers to use, including those who avoid plugins (e.g. This component allows the developer to show a world map on the page, and add one or more “Layers”, each based on a table or SQL query, to show features on the map. ![]() In the latest pre-production release APEX 21.1 which you can try today for yourself at, the APEX development team has introduced the new Map region. The most popular of these is the ReportMap Plugin which has received a wealth of features and enhancements, and is being used widely. Since 2016 I have built and maintained plugins that make it easy to integrate Google Maps in your APEX applications. Within the APEX development team it has been known for some time that maps are frequently required and this has been on the roadmap to be built in to the core product. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |