Improved Mapping Layer Capability

Dan_Ryan-Oracle

The current limit on the size of file for creating new map layers is too small to have any level of detail. For example, being able to map to UK postcode level is currently not possible as it exceeds the size limit allowed. There are potentially many maps in the UK alone such as road and rail networks, detailed local area boundaries and so on. This would not be limited to the UK.

There are also open source mapping portals such as https://geoportal.statistics.gov.uk/search?q=BDY_SCN&sort=Date%20Created%7Ccreated%7Cdesc which could be a good way to get map layers without the need for download and upload if we could create some form of integration to these portals.

@Philippe Lions-Oracle

mgoswami

good idea Dan.

Philippe Lions-Oracle

Hello @Dan_Ryan-Oracle , @mgoswami

Thanks. You are actually asking two different questions : 1) max size for map layers in OA, and 2) providing capabilities to consume vanilla 'online' layer services.

For 1), we have just provided two distinct improvements in the product :

a) in Jan update (or possibly March if you don't see it yet from your side), when you upload a layer, under advanced tab you have the option to select External storage. See pic below. This storage will accommodate much larger geojsons, so that should help the issue. Note that, a large geojson will still impact rendering performance but at least the size limit should not block anymore. Functionally there should not be any difference between default and external, external does not require any extra configuration by administrators, it is simply part of any OA deployement behind the scenes.

b) the product now supports consuming geometry data types (either in DB sources, or as wkt format in csv files). This can dramatically help with very granular polygons as it bypasses the need of uploading any layer. Let us know if you need more details on this.

For 2), we are considering this as well, but have not yet designed it. Two parts :

a) allowing OA to generate dynamic layers based on API endpoints from external services. Currently this can be done for map backgrounds but not yet for data layers nor reference layers.

b) providing a library of services to support typical polygons (regions, zips, counties, etc…)

This is on our roadmap, but we can't yet nail a date for it unfortunately.

Let us know if you are thinking about other needs in that respect

thanks

Philippe

@Gautam Pisharam-Oracle @Benjamin Arnulf-Oracle